What should product and design verify?
Product and design should verify that each core task has a clear compact, expanded and transition behavior before engineering begins the port.
- Rank journeys by user value and adaptation risk.
- Document hierarchy, reachability and continuity decisions.
- Include text scaling, reduced motion and assistive technology states.
What should engineering verify?
Engineering should verify lifecycle handling, state restoration, safe-region behavior, input focus and rendering budgets across every supported state.
- Remove hard-coded screen dimensions and orientation assumptions.
- Test backgrounding and interruption during transitions.
- Instrument layout shift, frame time, memory and failures.
What should QA include in the release matrix?
QA should include transition paths as first-class test cases because defects often appear while moving between states rather than after a layout has settled.
- Cover every start state, transition direction and interruption.
- Verify content continuity, controls and accessibility focus.
- TODO: Add verified iPhone Duo hardware, OS and simulator combinations.