Test on real devices
The physical-device pass that simulators and Expo Go cannot replace.
Use at least one current iPhone and one representative Android phone before release. Simulators are useful, but they cannot prove real camera, push, biometrics, purchase sheets, universal links, lifecycle, or device performance.
Ask your AI to run the matrix
Read agent-skills/test-on-device.md. Create a device test sheet for the exact
development and preview builds I give you. Walk me through one scenario at a
time, record device/OS/build/result, and collect a screenshot or video for each
failure. Do not mark native behavior passed from a simulator.Core journeys
- clean install, upgrade, onboarding complete and skipped,
- auth success, wrong/expired OTP, OAuth cancel, sign-out, account switch,
- all four tabs, Activity, Scan cancel/result, Coach stream/stop,
- hard, soft, and promotional paywalls; purchase cancel; restore,
- notification permission and foreground/background/killed taps,
- deep links from browser/Notes, offline launch, background/resume, process kill,
- deletion, subscription-management separation, support/legal URLs.
Accessibility and environment
Repeat important journeys with large text, bold text, dark mode, reduced motion, VoiceOver/TalkBack, and a hardware keyboard where relevant. Test denied and revoked permissions, weak connectivity, interruption, and low-power mode.
The repository includes Maestro journeys in e2e/, but automation supports the
manual device pass; it does not replace judgment or store-sandbox verification.