Mobile First is a design strategy that calls for designing the smallest-screen, most constrained experience before the desktop one, then layering on additional content and capability as the screen and context allow. The phrase was coined by Luke Wroblewski, who introduced it in a November 3, 2009 post on his own site lukew.com and later expanded it into the 2011 A Book Apart title “Mobile First.”
In the original post, Wroblewski gave three reasons to start with mobile. The first was growth: mobile use was accelerating fast, and designing for it meant reaching a rapidly expanding audience. The second was focus. As he put it, “There simply isn’t room in a 320 by 480 pixel screen for extraneous, unnecessary elements,” so the small canvas forces teams to prioritize the content and actions that matter most. The third was capability: phones carried sensors and inputs that desktops lacked, such as GPS, accelerometers, multi-touch, and a digital compass, opening the door to “rich context-aware applications.”
The key inversion is in the order of work. Conventional practice designed the full desktop site first and then tried to cram or strip it down to fit a phone, a process that tended to lose the most important things in the shuffle. Mobile First reverses that flow: begin with the hard constraints, decide what is essential, and treat everything beyond the small screen as progressive enhancement rather than the starting point.
Mobile First became one of the foundational ideas of responsive web design, dovetailing with techniques like fluid grids and CSS media queries that let a single codebase adapt across screen sizes. By framing constraints as a source of clarity rather than an afterthought, it reshaped how teams approached layout, performance, and content priority across the web and influenced the later push toward installable, app-like web experiences.