When does mobile need a genuinely different design vs just a reflow?

Mobile needs a genuinely different design only when the priorities change, not just the width. If the same content in the same order still serves the user in a single column, a reflow is enough. If the mobile context, the way people actually hold the phone, where they are, what they came to do, shifts what matters most, then you are no longer narrowing a layout, you are designing a different experience that happens to share a brand. The test is the priority list, not the pixel count.

The reason the priority test beats the width test is that responsive technique can pour any layout into a narrow frame, but it cannot decide what belongs at the top. A reflow keeps your desktop hierarchy and simply restacks it. That works when the hierarchy is still right. The moment the mobile user wants something the desktop user did not, a clean reflow faithfully reproduces the wrong order. Width tells you how much room you have. Priority tells you what to do with it, and only the second question reveals whether a rethink is owed.

Consider a restaurant site. On desktop the homepage leads with mood photography, the story of the chef, then the menu, then a reservation form well down the page. Reflowed to mobile, all of that stacks honestly and the photos still look good. But the person on the phone is usually standing outside or in a car deciding whether to come in tonight. They want the address, the hours, the phone number, and a way to book, fast. The priorities have changed, so the right mobile design promotes those four things above the fold and lets the story wait. That is not a reflow, that is a different design, and the desktop version was not wrong, it was answering a different person.

There is a middle ground worth naming, because the call is rarely all reflow or all redesign. Often the priorities shift for one zone of the page rather than the whole thing, so the right answer is a reflow for most of it plus a genuine rethink for the part that changed. A product page might reflow its description and specs cleanly while its add-to-cart and price block get promoted, pinned, and simplified for the thumb. Treating that as a binary, either restack everything or rebuild everything, misses the common case, which is a faithful reflow with a few sections redesigned where mobile use actually diverges. The priority test still decides, it just decides section by section.

The edge case is real and it cuts the other way often. Most content sites, documentation, articles, marketing pages where the reader simply consumes top to bottom, genuinely need only a reflow, and inventing a separate mobile design for them adds maintenance cost and cross-device confusion for no gain. A blog post is a blog post on any screen. The trap is assuming every project sits on one side of the line. The honest move is to run the priority test per project rather than defaulting to either “just stack it” or “build a special mobile version.”

Before you settle for a reflow, write down what the mobile user most needs to do and compare it to the desktop priority order. If the two lists match, restack with confidence and spend your effort on spacing and sequence. If they diverge, treat mobile as its own design problem and let the layout follow the changed priorities rather than the inherited shape. Decide by the priorities, and the width will take care of itself.