Push opt-in timing in FTUE versus later sessions

Push permission is a one-shot system dialog on Apple platforms. Apple’s HIG Privacy guidance emphasises clear purpose and avoiding unnecessary prompts. Apple’s request-review documentation likewise advises against interrupting launch and recommends waiting for a completed positive sequence — useful timing hygiene even though it addresses reviews, not push.

Operator checklist

1. Pre-permission screen explaining the value (energy full, war start, event) before the system dialog.
2. Not at first cold launch unless the feature is unusable without push.
3. After a value moment (first clear, first clan invite, first energy empty).
4. Purpose string matches actual push categories.
5. Decline path: App remains usable; soft re-prompt via settings deep link only.
6. Analytics: Record auth status; do not treat provisional/denied as opted-in.
7. Live-ops dependency: Critical events must also surface in-session for denied users.

Limits

Android notification permission timing differs by OS version; confirm on current target API separately.

Download the evidence table.

Research checked 20 September 2026. Local draft; human editorial review pending. No CMS write performed.