Three myths about responsive layout
The version of this that works is simpler than the version most people imagine. A few things about responsive layout that get repeated more often than they get checked.
Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
“It only matters for big sites”
Design for the smallest screen first and let the layout grow. That sounds obvious written down. It is still the thing most often skipped. Write the reasoning down alongside the decision, because the reasoning is what changes first.
“We can deal with it after launch”
Sometimes true, usually expensive. Getting it slightly wrong is survivable. Ignoring it entirely is not.
“Our platform handles it”
Test on a real phone, not just a resized browser window. The cost of getting this wrong is rarely visible on the day it happens. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
How to tell if yours is fine
Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. Three things worth confirming about responsive layout before you move on:
- Someone can say what the current setup is without going to look
- Design for the smallest screen first and let the layout grow — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If any of that sounds like a description of your current setup, it is fixable.