“Mobile-first” was a useful phrase when most designers were building for desktop and treating mobile as an afterthought. That hasn’t been true for years. The phrase persists in agency websites, in design briefs, and in client conversations — but as a strategy, it’s now slightly wrong, slightly out of date, and slightly misleading.
What “mobile-first” used to mean
The original phrase, from Luke Wroblewski in 2009, was a reaction to a real problem. Designers were building rich desktop experiences and then squeezing them down to mobile, where they performed poorly. Wroblewski’s argument: design for the constrained context first. Force yourself to identify what’s truly essential. Then add to it for larger screens.
This was excellent advice in 2009. It’s still excellent design discipline. But “mobile-first” has come to mean something else in agency briefs — usually some version of “the site needs to look good on a phone” — and that meaning is much weaker than the original.
Why the phrase doesn’t carry its weight anymore
Three things have changed since 2009 that make “mobile-first” insufficient as a design directive:
Mobile traffic isn’t homogeneous. “Mobile” in 2026 covers everything from a top-end iPhone with edge-to-edge display to a $100 Android in a slow market. The “mobile experience” you design for one is wrong for the other. Designing for “mobile” without specifying which mobile is designing for nobody.
Desktop is back, in some categories. B2B SaaS purchases happen on desktop. Long-form content gets read on desktop. Anything involving sustained focus or comparative shopping happens on desktop. For a B2B service business, treating desktop as a compromise of mobile is exactly backwards.
The contexts that matter are situations, not devices. “Someone browsing while in line for coffee” and “someone evaluating vendors at their desk” are different contexts. Both are valid traffic. The distinction isn’t device — it’s intent and attention.
What’s replaced it
The frame that’s working in 2026 is “context-first” or “task-first” design. You ask: what does the visitor want to do, how much attention do they have, and what do they have access to?
For a B2B service site, the priority contexts usually look like:
- Quick credibility check on phone. A potential client gets your name from a referral and Googles you on their phone. They have 30 seconds. The site needs to confirm you’re legitimate, working, and the right kind of business.
- Sustained evaluation on desktop. Same person, two days later, at their desk, with three tabs open comparing you to two competitors. They have 15 minutes. The site needs to support comparison and provide enough depth to be the best of the three.
- Pricing and decision conversation. Same person, with their team, on a screen-share. The site needs to be the kind of thing that holds up in a meeting where it’s being scrolled through and discussed.
None of these is “mobile” or “desktop” — they’re situations. The site needs to work across all of them. “Mobile-first” tells you nothing about the third.
What this means in practice
Designing for situations rather than devices changes a few things:
Information density varies by context. The mobile homepage might show three things; the desktop homepage might show twelve. The desktop version isn’t “the mobile version with more on it” — it’s a different layout because the situation is different.
Performance budgets are situational. The 3G commute viewer needs the page in 1.5 seconds. The desktop reviewer can wait 2 seconds for richer interaction. Optimising both situations is different work, not the same work copied.
Content strategy gets explicit. What’s the lead-in for the 30-second credibility check? What’s the depth for the 15-minute evaluator? These should be designed deliberately, not assumed to emerge from a single content set displayed differently on different screen sizes.
Why this matters for SEO
Google’s mobile-first indexing has been the rule since 2019, but it doesn’t mean what most people think. Google indexes the mobile version as the primary, not because mobile is more important — but because mobile is the lower bound. If the mobile version is good enough, the desktop version usually is too. If the mobile version is missing content, the SEO damage happens regardless of how good the desktop is.
The implication: the mobile version should be the complete site, not a stripped-down version. Hide content from mobile users and you’ve hidden it from Google. The “mobile-first” framing is right about this and the modern context-first framing reaches the same conclusion.
For more on what’s actually moving the needle in 2026, our SEO playbook covers the indexing and ranking changes, and our conversion analysis walks through the situations that matter for B2B sites specifically.
The takeaway
Stop hiring an agency that markets “mobile-first design.” It’s a 2009 phrase doing 2026 work. Hire an agency that talks about who’s looking at the site, what they’re trying to do, and what device they’re holding while they do it. The terminology is less catchy. The work is better.
The phrases that survive in design vocabulary are the ones that solve real problems. “Mobile-first” solved one in 2009. The problems in 2026 are different. The vocabulary should follow.
