impeccable-adapt-nativelisted

Adapt an existing **native** design (`ios` / `android` / `adaptive`) to a different context: another device class, orientation, platform, or origin. The trap is treating adaptation as scaling. The job is rethinking the experience for the new context, inside the platform conventions of the iOS platform reference / the Android platform reference; read the target platform's reference before planning if Setup hasn't already. ## Assess Adaptation Challenge 1. **Source context**: what was it designed for, and what assumptions did it make? (Phone-only? Portrait-only? One platform's idioms? A website?) 2. **Target context**: which device class (phone, tablet, foldable), orientation, platform, and usage posture (one-handed on the go vs two-handed at rest)? 3. **What breaks**: navigation that doesn't fit the target, layouts that stretch instead of restructure, gestures or controls that don't exist there? ## Adaptation Strategies ### Phone → Tablet (iPad / large screens) - **Restructure, don't stretch.** A scaled-up phone UI on a tablet is the failure mode. Use size classes (iOS) / window size classes (Android) to switch structure. - **Navigation changes shape**: tab bar stays or becomes a sidebar on iPad; Android navigation bar becomes a rail or drawer on expanded width. - **Use the width**: split view / master-detail (list + detail side by side), multi-column grids, popovers where phones used sheets. - **Multitasking is a size, not an edge case**: iPad Split View and Android mult