We Stopped Doing Mobile-First and Started Content-First

October 27, 2026

Illustration of mobile and desktop screens surrounded by content blocks stacked by priority bottom cut

We Stopped Doing Mobile-First and Started Content-First

A few months ago I sat in a kick-off for a B2B platform redesign. The designer opened Figma at 375 pixels wide and started laying out screens. I asked why mobile. The answer was the one I have been hearing for years: "We do mobile-first, it's best practice." The detail that mattered: 83% of that platform's users worked on desktop, mid-workday, inside a tool they live in for eight hours. Mobile was the edge case, and we had put it at the center of the process because that is what you are "supposed" to do.

That was the moment I realized mobile-first, for most teams, had stopped being a decision and become a ritual.

Where mobile-first came from and why it made sense

The term was popularized by Luke Wroblewski around 2009 and his 2011 book "Mobile First". The argument was excellent for its time: a small screen forces you to drop everything non-essential and keep only what matters. If content and function fit and work at 320 pixels, on desktop you simply have more room to breathe. Back then, mobile-first was healthy discipline against cluttered, desktop-centric interfaces that fell apart on phones.

But that was advice for a specific context at a specific moment. We turned it into a universal rule and stopped asking whether it still holds for the project in front of us. That is the definition of a cargo cult: you perform the ritual because it once produced a result for someone, with no understanding of why.

What the real problem is

The problem is not the phone. Mobile traffic is huge, with StatCounter putting it somewhere between half and roughly sixty percent of global traffic depending on the month and methodology. The problem is that people read "start from mobile" as "start drawing the narrowest layout", and that is the wrong first decision entirely.

When you draw layout first, your first questions are "how many columns" and "how does this fit", not "what actually needs to be here and in what order". The result is screens that look tidy on both devices while serving no meaningful task well on either. We have seen it dozens of times: a flawlessly responsive page where nobody knows where to click.

Content-first: we changed the order, not the tool

Content-first does not mean "we build for desktop". It means layout, and therefore the breakpoint, is not the first decision. The first decision is the hierarchy of content and tasks, independent of device.

Our order today looks like this:

  1. Tasks and content. What does the user have to accomplish here and what information do they need to do it? We write it as plain text before any Figma. If we cannot write it, we cannot design it.
  2. Priority. What is primary, what is secondary, what is allowed to disappear. This is the one thing mobile-first does well, so we keep it, we just do it with words, not frames.
  3. Device context. Only now do we look at where and how people actually use this. A tourism booking on a phone at a café and an internal dashboard on dual monitors are not the same problem and do not deserve the same starting screen.
  4. Layout and breakpoints. The last step, not the first.

On a tourism project this meant we genuinely built a mobile experience for guests, because they book from a terrace. On the B2B platform above it meant we first laid out information density for the desktop workflow, then degraded it sensibly toward mobile, instead of stretching mobile "minimalism" onto a screen with ten times the room.

This is not a call to go desktop-first

To be clear: desktop-first from 2008 was worse. I am not arguing for a return to cluttered interfaces that choke on phones. I am arguing that we stop choosing a device as the first decision and start choosing content.

The technical tools stay the same. You still write min-width media queries, you still build fluid grids and container queries. The difference is in your head: the breakpoint becomes a consequence of content that breaks, not a number you picked at the start because "mobile-first".

How to know which approach you need

Do not look for a universal rule, ask three questions before every project. Where does traffic actually come from, per your analytics, not someone else's blog? In what context does the user perform the main task? Is the product content-light or content-dense? The answers will tell you more than any headline "best practice".

The cargo cult is comfortable because it removes responsibility. "We do mobile-first" sounds professional and nobody asks you why. But the client does not pay for a ritual, they pay for a result. And the result comes when you first decide what you are saying, and only then on which screen.

Related:

Planning a redesign and not sure you are starting in the right place? Contact us and we will look at where your users actually come from and which order of decisions makes sense for your product.

It takes 10 seconds to request a quote.

No strings attached.

computer guy

Subscribe to our Newsletter

Flawless digital

solutions

Our Offices
Check out
facebook twitter linkedin