Mobile-First Is Not the Same as Mobile-Only

"Mobile-first" was a useful corrective in 2012. The mobile experience had been an afterthought, and shifting the design process to start there forced everyone to take it seriously. It worked.

Then it became dogma. By 2018, "mobile-first" had quietly become "mobile-only" — the desktop experience was an afterstretched mobile layout, the same UI scaled up. The result was billions of pixels of empty whitespace and content that fit in a column when it should have been a grid.

The Actual Principle

The original meaning was: design the mobile experience as a first-class citizen, not as a degraded version. The principle was about parity, not exclusivity.

The right way to apply it now: design both experiences in parallel, with shared design language but separate layouts. The mobile experience is single-column and stacks vertically. The desktop experience can use the third dimension that mobile does not have — peripheral information, side panels, secondary actions visible without a tap.

I have audited dozens of apps in the last year that ship a phone-shaped interface in the middle of a 2K monitor. The user is not impressed by the consistency. The user is annoyed by the wasted space.

Mobile-first as a process is right. Mobile-shaped as an output is wrong.