The short answer
- Push notifications are sent from your server through Apple Push Notification service on iPhone and Firebase Cloud Messaging on Android, and current versions of both ask the user’s permission.
- Ask for permission at a moment when the benefit is obvious, because on iPhone a refusal can only be reversed in the Settings app.
- Treat marketing notifications like marketing email, with clear opt-in consent that is separate from the system permission and easy to withdraw in the app.
Push notifications people keep switched on are timely, specific to them and expected, and they are split by type so each person can choose what they receive. A push notification is a short message sent from your server to an app on someone’s phone, which appears even when the app is closed. Ask for permission when the value is obvious, send transactional messages that save people effort, and treat marketing as a separate, opt-in category.
How push notifications work
When an app is set up for notifications, the phone gives it a device token, a long identifier that addresses that app on that device. The app sends the token to your server. To send a notification, your server passes the message and the token to the platform’s delivery service, which delivers it to the phone.
- APNs, the Apple Push Notification service, delivers notifications to iPhone and iPad apps.
- FCM, Firebase Cloud Messaging, is Google’s service for Android. It can also send to iOS apps, by passing messages on to APNs, and to web browsers.
Tokens change when an app is reinstalled or a phone is restored, and both services tell your server when a token is no longer valid, so remove those promptly. A notification payload is small, around 4 KB, so it carries a short message and an identifier for the app to fetch the rest. Delivery is best effort. A notification should never be the only place an important message lives, and a booking confirmation, for example, should also be visible in the app and sent by email.
Transactional and marketing notifications
Every notification you plan should fall into one of two groups, because the rules and people’s tolerance differ for each.
| Transactional | Marketing | |
|---|---|---|
| Purpose | Tells someone about something they did, asked for or are directly involved in | Promotes products, offers or more use of the app |
| Examples | Booking confirmed, lesson starting soon, job assigned to you, payment failed | A sale, a new feature to try, a message to people who have not opened the app recently |
| Permission needed | The system permission | The system permission plus separate marketing consent |
| Default setting | On, with a switch per category | Off until the person opts in |
| What goes wrong | Late, duplicated or sent at night | Too frequent, irrelevant, or sent without consent |
Apple’s App Review Guidelines say push notifications must not be required for an app to work, should not carry sensitive personal or confidential information, and should not be used for promotions or direct marketing unless people have explicitly opted in through consent wording in the app, with a way to opt out in the app. Notifications also appear on the lock screen, where anyone nearby can read them. “Your lesson report is ready” is fine. The contents of the report are not.
When to ask for permission
On iPhone, the system permission prompt appears only once. If the person taps Don’t Allow, the app cannot ask again, and the only way back is through the Settings app. Since Android 13, Android also asks for permission before an app can show notifications, and after repeated refusals the prompt stops appearing.
That makes timing the most important decision. Asking on first launch, before the person has seen what the app does, invites a refusal. Ask at the moment the benefit is clear, such as straight after someone books a lesson or is assigned their first job. A short screen in your own design can explain what you will send before the system prompt appears, so the person knows what they are agreeing to.
iPhone also offers provisional authorisation, which delivers notifications quietly to Notification Centre without asking first. The person sees them there and decides whether to keep them. It suits apps whose value is easier to show than to explain.
Giving people control over notifications
People are more likely to switch everything off when the only choice is all or nothing. Give them categories and sensible limits.
- Per-type settings in the app. Booking reminders, messages, reports and marketing as separate switches.
- Android notification channels. Since Android 8, each notification belongs to a channel that the person can silence or adjust in system settings. Match the channels to the categories in your app.
- Interruption levels on iPhone. Mark only genuinely urgent messages as time-sensitive, so they can break through Focus. Critical alerts that ignore the mute switch need a special entitlement from Apple.
- Quiet hours. Hold non-urgent messages overnight in the person’s own time zone, and batch low-priority updates into a daily digest.
- Frequency limits. Cap how many messages one person can receive in a day, across every feature.
Time zones need care. In CurioKids, bookings are shown in the family’s own time zone, and the same principle applies to any notification about a booking. A reminder calculated in the server’s time zone arrives at the wrong hour for a family abroad. The same care applies to any app built around a schedule, such as an event app.
Marketing notifications and UK law
Under the Privacy and Electronic Communications Regulations (PECR), unsolicited direct marketing sent by electronic mail, which covers email and text messages, generally needs the recipient’s prior consent, with a narrow exception for existing customers known as the soft opt-in. Whether a particular push notification counts as electronic mail under PECR depends on how it is sent and stored, and the position is less clear-cut than it is for email. UK GDPR applies either way, because the token and the data used to choose who gets a message relate to identifiable people.
The safe approach, and the one we’d recommend, is to treat marketing pushes as you would marketing email. Ask for marketing consent separately from the system permission, with plain wording about what you will send. Record when and how consent was given. Make it as easy to withdraw as it was to give, inside the app. Tapping Allow on a system prompt that says nothing about marketing is unlikely to count as consent to it. Take legal advice if marketing notifications are central to your plans.
Measuring whether notifications help
Measure each category separately, because a useful reminder and an unwelcome promotion can hide each other in an average.
- Permission rate. The share of people who allow notifications when asked, broken down by where in the app you asked.
- Opt-outs. How many people switch a category off, or disable notifications in system settings. The app can check its permission status each time it opens.
- Opens and actions. Taps on the notification, and whether the person then did the thing it was about.
- Outcomes. Fewer missed lessons, faster responses to assigned jobs, fewer failed payments left unresolved.
- Complaints and uninstalls in the days after a campaign.
Outcomes matter most. A notification that raises taps but also raises opt-outs is spending trust you will need for the messages that matter.
Questions people ask
Can a web app send push notifications on iPhone?
Yes, since iOS 16.4, but only once the web app has been added to the home screen and the person grants permission. A website open in a browser tab cannot send them. Our comparison of progressive web apps and native apps covers the other differences.
Do I need consent to send push notifications in the UK?
The phone’s own permission is needed for any visible notification. For marketing, get separate, clear opt-in consent, because PECR and UK GDPR may apply and Apple’s guidelines expect it. Transactional messages about something the person is doing do not need marketing consent.
How many push notifications are too many?
There is no fixed number. The right level depends on how useful each message is to the person receiving it. Watch opt-outs by category, and if one type of message is switched off more often than the rest, send it less often or stop.
Why are some push notifications not delivered?
APNs and FCM deliver on a best-effort basis. A phone that is off or without signal may receive a notification late, and when several are waiting, APNs keeps only the most recent one for each app. Invalid tokens, disabled permissions and Focus settings also stop messages appearing.