# Adaptive Design

Adaptive design selects or composes distinct layouts and behaviors for meaningful device, window, input, or task contexts rather than merely scaling.

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

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

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

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

## How it works

1. Identify contextual differences that change the task, not only pixel width.
2. Define a small set of coherent modes and rules for entering or leaving each one.
3. Keep terminology, data, permissions, and core capabilities consistent across modes.
4. Preserve state, focus, and unfinished work when the layout changes.
5. Test transitions between modes, external displays, zoom, keyboard, touch, and assistive technology.

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

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

## Visualization

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

## Sources

1. [Layout](<https://developer.apple.com/design/human-interface-guidelines/layout>) — Apple Human Interface Guidelines · Institutional guideline
2. [Mobile Sites vs. Apps: The Coming Strategy Shift](<https://www.nngroup.com/articles/mobile-vs-responsive/>) — Nielsen Norman Group · Professional article
3. [Responsive design](<https://developer.mozilla.org/en-US/docs/Learn_web_development/Core/CSS_layout/Responsive_Design>) — MDN Web Docs · Technical documentation

## Related topics

- [Responsive Design](<https://wiki.soroush.uk/topic/responsive-design/>)
- [Grid System](<https://wiki.soroush.uk/topic/grid-system/>)
- [Progressive Disclosure](<https://wiki.soroush.uk/topic/progressive-disclosure/>)
