# Responsive Design

Responsive design uses fluid layout, flexible media, and conditional rules so one interface adapts continuously across viewport sizes and capabilities.

- Type: practice
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/responsive-design/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Prioritize content and actions before selecting breakpoints.
2. Build flexible components with intrinsic sizing, wrapping, and media that cannot overflow.
3. Add breakpoints where content needs a new arrangement, not at fashionable device widths.
4. Preserve reading order, focus order, target size, and functionality as regions move.
5. Test narrow to wide, high zoom, long translations, slow assets, and assistive technology.

## A 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.

## Where 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

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/responsive-design/#visualization-responsive-design>)

## Sources

1. [Responsive design](<https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/CSS_layout/Responsive_Design>) — MDN Web Docs · Technical documentation
2. [Understanding SC 1.4.10: Reflow](<https://www.w3.org/WAI/WCAG22/Understanding/reflow.html>) — W3C Web Accessibility Initiative · Accessibility guidance
3. [Responsive Web Design and User Experience](<https://www.nngroup.com/articles/responsive-web-design-definition/>) — Nielsen Norman Group · Professional article

## Related topics

- [Adaptive Design](<https://wiki.soroush.uk/topic/adaptive-design/>)
- [Grid System](<https://wiki.soroush.uk/topic/grid-system/>)
- [Accessibility](<https://wiki.soroush.uk/topic/accessibility/>)
