Push Notifications: What to Send, When, and How Often

Push Notifications: What to Send, When, and How Often

Send push notifications that users would be annoyed to miss: an order status, a booking reminder, a security alert, something they explicitly asked to be told about. Send them when they are relevant – in the user's local time, close to the event – and send fewer than you think you can. Marketing messages need explicit consent: on iPhone it has to be requested in your app's interface, with an in-app way to opt out. Users can switch notifications off in a few taps, so every message tests whether the app deserves to keep that permission.

Why the permission is precious

Apple's design guidelines say you "need to get permission before sending any notification", and people can change that decision in settings at any time. On Android 13 and later, notifications for newly installed apps are off by default until the user grants permission. Android users can also see how many notifications an app sends each day and revoke the permission whenever they like. The permission is easy to lose and hard to win back.

What to send

TypeExamplesNotes
TransactionalOrder confirmed or shipped, booking reminder, payment received, password changedThe core use of push; users expect these.
Requested by the userPrice drop on a saved product, a new match for a saved search, a reply to their messageValuable because the user chose them – let them choose by topic.
Product newsA new feature they would actually useRarely, and only if relevant to how they use the app.
MarketingOffers, discounts, campaignsOnly with explicit opt-in and an in-app way to opt out.

NN/g describes transactional notifications as tied to an existing order or customer relationship, and notes that users expect notifications to be "more concise, timelier, and only for urgent content" than email. Push has limits too: according to NN/g it displays only 50–240 characters, can be cleared with a single tap and depends on connectivity. Information people must keep, such as a pickup code, is better sent by SMS.

What not to send

  • Sensitive information. Apple's App Review Guidelines say push notifications "should not be used to send sensitive personal or confidential information". Assume someone else may see the screen: write "Your test results are ready", not the results.
  • Marketing without consent. The guidelines allow promotional push only when customers "have explicitly opted in to receive them via consent language displayed in your app's UI", and you provide an in-app way to opt out. Apple's design guidelines add that you must also provide an in-app settings screen where people can change their choice.
  • Anything the app can't work without. Push notifications "must not be required for the app to function". If someone declines, the app must still work.
  • Repeats and bursts. Resending the same reminder because the user didn't react, or sending several messages in a row, is a quick route to the off switch. NN/g recommends combining several pending notifications into a single message.

When to ask for permission

Not at first launch. NN/g lists asking at first launch among five mistakes in designing push notifications, and Android's guidance is to let people get familiar with the app first, then ask at a moment that makes the benefit obvious – when they tap a bell icon, follow something or submit an order. Explain what kinds of notifications they will get, and why that helps them, before the system dialog appears; Google notes that users are more likely to grant permission when your intentions are transparent.

When to send

  • Close to the event. A reminder the evening before, or an hour before a booking, is useful; one sent days earlier is easily forgotten.
  • In the user's local time. Schedule by the user's time zone, not your server's, and keep non-urgent messages out of the night.
  • At the right urgency. On iPhone, notifications can be passive, active, time-sensitive or critical. Apple says to use Time Sensitive "only for notifications that are relevant in the moment" – an event happening now or within an hour – and never for marketing; critical alerts are reserved for urgent health and safety information. People can also choose to receive notifications in a scheduled summary rather than immediately, so write non-urgent messages that still make sense hours later.
  • By type, so users can choose. Since Android 8.0, every notification belongs to a channel, and users control each channel's behaviour. Google recommends a channel for each type of notification. Separate "Order updates" from "Offers", and users can silence offers without losing order updates.

How often

Neither Apple nor Google publishes an ideal number, and any universal figure would be a guess. What the guidelines and research agree on:

  • transactional messages follow real events – one order, a few status updates;
  • messages the user didn't ask for should be rare and clearly relevant to them;
  • several pending messages should be combined into one;
  • the user, not the app, decides what they receive.

Set your own limit – for example, a maximum number of non-transactional messages per user per week – and enforce it in the system that sends them, not just through good intentions. Then measure how many people grant permission, how many open notifications, and how many switch off a category or all notifications after a campaign. A rising opt-out rate means you are sending too much, or the wrong things.

Writing a good notification

  • Start with what happened: "Your order 1042 is on its way", not "Great news!".
  • Keep it short – long text gets cut off.
  • Make a tap open the relevant screen, such as the order or the booking, not the home screen.
  • Write in the language the user has chosen in the app.

Settings inside the app

Give users a screen in the app where they choose what they receive, by type – matching your Android channels. NN/g recommends letting people edit notification preferences within the app rather than sending them to the phone's settings, and for marketing notifications on iPhone Apple requires it. A user who can turn off offers is less likely to turn off everything.

What it takes to build

Push looks simple but needs a server side: storing device tokens per user, deciding who gets which message, respecting time zones, preferences and limits, and logging what was sent. Automatic status updates also need a connection to the system that knows the status – your shop, booking system or CRM (see API integrations). If you are still deciding between an app and a website, we compared what each can do, notifications included, in Does Your Business Need an App or a Better Mobile Website?.

If you are planning notifications for a new app, or want to rethink the ones you send now, start with a list: which event triggers each message, who receives it and what they can do with it. We can help design and build the whole chain, from the permission prompt to the server that sends the messages, as part of our mobile app development service. Contact us.

Sources

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.