Introduction
For 14 years, every Android app could send you notifications by default. Install a weather app, and it could spam you with alerts. Install a game, and it could ping you hourly to “claim your reward.” The only way to stop it was to dig through Settings and disable notifications per-app.
Android 13 (2022) flipped the default. Apps had to request permission to send notifications — just like camera, microphone, and location. Users could say no at install time. Notification spam was no longer the default. It was opt-in.
How It Works
Apps targeting Android 13 (API 33) must request POST_NOTIFICATIONS permission. The first time the app tries to post a notification, a system dialog appears: “Allow [App] to send notifications?” Options: Allow or Don’t Allow.
If the user denies, the app cannot post notifications. Period. There’s no workaround, no alternative channel, no nag screen.
For apps targeting older API levels (32 and below), notifications are auto-granted on upgrade. But the first time the app is installed on an Android 13+ device, the permission dialog appears.
The Impact
The results were immediate:
- Notification spam dropped: Apps could no longer assume notification access. Spam apps lost their primary engagement channel.
- Permission requests became meaningful: Apps had to explain why they needed notifications. “We’ll send you updates about your order” is a reasonable request. “We’ll send you daily promotions” is not.
- User control increased: Users who wanted notifications from messaging apps and silence from everything else could have both.
Android 13’s notification permission was a long-overdue correction. Apps should earn the right to interrupt you.
References
- Android 13 notification permission documentation
- “Android 13: Notification Permission” (Android Developers Blog, 2022)