Responsive vs. mobile-first
A responsive layout adapts. A mobile-first layout is designed. The distinction matters because a desktop design compressed onto a small screen retains all the visual weight, complexity, and information density of the original. A mobile-first design starts by asking: what is the one thing this screen needs to communicate, and how do we make that impossible to miss?
In CSS terms, mobile-first means writing styles for the smallest viewport first and using min-width media queries to progressively add complexity as the screen grows, rather than writing desktop styles first and using max-width queries to strip things away. The direction of that progression changes what gets treated as the default.
Why mobile context is the harder design problem
Designing for mobile is harder than designing for desktop because the constraints are more severe. Limited screen space forces hierarchy decisions that desktop layouts can avoid. Touch interaction requires larger targets and more forgiving spacing than cursor interaction. Users on mobile are often distracted, in motion, or on slower connections.
These constraints are useful. A mobile-first designer has to decide what is most important early in the process, before the abundance of desktop space makes it possible to defer that decision. The result is usually a cleaner hierarchy that works on every screen size.
A common symptom of a desktop-first design is a homepage that looks impressive on a wide monitor and confusing on a phone, with tiny text, hard-to-tap navigation, and a primary call to action buried below several sections that work better in a wide-column layout.
The principles in practice
- One primary action per screen. On mobile, every page should have a clear primary action. Secondary options exist but do not compete visually. This is good design on any screen; mobile forces you to decide.
- Typography leads the layout. On a narrow viewport, text is most of what the user sees. Type sizes, line lengths, and line heights have an outsized effect on readability compared to a desktop layout where images and panels break up the page.
- Navigation is a last resort. If a user needs to open a menu to find something important, the page design has failed. Put the most common destination directly on the screen rather than behind a hamburger icon.
- Load only what is needed. Mobile connections are frequently slower than fixed broadband. Deferring images below the fold, using modern formats, and minimising JavaScript on the critical path are both performance and design decisions.
Mobile-first and Core Web Vitals
Google’s Core Web Vitals are measured predominantly from mobile field data. A site that scores well on desktop but poorly on mobile will rank on the basis of its mobile performance. Mobile-first design and performance optimisation are therefore complementary: a leaner, more focused mobile layout typically has fewer large resources, less render-blocking code, and faster interactivity than a compressed desktop design.
When auditing an existing site for performance, checking the mobile experience first reveals the most common sources of LCP and CLS issues: unoptimised hero images scaled down from large desktop dimensions, layout shifts caused by content reordering between breakpoints, and third-party scripts that run regardless of device type.