Adapt by capability, not device label
Components declare supported inputs, presentations, attention contexts, accessibility preferences, environments, and fallbacks.
Guidance
Preserve intent while adapting hierarchy and interaction; never assume hover, precision, motion, transparency, or a fixed viewport.
Do
- Publish a capability declaration and fallback
- Test compact, regular, assistive, localized, and degraded states
Do not
- Treat mobile, desktop, and spatial as scaled skins
Verification contract
capability declaration plus cross-input and adaptive-state tests
Supporting references
ref.apple.hig-accessibility— Apple HIG Accessibilityref.apple.hig-motion— Apple HIG — Motionref.apple.hig-spatial— Apple HIG Spatial Designref.apple.hig— Apple Human Interface Guidelinesref.google.android-adaptive-layout— Build adaptive apps — Android Developers