When responsive layout is worth the effort

It is rarely the thing that gets a project approved, and often the thing that decides how it goes. Responsive layout 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. If two people in the business would answer this differently, that gap is the actual problem.

When it is worth it

Design for the smallest screen first and let the layout grow. In practice this is a scheduling problem more than a technical one. It rarely shows up as a line item, which is exactly why it slips.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. None of that requires a large budget, only a decision and someone to own it.

How to decide

Test on a real phone, not just a resized browser window. There is a version of this that is over-engineered, and it is worth avoiding. If it only works because one person remembers to do something, it does not work yet.

What this looks like day to day

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 responsive layout before you move on:

• Someone can say what the current setup is without going to look
• Breakpoints should follow your content, not device names — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If you are not sure where your systems currently stand on this, it takes us about an hour to find out.