
Prototype review
Test navigation and task flow with intended users. Feedback on a simple prototype can prevent expensive revisions later. Keep enough history to separate a planned test from an unrelated change.
List camera, notifications, location, offline, and accessibility needs. Request permissions only when the feature requires them. Separate essential work from optional additions in the proposal.
- A written brief
- Named responsibilities
- Agreed review points




