Push notifications: the strongest channel, and the fastest to lose
Direct access to someone's pocket is granted once. Once it is switched off it does not come back, and most apps spend it in the first week.
Notification permission is the most valuable thing a user gives you: direct access to their pocket.
And it is granted once. To turn it back on they have to open Settings, find your app and re-enable it. Nobody does that.
Do not ask on first launch
The most common mistake. The app opens, and before anyone understands what it does, the system dialog appears: "wants to send you notifications."
What the user is thinking is: I have no idea what this app will send me. So they tap Don't Allow.
Ask in a moment that has context instead:
- After placing an order: "shall we tell you when it ships?"
- After starting to track something: "notify you when the status changes?"
- After booking an appointment: "remind you the day before?"
At that point the user knows what they are agreeing to.
It also helps to put a step in front: explain in your own screen why you are asking, before the system dialog. If the user says "not now" there, the system permission is unspent and you can ask again later. If they decline the system dialog, that chance is gone.
Separate the types
A single "notifications" toggle forces the user to accept everything or nothing. They usually choose nothing.
These should be independently controllable:
| Type | Example |
|---|---|
| Transactional | Your order has shipped |
| Reminder | Your appointment is tomorrow |
| Social | You have a new message |
| Marketing | This week's campaign |
When someone tires of marketing notifications they should be able to turn off just that. Otherwise you lose the order notification too — which was the valuable one.
Timing
A campaign notification at 11pm can be the reason an app gets deleted. Respect the user's time zone and define quiet hours.
Also: do not send multiple notifications for the same event. Five messages should produce one summary, not five buzzes.
Content
Bad: "There's a new update!"
Good: a notification that informs without being opened, and that opens directly to the relevant screen when it is.
- "Your order has shipped — tracking no: 1234"
- Tapping it should land on the order detail, not the home screen
That last point is widely neglected. A user who taps a notification and lands on the home screen has to go find the thing themselves. They do not tap the next one.
What happens when permission is denied
Your app has to work without notifications. If critical information is only delivered by push, users who declined never receive it at all.
Keeping an in-app notification list rescues both the people who declined and the people who missed one.
Measure
Which type goes to how many people, how many tap it, and most importantly: after which notification do users turn permission off?
That last question is almost never asked. Its answer tells you directly which notification to stop sending.
In short
A notification is not a broadcast channel, it is a trust relationship. The user lets you into their pocket and expects something useful in return.
An app that breaks that balance loses the permission — and with it, the most effective tool it had for bringing people back.