Responsive Website Design: How to Plan for Mobile, Tablet and Desktop
How to plan responsive design: content priority per breakpoint, breakpoints from content and analytics, component specs, WCAG reflow and a device test matrix.
How do you plan responsive design?
Plan responsive design in four steps: rank the content on each template and decide what happens to each block at narrow, medium and wide widths; choose breakpoints where your content breaks, checked against your own analytics rather than a list of devices; write a behaviour spec for each component; and agree a device test matrix before the build. Design at a small phone width first, make sure everything still works at 320 CSS pixels, and keep the same content on every screen size.
This guide is for founders, marketers and product owners commissioning a website or app, and for designers writing the responsive part of a brief. It covers the planning and design decisions. For fixing an existing site, see how to make a website mobile-friendly.
Key takeaways
- Decide content priority per template before drawing layouts.
- Set breakpoints from the content, then sanity-check them against your own analytics.
- Do not hide content on mobile; reorder or collapse it instead.
- Write a behaviour spec for every component, not just three artboards.
- Treat WCAG reflow at 320 CSS pixels and 24 by 24 pixel targets as floors.
- Agree the device test matrix before the build, not after launch.
Start Mobile-First
Designing the smallest screen first forces the key question: what matters most? Once the essential content and actions work on a phone, larger screens can add space, secondary content and richer layouts. Starting from desktop tends to produce cramped, compromised mobile layouts.
There is also a search reason. Google says it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking", asks that the mobile site contain the same content as the desktop site, and recommends responsive design as the easiest pattern to implement and maintain.
Planning kit 1: content priority per breakpoint
For each template (home, service, product, article, checkout), list the content blocks and rank them by what the visitor needs first. Then decide, for each width band, whether each block is shown as is, collapsed (accordion or tabs), moved (lower down or into a menu or sheet) or deferred (loaded on demand). The rule is that nothing is removed on small screens. web.dev's guidance is direct: "Don't hide content just because you can't fit it on the screen."
| Block (example: service page) | Rank | Narrow (phone) | Medium (tablet) | Wide (desktop) |
|---|---|---|---|---|
| Headline and primary action | 1 | Show, first screen | Show | Show |
| Short proof (ratings, logos) | 2 | Show, compact | Show | Show beside headline |
| Service details | 3 | Collapse into sections | Show | Show |
| Process steps | 4 | Show as a vertical list | Two columns | Horizontal row |
| FAQs | 5 | Collapse | Collapse | Collapse |
| Secondary navigation | 6 | Move into menu | Move into menu | Show |
Planning kit 2: choosing breakpoints
Most breakpoint lists online are sets of device widths. Google's own guidance on web.dev says the opposite: "Don't define breakpoints based on device classes, or any product, brand name, or operating system." Devices change every year; your content does not. Use this method instead.
- Design the narrow layout first at a common small phone width, such as 360 CSS pixels, and check it still works at 320.
- Widen the canvas until the layout breaks (lines too long, cards too narrow, navigation crowded) and add a major breakpoint there. Repeat.
- Add minor breakpoints only for type, spacing and margins, not for whole new layouts.
- Set a maximum content width so lines stay readable on large screens.
- Pull the screen sizes from your own analytics for the last 90 days. List the widths that cover most sessions and check that each sits comfortably inside a layout band rather than just either side of a breakpoint.
- For components that appear in several column widths (cards, product tiles, pricing boxes), use container queries rather than more page breakpoints.
Worth noting
Device mix genuinely differs by market. StatCounter's platform share for September 2026 shows mobile at 77.3% of page views in India, 60.04% in the UAE, 53.56% in the UK and 48.57% in Australia, with tablets highest in the UK at 4.66%. These figures are page views on sites that use StatCounter, not users or sales, and they move month to month. Use them as context and plan from your own analytics.
Container queries and media queries
Media queries respond to the viewport, so they suit page-level layout: when the sidebar appears, when the grid goes from two columns to three. Container queries respond to the size of the element a component sits in, so the same product card can stack in a narrow sidebar and sit side by side in a wide section without separate variants. MDN lists the @container rule as Baseline widely available, "available across browsers since February 2023", with a note that some parts of the feature have varying support.
For planning, this changes the spec. Instead of describing a card "on tablet", describe it by the width of its container, which is how the developer will build it.
Planning kit 3: component behaviour spec
Write one of these for each component that changes across widths. It is the written version of what designers often leave in three artboards, and it is what developers need at design handoff. The example shows a product card.
| Field | What to specify | Example: product card |
|---|---|---|
| Container widths | The widths of space it appears in | Grid cell 160 to 320px; sidebar 240px |
| Layout per band | How the parts arrange at each container width | Under 240px: image above text; 240px and over: image left |
| Truncation | What shortens and how | Title two lines then ellipsis; full title on product page |
| Moves or collapses | What goes into a menu, sheet or accordion | Quick-add opens a bottom sheet on narrow widths |
| Touch target | Minimum size and spacing | Add button at least 24 by 24 CSS px, with spacing |
| Hover fallback | What replaces hover on touch | Second image on hover; no reliance on hover for price or actions |
| Reflow at 320 | Behaviour at the WCAG floor | Single column, no horizontal scroll |
| Text scaling | Behaviour with larger system text | Card grows in height; text does not clip |
Responsive Components
Common patterns to start from:
| Component | Narrow screens | Wide screens |
|---|---|---|
| Navigation | Menu button or bottom bar, few top items | Full horizontal navigation |
| Product or card grid | One or two columns | Three or more columns |
| Tables | Scroll within container or stacked cards | Full table |
| Sidebars and filters | Collapsible panel or sheet | Persistent sidebar |
| Forms | Single column, full-width inputs | Grouped fields where logical |
| Media | Cropped or reordered for focus | Wider compositions |
Typography and Spacing
Scale headings down on small screens while keeping body text comfortably readable. Spacing should also scale: generous whitespace on desktop may need tightening on mobile, but not to the point of crowding. Define these as tokens in your design system so the rules hold as the site grows.
The accessibility floors: reflow and target size
Two WCAG 2.2 level AA criteria set hard minimums for responsive work. Success criterion 1.4.10 Reflow reads: "Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning." W3C notes that 320 CSS pixels is equivalent to a 1280 pixel wide viewport at 400% zoom, which is also how to test it.
Success criterion 2.5.8 Target Size (Minimum) reads: "The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when" one of five exceptions applies: spacing (smaller targets with enough space around them), an equivalent control elsewhere on the page, inline targets in a sentence, targets sized by the browser, or where a particular presentation is essential. Platform guidelines for apps recommend larger targets than this minimum, so treat 24 pixels as a floor, not a goal. On touch screens, also make sure nothing essential depends on hover. More in accessibility in UI/UX design.
Planning kit 4: device test matrix
Agree this before the build so testing is budgeted and nobody argues about it at launch. The widths are examples of common sizes, not targets; replace them with the widths from your own analytics. StatCounter's mobile resolution data for India in September 2026, for instance, put 360×800 at 15.28% of mobile page views with a long, fragmented tail behind it, which is why ranges matter more than devices.
| Test condition | Why | Where to test |
|---|---|---|
| 320 CSS px wide, or 1280px at 400% zoom | WCAG reflow floor | Desktop browser zoom and DevTools |
| 360 to 393 px phone widths | The most common phone widths in StatCounter's India data | Real mid-range Android in Chrome; Samsung Internet if your analytics show it |
| A current iPhone at its native width | iOS Safari handles viewport height, zoom and fixed elements differently | Real iPhone in Safari |
| Tablet portrait and landscape (around 768 and 1024 px) | The in-between layouts where bugs hide | Real tablet or emulator; add an iPad if your audience uses them |
| 1280, 1440 and 1920 px | Line length, maximum widths, empty space | Desktop Chrome, Safari, Edge and Firefox |
| 200% text size | Large system text clips labels and buttons | Phone and desktop settings |
| Landscape phone | Short heights break sticky headers and modals | Real phone |
| Slow connection | Images and layout shift on mobile networks | Browser network throttling |
Pro tip
Regional note: where your audience is mostly on Android phones, as StatCounter's data suggests for India, include at least one low-to-mid range Android device in real-device testing. Where tablets carry a noticeable share, as in the UK data, give iPad portrait and landscape their own row.
Hypothetical example: planning a services site
Hypothetical example: a professional services firm is commissioning a new site. Its designer has produced a desktop design and a single mobile version. Before quotes go out, the firm adds the planning kit to the brief. The content priority table shows the service details were going to be cut on mobile, so they become collapsible sections instead. The analytics export shows a large share of visits at 390 to 430 pixels, and the designer's tablet breakpoint sat at 420, so a common phone width would have flipped between two layouts; the breakpoint moves to where the layout actually needs it. Three components get behaviour specs, and the test matrix becomes part of acceptance. Developers can now quote against the same written expectations.
Common mistakes
- Copying a breakpoint list from a framework or blog without checking the content
- Hiding content on mobile to make the layout fit
- Designing three artboards and leaving the widths between them to developers
- Testing only by resizing a desktop browser
- Treating the 24 pixel target minimum as the target
- Leaving tables, long words and embedded media to overflow
- Ignoring landscape phones and large system text
When this approach is not the right fit
A single responsive design is the right default for most websites, but not for everything. Complex data tools used mostly at a desk, such as admin dashboards, may justify designing the wide layout first and offering a simpler mobile view of the key tasks. Native apps follow platform conventions rather than web breakpoints. And for a small brochure site on a well-built theme, the full kit is more than you need: the content priority table and the test matrix still pay off, but the theme's breakpoints are usually fine.
If your site is already live and failing on phones, start with our mobile-friendly checklist instead; this planning kit is for new builds and redesigns. Our website development service page explains how we approach responsive builds.
Sources
web.dev: Responsive web design basics (last updated 12 February 2019; long-standing guidance); Google Search Central: mobile-first indexing best practices (last updated 10 December 2025); MDN: @container; W3C: Understanding SC 1.4.10 Reflow; W3C: Understanding SC 2.5.8 Target Size (Minimum).
Market data: StatCounter: desktop vs mobile vs tablet market share (India, United Arab Emirates, United Kingdom and Australia pages, September 2026) and StatCounter: mobile screen resolution stats, India (September 2026). Third-party page-view data; it changes monthly.
Accessed 15 October 2026.
Conclusion
Responsive design goes well when it is planned in writing: content priority per template, breakpoints set by the content and checked against your analytics, a behaviour spec for each component, and a test matrix everyone has agreed. Hold to the accessibility floors, keep content the same across screen sizes, and test on real phones. A good next step is to fill in the content priority table for your most important template before any layouts are drawn.
Planning a new site or redesign?
ZSpace Labs is a remote-first technology studio that works with clients globally on website development and UI/UX design. If useful, we can help you write the responsive spec: content priority, breakpoints from your analytics and a device test plan.
Common questions.
Designing interfaces that adapt their layout, content and components to different screen sizes and input methods, rather than creating separate fixed designs for each device.
Designing the smallest screen first, then enhancing for larger screens. It forces prioritisation of the most important content and actions.
Choose breakpoints where your content needs to change layout, not around specific devices. Start narrow, widen until the layout breaks, and add a breakpoint there. Then check your own analytics to make sure the widths most of your visitors use sit comfortably inside a layout rather than right on the edge of one.
Responsive layouts flow continuously with the screen size. Adaptive designs switch between a few fixed layouts. Most modern sites are responsive, sometimes with adaptive elements.
Consider horizontal scrolling within a container, stacking rows into cards, or showing fewer columns by default. Never let a table break the page width. WCAG's reflow criterion allows two-dimensional scrolling only for content that genuinely needs a two-dimensional layout, such as a data table.
WCAG 2.2 success criterion 2.5.8 (level AA) sets a minimum of 24 by 24 CSS pixels for pointer targets, with exceptions such as enough spacing around smaller targets and links inside sentences. That is a minimum. Apple's and Google's platform guidelines recommend larger targets for apps, so check their current guidance if you are designing for iOS or Android.
Google uses the mobile version of a site's content, crawled with a smartphone agent, for indexing and ranking, and recommends responsive design as the easiest pattern to maintain. The practical rule is to keep the same content on mobile as on desktop; tabs and accordions are acceptable.
This guide covers planning and design decisions: content priority, breakpoints, component behaviour and the test plan. The mobile-friendly website guide is a practical checklist for implementing and fixing a mobile-friendly site.
As many as the content needs, which for many marketing sites is two or three major layout changes plus some minor adjustments to type and spacing. Components that appear in several column widths may be better handled with container queries than with more page-level breakpoints.
Both. Media queries suit page-level layout. Container queries let a component respond to the width of the space it sits in, which is useful for cards and widgets reused in sidebars, grids and full-width sections. MDN lists container queries as Baseline widely available, though some newer parts of the feature vary in support.