Mobile First

Mobile-first is a design constraint, not a workflow trick. Starting from the smallest screen forces decisions about what actually matters — and produces designs that work everywhere, rather than desktop layouts that survive being squeezed.

Why Constraint Produces Better Design

A desktop screen accommodates ambiguity. You can add a sidebar, expand a navigation, stack columns of information. A mobile screen does not allow this. Every element must justify its presence. The question is not "how do we fit this?" but "does this belong here at all?"

Responsive as a System, Not a Fix

Responsive design fails when it is applied retroactively — when breakpoints are added to patch a layout that was built for a fixed width. Done well, responsive design means a layout that adapts continuously, built from fluid values (percentages, rem, clamp) rather than fixed pixels that break at specific widths.

"Responsive design is not about making things fit. It is about making things right at every size."

Touch as the Primary Input

On mobile, the primary interaction model is touch — and touch has different requirements than mouse. Tap targets need to be at least 44×44px. Hover states are meaningless. Gestures (swipe, pinch, long-press) offer interaction patterns that have no desktop equivalent. Designing for touch first produces interfaces that are more forgiving everywhere.

Performance Is a Mobile-First Concern

Mobile devices have slower processors and less reliable network connections than desktop. A page that loads in 1.2 seconds on a fast laptop may take 4 seconds on a mid-range phone on LTE. Performance optimisation is not separate from mobile-first design — it is part of it.

Testing on Real Devices

Browser DevTools device emulation is useful for layout testing. It is not useful for performance testing, touch behaviour, or real-world rendering. Testing on actual hardware — a range of iOS and Android devices at different price points — reveals problems that emulation hides.

Conclusion

Mobile-first is an act of prioritisation. It produces cleaner information hierarchies, faster pages, and more focused interfaces. The constraint is the feature.