Responsive Design
Responsive design uses fluid layout, flexible media, and conditional rules so one interface adapts continuously across viewport sizes and capabilities.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/responsive-design/
01What it means
Responsive design lets the same core content and interface reflow across available space. Relative sizing, flexible grids, responsive media, container or media queries, and content-driven breakpoints let components change arrangement without a separate page for each device class.[1][2][3]
- 01NarrowStack, wrap, prioritize, avoid overflow
- 02GrowingIntrinsic components use available space
- 03BreakpointChange arrangement where content needs it
- 04WideAdd columns without separating the experience
Breakpoints respond to layout needs rather than fashionable device widths, while preserving content, function, reading order, and focus order.
02Why it matters
People resize windows, zoom text, rotate devices, split screens, and use displays outside a few presets. Responsive design protects readability and completion across that range, supports accessible reflow, and reduces divergence caused by maintaining unrelated mobile and desktop experiences.
03When to use it
Use it for sites and applications whose content and tasks should remain available across screen sizes. Plan from the component and content model onward, then test zoom, large text, narrow windows, touch, keyboard, and real content—not only device screenshots.
04How it works
- Prioritize content and actions before selecting breakpoints.
- Build flexible components with intrinsic sizing, wrapping, and media that cannot overflow.
- Add breakpoints where content needs a new arrangement, not at fashionable device widths.
- Preserve reading order, focus order, target size, and functionality as regions move.
- Test narrow to wide, high zoom, long translations, slow assets, and assistive technology.
05A practical example
A commerce category uses a fluid grid that moves from one to several columns as cards gain space. Filters become a labeled disclosure on narrow views but preserve selections and keyboard access. Images publish appropriate sizes so small screens avoid desktop downloads.
06Where it breaks
Responsiveness does not guarantee good mobile usability or speed. A layout may reflow while preserving too much content, downloading oversized assets, or moving controls unpredictably. Extreme tables, canvases, and editors may need task-specific alternatives rather than stacking.
Common mistakes
- Choosing breakpoints only from current device models
- Changing visual order while leaving keyboard and reading order behind
- Serving desktop-size media and scripts to every viewport
07Sources
- Responsive designMDN Web Docs · Technical documentationResponsive design
- Understanding SC 1.4.10: ReflowW3C Web Accessibility Initiative · Accessibility guidanceUnderstanding SC 1.4.10: Reflow
- Responsive Web Design and User ExperienceNielsen Norman Group · Professional articleResponsive Web Design and User Experience