Notification Permission Timing, Explained: iOS Authorization and Android's POST_NOTIFICATIONS
How iOS records your first notification-permission answer and offers provisional trials, how Android 13's POST_NOTIFICATIONS runtime dialog works, and why the ask belongs in context, not at first launch.
The push notification permission prompt behaves differently depending on OS version and your target SDK: iOS records the first answer and stops prompting, Android's rules hinge on your target version, and on both platforms the road back runs through system settings. A careless "ask on first launch" spends that goodwill before the user has any reason to say yes. iOS and Android now treat this moment differently enough that one flow no longer fits both.
iOS: one recorded answer, and a trial mode
On iOS you ask through UNUserNotificationCenter's requestAuthorization, naming the interaction types you actually use - alerts, sounds, badges. The mechanics are unforgiving by design: the first time your app requests authorization, the system prompts and records the person's response, and subsequent requests do not prompt again. Apple's own guidance is to make the request in a context that explains itself - a task app asks after the user schedules their first task, not at first launch, because people grant what they can see the purpose of. iOS also offers an escape hatch Apple explicitly recommends for the not-sure-yet user: provisional authorization, which sends notifications on a trial basis (quietly, to the notification center) so people can judge your notifications before you ever show the dialog. Between those two levers - ask in context, or trial provisionally first - "we prompt at onboarding because that's when everyone is there" stops being a reason and becomes a choice with a measurable cost.
Android 13+: a real runtime permission, with a trap for old targets
Since Android 13 (API level 33), posting notifications requires the runtime permission POST_NOTIFICATIONS, declared in the manifest and requested like any other runtime permission. The dialog gives the user three outcomes: Allow (all your notification channels work), Don't allow (all notification channels blocked, except for a few specific roles, per Google's wording - and the user can still reverse it in system settings), or swiping the dialog away without answering. The trap is in the targeting: Google warns that if your app targets 12L (API 32) or lower and the user taps "Don't allow" even once, they are not prompted again until they uninstall and reinstall, or you update the app to target Android 13 or higher. So the old "we'll ask later" posture has an expiry date. Two details worth keeping straight: a foreground service does not need POST_NOTIFICATIONS to launch, but it must still show a notification as before; and the permission governs non-exempt notifications, so the exemption list matters if your app has system-adjacent roles.
Designing the ask across both platforms
The shared principle is that first answers carry weight - iOS does not prompt again after the first recorded response, Android guarantees the in-context ask only when you target API 33+ (on older targets one denial ends prompting until reinstall or retarget), and system settings are the recovery path everywhere - so context is what buys a yes. On iOS, decide between an in-context explicit ask and a provisional trial that lets your notifications earn the dialog. On Android, move to targeting API 33+ so a denial does not become permanent-by-accident, and request the permission when the feature that needs it is in front of the user. On both, the pre-prompt screen (your own explanation shown before the system dialog) is the industry-standard way to defer the official ask until the user has already said "this seems useful" once - and both platforms let you measure the result, so treat grant rate as a first-class metric rather than a surprise.
A short checklist
- iOS: request only the options you use, ask in context, and consider provisional authorization before ever showing the dialog; remember the first recorded answer stands.
- Android: declare POST_NOTIFICATIONS, target API 33+, know the three dialog outcomes, and remember the 12L-or-lower one-tap-permanence trap.
- Both: never ask at first launch without a reason on screen; track grant rate as a metric; have a quiet-channel plan (in-app inbox, badges) for the users who say no.
The honest summary
Both platforms made notification permission a considered user choice, and both made the first answer hard to undo. The apps that keep their push channel are the ones that treat the prompt as something to earn - in context on iOS, with a trial mode when unsure, and with a modern target on Android before the dialog's rules harden against them.
Sources
- Apple Developer Documentation: Asking permission to use notifications
- Android Developers: Notification runtime permission
Prepared with AI assistance and reviewed before publication. Permission behavior and API details are drawn from the source pages above, checked on 19 November 2026.