Somewhere along the way, the industry picked up a quiet habit: design for the laptop, then squeeze the result onto mobile as a closing chore. It made sense when mobile traffic was a sliver. That era is over. For most sites, the majority of visits happen on a phone — which means the 'mobile version' is the main version, and always was.

You're not designing for a screen size

Responsive design isn't really about pixels; it's about context. A phone in one hand means a thumb, not a cursor. It means sunlight, a distracted bus ride, a connection that flickers. The same person who browses on a laptop at noon completes the purchase on a phone at midnight. The experience has to follow them, not ask them to come back on a bigger device.

Mobile-first is a decision filter

Starting mobile-first isn't about technology; it's about honesty. A small screen forces the question every design secretly needs: what actually matters here? If it doesn't fit on the phone, maybe it was never important. Desktop then becomes the easy part — giving the essentials more room to breathe.

  • Touch targets a real thumb can hit without aiming.
  • Text large enough to read at arm's length.
  • Layouts that reflow instead of merely shrinking.
  • Images that don't cost more data than the page is worth.
  • No content that only exists on hover.
Your website doesn't have a target device. It has a target human — and the human moves.

Responsive design is respect, rendered in CSS. It says: however you arrived — old phone, new tablet, borrowed laptop — you get the whole experience, not a compromise with an apology attached. That's why, on every project I build, it isn't a feature at the end of the list. It's the ground everything else stands on.