When mobile-first design is worth the effort

The version of this that works is simpler than the version most people imagine. Mobile-first design is not free, and pretending otherwise leads to bad decisions.

The measurable part of design is whether people can find what they came for and act on it without hesitating. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

When it is worth it

More than half of most sites' traffic arrives on a phone. The teams that handle this well are rarely the ones with the biggest budgets. If it only works because one person remembers to do something, it does not work yet.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. Getting it slightly wrong is survivable. Ignoring it entirely is not.

How to decide

Desktop layouts are easier to add than to strip back. That sounds obvious written down. It is still the thing most often skipped. If two people in the business would answer this differently, that gap is the actual problem.

In practice

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Three things worth confirming about mobile-first design before you move on:

• Someone can say what the current setup is without going to look
• Starting narrow forces you to decide what actually matters — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.