Adaptive Design
Adaptive design selects or composes distinct layouts and behaviors for meaningful device, window, input, or task contexts rather than merely scaling.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/adaptive-design/
01What it means
Adaptive design changes an experience at defined conditions, sometimes selecting among purpose-built layouts or interaction modes. Conditions include available space, input, posture, platform convention, or task context. The goal is not to guess a device name, but to provide a coherent variant where continuous reflow is insufficient.[1][2][3]
- 01Fluid responseThe same composition resizes and reflows continuously
- 02Component adaptationIndividual controls change arrangement or density
- 03Layout modeA distinct composition serves a meaningful width or task context
- 04Behavior adaptationInput, navigation, or interaction changes with capability
- 05Context-specific experienceOnly justified when equivalent outcomes remain available
Breakpoints should follow content, task, input, and capability needs rather than named devices; one context must not lose essential access.
02Why it matters
Different contexts can require more than smaller dimensions: a wide workspace may support persistent tools, while compact touch needs larger targets and a focused sequence. Deliberate adaptation improves efficiency and clarity while preserving the same content, permissions, and conceptual model.
03When to use it
Use adaptive design when a task benefits from materially different composition or behavior across contexts, such as dense authoring, foldable postures, kiosk use, or platform-specific navigation. Combine it with responsive behavior inside each variant.
04How it works
- Identify contextual differences that change the task, not only pixel width.
- Define a small set of coherent modes and rules for entering or leaving each one.
- Keep terminology, data, permissions, and core capabilities consistent across modes.
- Preserve state, focus, and unfinished work when the layout changes.
- Test transitions between modes, external displays, zoom, keyboard, touch, and assistive technology.
05A practical example
A mail app uses a three-pane workspace when space allows and a single-pane sequence when compact. Both share folders, search, actions, and URLs. When the window narrows, the open message stays selected and focus moves predictably rather than resetting to the inbox.
06Where it breaks
Each variant increases design, testing, and maintenance cost. Device detection and user-agent assumptions age badly, while abrupt changes cause lost context or focus. Adaptation should not remove essential functionality or create a second-class version for smaller windows.
Common mistakes
- Equating adaptive design with brittle user-agent detection
- Removing core actions from compact variants
- Resetting navigation, focus, or drafts when crossing a mode
07Sources
- LayoutApple Human Interface Guidelines · Institutional guidelineLayout
- Mobile Sites vs. Apps: The Coming Strategy ShiftNielsen Norman Group · Professional articleMobile Sites vs. Apps: The Coming Strategy Shift
- Responsive designMDN Web Docs · Technical documentationResponsive design