Push Notifications That Don’t Annoy Users: A Design Guide

Push notifications are the most abused channel in mobile. Treated as a quick growth lever, they reliably tank retention and drive uninstalls. Treated as a product feature, they become a competitive advantage.

The four kinds of useful pushes

• Transactional — order shipped, payment received, message from a known person.
• Personalised triggers — based on user behaviour or preferences they explicitly set.
• Timely value — weather alert, traffic update, price drop on a watched product.
• Re-engagement with clear context — “your draft is still saved”, not “we miss you”.

The kinds that destroy retention

Generic “X% off everything today” broadcasts. Re-engagement messages timed by days-since-open rather than user signal. Repeated reminders for ignored notifications. Marketing dressed up as alerts. All four read as spam and trigger system-level mute or uninstall.

Design rules

Ask for permission only when the value is obvious — not at app launch. Use deep links so taps land on the relevant screen, not the home screen. Respect quiet hours (10pm-7am in user’s time zone). Cap volume to under five per day, even for power users.

Measurement

Track three things together: click-through rate, downstream action completion, and notification opt-out rate. A campaign with great CTR but rising opt-outs is failing — it borrows future engagement against today’s metric.

Permission strategy

Soft-prompt before the system prompt. Explain what you will send and why. Users who decline the soft prompt never see the system one, preserving your right to ask later when they are more engaged.