For the first ten years of the commercial web, "design a website" quietly meant "design a website for a desktop monitor." Phones existed, but they got a stripped-down, separate ".mobile" site if they got anything at all. That assumption broke this year. Browsing data from several ad networks and analytics providers now shows mobile devices accounting for more page views than desktops in a growing number of markets, and the trend line only points one way.
What "responsive" actually means
Ethan Marcotte coined the term in 2010, and the idea is simple even if the execution takes practice: one HTML document, one set of assets, and a stylesheet that reshapes the layout using fluid grids, flexible images, and CSS media queries. Nothing is duplicated for mobile. The same markup that renders a three-column dashboard on a widescreen monitor collapses into a single readable column on a phone, because the CSS - not the server - decides how much room is available.
/* fluid grid unit, not a fixed pixel width */
.column {
width: 100%;
}
@media (min-width: 768px) {
.column {
width: 33.333%;
float: left;
}
}
Start from the smallest screen
The practical shift we've made in our own process is designing mobile-first rather than adding mobile as an afterthought. Sketch the content that matters most on a 320px-wide screen, get that hierarchy right, and then use min-width media queries to add complexity as space allows - a second column here, a sidebar there. Doing it backwards, stripping a desktop layout down for mobile, almost always leaves you cutting features under deadline pressure instead of designing them properly from day one.
Flexible images, not fixed ones
The other habit worth breaking is the fixed-width <img> tag. A single rule fixes most of it:
img { max-width: 100%; height: auto; }
That one line stops a 1200px hero image from blowing out a 320px viewport, and it costs nothing to add. Serving a smaller file to that same phone is a separate, harder problem - the srcset attribute is still working its way through browser support - but the layout, at least, no longer breaks.
A responsive layout isn't a phone version of a desktop site. It's one design that knows how to be several sizes.
What this costs, and what it buys back
Responsive design does mean more testing: a real device lab, or at minimum a set of browser emulators, becomes part of the workflow rather than a nice-to-have. It also means content decisions can't be deferred to a "we'll fix mobile later" phase, because mobile isn't a phase anymore - it's the majority. The payoff is one codebase, one URL structure that search engines can index without confusion, and a site that keeps working as new screen sizes keep arriving, because none of them were ever designed for.
"Optional" stopped being true around 2016
Mobile traffic overtaking desktop wasn't a gradual trend that eventually justified responsive design - for most sites it crossed 50% years ago and has kept climbing since. A site that isn't responsive today is actively broken for the majority of the people trying to use it, not just suboptimal for a minority.
<meta name="viewport" content="width=device-width, initial-scale=1">
img, video { max-width: 100%; height: auto; }
Responsive is necessary, not sufficient
A layout that merely reflows to fit a smaller screen without reconsidering navigation patterns, tap target sizes, and content priority is technically responsive and still a poor mobile experience. Genuine mobile quality means rethinking the interaction model for touch and a smaller viewport, not just running the desktop design through a set of breakpoints and calling it done.