The most common mistake in mobile design is treating the phone as a small monitor. Take the desktop layout, squeeze it, stack the columns, shrink the text, and call it responsive. It technically fits. It also misses the entire point, because the screen size is the least important thing that changed. What actually changed is the situation the person is in.
The desktop user and the phone user are not the same person
Picture the two honestly. The desktop user is sitting down, probably indoors, likely with time and both hands, attention more or less on the task. The phone user could be anywhere: walking, queuing, on a train, holding a child, half-watching something else, with thirty seconds and one thumb. Same human, completely different conditions. Designing for the second as though they were the first is why so many mobile experiences feel like hard work.
What the situation demands
Once you design for the situation rather than the screen, different things start to matter.
- One thumb, one hand. The important controls belong where a thumb can actually reach them, not tucked in a top corner that needs a second hand.
- Interruptible. Phone tasks get interrupted constantly. The app should hold its place and let people resume, not punish them for looking away.
- Glanceable. Often someone has seconds, not minutes. The most useful thing should be readable at a glance, not buried below three taps.
- Forgiving of fat fingers and bad light. Bigger targets, stronger contrast, fewer chances to tap the wrong thing — not because the screen is small, but because the conditions are messy.
Less is not a compromise, it is the design
Shrinking a desktop screen tries to preserve everything, just smaller. Designing for the mobile situation does the opposite: it asks what this person, here, now, actually needs, and shows them that, prominently, and hides or drops the rest. The result is not a lesser version of the desktop experience. It is often a clearer one, because the constraint forced a decision about what really matters that the spacious desktop let you avoid.
That clarity tends to flow back the other way, too. Teams that design the mobile situation first usually end up with a sharper desktop product as well, because they were forced to work out the essence before they were allowed to add the nice-to-haves.
Start with the moment, not the breakpoint
So before reaching for the responsive grid, ask the more useful question: where is this person and what is happening around them when they pull out their phone to do this? Design for that moment — the walking, the waiting, the one free thumb, the half of their attention — and the layout will follow. Start with the breakpoint instead, and you will ship a desktop product in a smaller box, and wonder why it feels like such a chore to use.