A one-time question
On iOS and Android 13+ (Google, n.d.) notification consent comes via a system dialog; after a denial apps can rarely show it again, so it is effectively one chance. Felt et al. (2012) found many users barely read or understand permission screens, so the context and explanation before the dialog decide the outcome.
When and how to ask
Apple (n.d.) advises asking when the permission is needed, with a reason; per Fogg (2009) the moment motivation appears is the best prompt, such as offering shipping alerts right after an order. A pre-permission screen explaining what and how often, with a 'later' option, protects the single system dialog; design it with app onboarding. Because privacy choices are swayed by framing (Acquisti et al., 2015), avoid shaming dark pattern copy.
After allow and after deny
Pielot et al. (2014) logged dozens of notifications per day, and Mehrotra et al. (2016) found mismatched content and context get ignored or annoy. Send only promised types and allow per-type opt-outs. For users who declined, quietly note on relevant screens that they can enable it in settings, and use toasts or badges in-app.
FAQ
- Why not ask at first launch?
- Users do not yet see the value, deny easily and cannot easily be asked again.
- Can you ask again after denial?
- Rarely via the system dialog; guide users to settings from relevant screens.
Sources reviewed: 2026-10-27
References
- Felt, A. P., Ha, E., Egelman, S., Haney, A., Chin, E., & Wagner, D. (2012). Android permissions: User attention, comprehension, and behavior. In Proceedings of the Eighth Symposium on Usable Privacy and Security (Article 3, pp. 1–14). ACM. Users rarely read or understand permission prompts.
- Pielot, M., Church, K., & de Oliveira, R. (2014). An in-situ study of mobile phone notifications. In Proceedings of the 16th International Conference on Human-Computer Interaction with Mobile Devices & Services (pp. 233–242). ACM. Field study of daily notification volume and reactions.
- Mehrotra, A., Pejovic, V., Vermeulen, J., Hendley, R., & Musolesi, M. (2016). My phone and me: Understanding people's receptivity to mobile notifications. In Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems (pp. 1021–1032). ACM. Receptivity depends on content, sender and context.
- Acquisti, A., Brandimarte, L., & Loewenstein, G. (2015). Privacy and human behavior in the age of information. Science, 347(6221), 509–514. Privacy choices are swayed by context and framing.
- Fogg, B. J. (2009). A behavior model for persuasive design. In Proceedings of the 4th International Conference on Persuasive Technology (Article 40, pp. 1–7). ACM. Motivation, ability and prompt must align.
- Google. (n.d.). Notification runtime permission. Android Developers. Android 13+ runtime notification permission.
- Apple. (n.d.). Privacy. Human Interface Guidelines. Request permissions in context with a reason.