Push notifications without annoying users

Short version: push notifications are powerful and easy to abuse. The difference between re-engagement and uninstalls comes down to a few rules: make every notification relevant and timely, ask permission at the right moment, give users control, and always favour quality over quantity. A welcome notification brings people back; an annoying one loses them for good.

A push notification is one of the few ways to reach a user who isn't in your app. Used well, it re-engages people with something they're glad to see. Used badly, it's the fastest way to get muted or uninstalled. Here's how to stay firmly on the right side of that line.

Relevance is everything

The number-one reason people disable notifications is irrelevance — messages that don't matter to them. Every notification should be genuinely useful to that user: something happened they care about, an action they need to take, information they'd want. Blasting the same generic message to everyone is how you train people to ignore you. Personalise based on what the user actually does.

Timing and frequency

Send at sensible times. A notification at 3am, or one that interrupts constantly, breeds resentment. Respect the user's context.
Quality over quantity. There's no magic number, but the rule holds: fewer, better notifications beat a steady drip of noise. If it isn't worth the interruption, don't send it.
Don't repeat yourself. Nagging about the same thing is a classic uninstall trigger.

Ask permission the right way

Don't demand notification permission the instant someone opens your app, before they understand why they'd want it. Ask after they've seen some value, ideally in a moment where notifications obviously help ("Want a heads-up when your order ships?"). Explaining the benefit turns a reflexive "no" into a willing "yes."

Give users control

Let people choose what they hear about and how often. Granular preferences — rather than an all-or-nothing switch — mean users can keep the notifications they value and mute the ones they don't, instead of turning everything off (or leaving). Control keeps the channel healthy.

Every notification spends a little of the user's trust. Spend it only when you have something worth their attention.

Key takeaways

Make every notification relevant to that specific user.
Mind timing and frequency — quality beats quantity every time.
Ask permission after showing value, and explain the benefit.
Give users granular control so they mute noise, not everything.

Frequently asked questions

Why do users turn off notifications?

Because too many are irrelevant, poorly timed, or clearly just marketing. Once notifications feel like spam, people mute them or uninstall the app. Relevance and restraint are what keep the channel alive.

How often should an app send push notifications?

As often as it has something genuinely useful to say — and no more. There's no magic number; the right cadence depends on your app. The safe rule is quality over quantity: every notification should feel worth the interruption.

Should I ask permission before sending notifications?

Yes, and ask at the right moment — after the user sees value and in a context where notifications obviously help, not the instant they open the app. Explaining what they'll get in return dramatically improves opt-in rates.

ZIVARA designs engagement that respects users — notifications and flows that bring people back without wearing out their welcome. Let's talk. Related: onboarding flows that keep users.