By Sharon Gilbert-Rivett

When Google designer and product director Luke Wroblewski coined the concept of "Mobile First" in a 2009 blog post and subsequently a 2011 book, he backed website designers and developers into a corner without so much as a "by your leave". The result? A travesty for anyone with a single iota of understanding for the processes involved in creating an eye-catching, engaging website and a phrase that's laid waste to common sense. Here's why...

Wroblewski's original argument was strategic rather than design-based. Mobile internet usage was growing exponentially and designers were consistently treating mobile as an afterthought, bolting it on at the end of the desktop design process and producing stripped-down, inferior mobile experiences as a result. His point was essentially this: if mobile is where your audience is, design for that constraint first and let the desktop version be the expanded, enhanced version rather than the other way around.

It was a prioritisation argument rather than a workflow prescription, and for a while, in theory at least, it made a degree of sense. Then Google got involved and everything went sideways.

How a sensible idea became an industry-wide headache

In 2019, Google switched to mobile-first indexing, meaning it began using the mobile version of a site as the primary version for ranking and search purposes rather than the desktop version. The reason was straightforward: by that point the majority of global web traffic was coming from mobile devices. Google was simply reflecting reality.

But here's where the confusion took root and refused to leave because the SEO industry picked up the phrase "mobile-first indexing" and conflated it entirely with "mobile-first design". Two entirely different things, fused together into a single piece of received wisdom that has been repeated so many times and so confidently that most people have stopped questioning it.

Suddenly every agency, every platform, and every blog post was declaring that you must design for mobile first, because Google had changed its indexing behaviour and someone, somewhere, decided that meant the design process had to change too. It doesn't and it never did.

The practical reality of designing desktop first

Complex layouts, navigation structures, typography hierarchies, and visual relationships are infinitely easier to establish on a large canvas and then adapt for smaller screens than to build on a small canvas and try to expand upward.

Any designer or developer who has worked both ways knows this instinctively. A desktop canvas gives you space to think, to establish hierarchy, to build the visual relationships that make a site feel coherent and purposeful. You can see the whole picture and you can make decisions about proportion, balance, and flow that simply aren't possible when you're starting with 390 pixels of width and trying to imagine how it scales up.

Designing mobile first means you're constantly trying to expand something inherently constrained into something expansive. It's harder, it takes longer, and the desktop version almost always suffers for it. Designing desktop first and optimising downward is the logical direction of travel because you're simplifying and adapting a complete vision rather than trying to extrapolate an incomplete one.

The tools reflect this. Duda, one of the most sophisticated website development platforms available and the platform we build on exclusively, is structured around exactly this workflow. You design the desktop version and then use the responsive editor to adjust layouts, typography, and content for tablet and mobile breakpoints intelligently and specifically with full control over exactly how each element behaves at each screen size. It's designing intelligently for every screen, starting where the design has room to breathe.

What Google actually requires

Here is what Google's mobile-first indexing actually means in practice, stripped of the confusion that has accumulated around it. Google requires that the mobile version of your site is complete, functional, fast, and contains the same content as the desktop version. It requires that the mobile experience is not a stripped-down afterthought. It requires good Core Web Vitals scores on mobile, which means fast loading, visual stability, and responsive interactivity.

None of that requires you to design on mobile first but rather asks you to optimise for mobile thoroughly, to test on mobile rigorously, and to make sure the mobile version of your site is every bit as good as the desktop version. These are technical and quality requirements that have nothing to do with which screen size you open your design software on in the morning.

A desktop-first design process that produces a properly optimised, fully responsive, fast-loading mobile experience satisfies every one of Google's requirements completely. A mobile-first design process that produces a mediocre desktop experience does not.

The conflation that cost the industry its common sense

The damage done by conflating mobile-first indexing with mobile-first design is real and ongoing. Designers and developers who know better are second-guessing their workflow because clients have been told by the internet that mobile-first is non-negotiable. Agencies are adding unnecessary complexity to their processes and an enormous amount of energy is being spent defending a methodology that was never actually mandated.

What was mandated was mobile excellence, which is an entirely reasonable requirement and one that any competent developer takes seriously. The route to mobile excellence is not prescribed. Desktop-first design followed by thorough mobile optimisation gets you there just as reliably as any other approach, and for most designers and developers, considerably more efficiently.

What actually matters

The questions worth asking about any website are not which screen size was designed first, they are whether the mobile experience is fast, whether it's visually coherent, whether the content is complete and accessible, and whether it works flawlessly on the devices your audience is actually using.

If the answer to all of those questions is yes, Google is satisfied, your audience is satisfied and the methodology that got you there is your own business. Design desktop first if that's where your process works best and optimise for mobile with the thoroughness and care it deserves. Test on every screen size before anything goes live and stop letting a misread of Google's indexing behaviour dictate your creative process.