Push Notifications in Mobile Apps: When to Send Them and How to Build Them
When push notifications are worth sending, when to ask for permission, Apple's rules on marketing pushes, and how APNs, FCM, tokens and deep links work.
When should your app use push notifications?
Use push when something has changed that the user would want to know about before they next open the app: an order shipped, a payment failed, a message arrived, an appointment is soon, a security event happened on their account. Those notifications are expected and tend to stay switched on. Push becomes a problem when it is used to pull people back into the app for your reasons rather than theirs: generic reminders, promotions sent to everyone, or several alerts about the same thing. That is when people mute the app, turn off notifications or uninstall it.
Three rules follow. Ask for permission when the user can see the value, not on first launch. Keep marketing separate from service messages, and on iOS send marketing only to people who explicitly opted in, with an in-app way to opt out (Apple's App Review Guideline 4.5.4). And treat every opt-out as feedback about what you sent.
The first half of this page is the strategy: when to ask, what to send and how to tell if it is working. The second half covers implementation with APNs, FCM, tokens, payloads and deep links.
Key takeaways
- Push is worth it for timely, personal, expected information; it is a liability as a generic re-engagement tool.
- iOS shows its permission prompt once; use an in-app explanation first so you do not waste it.
- Android 13+ needs the POST_NOTIFICATIONS permission, and notifications are off by default for new installs.
- Marketing pushes on iOS need explicit opt-in and an in-app opt-out, and must never use the Time Sensitive level.
- Separate categories and channels so people can keep service messages and mute promotions.
- Watch opt-outs, permission changes and invalid tokens by message type, not just open rates.
When push is worth it, and when it becomes a problem
A useful test is whether the user would be annoyed not to receive the notification. If yes, it is probably worth sending. If they would never notice its absence, it is probably noise.
Push tends to earn its place in apps with real events: commerce and delivery, bookings, payments and banking, messaging, collaboration and anything with deadlines. It is weaker in apps where nothing changes unless the user acts, where the honest answer to "why are we sending this?" is engagement targets. In those apps, in-app messages, email or a better home screen may do the job without spending the user's trust.
Push is also not a delivery guarantee. Users can switch it off, the operating system can delay or group it, and Apple's guideline says push notifications must not be required for the app to function. Anything critical, such as a receipt or a password reset, needs another channel too.
When to ask for permission
On iOS, Apple's documentation says: "The first time your app makes this authorization request, the system prompts the person to grant or deny the request and records that response. Subsequent authorization requests don't prompt the person." A refusal sends people to Settings if they change their mind. Apple recommends making the request "in a context that helps people understand why your app needs authorization", for example after someone schedules their first task. For camera, location, contacts, tracking and the other permissions, see 15 mobile app permissions and when to request them.
That is why many apps show a pre-permission prompt first: an honest in-app screen that explains what you will send and why, with "Turn on notifications" and "Not now". Only a yes triggers the system dialog. A no costs nothing, and you can offer again at a better moment. Keep it plainly your own screen, not something styled to look like the system alert.
iOS also offers provisional authorisation: notifications are delivered quietly to Notification Center without a prompt, and people choose to keep or turn them off when they see one. Apple notes you can request this at first launch, because no prompt is shown. It suits apps whose value is easier to show than to describe.
On Android 13 (API 33) and later, POST_NOTIFICATIONS is a runtime permission and notifications are off by default for new installs. Apps that target Android 13 or later decide when the dialog appears; Android's guidance is to ask from a user action. Apps that target Android 12L or lower get the dialog when they create their first notification channel, and one "Don't allow" blocks the prompt until the app is reinstalled or updated to target Android 13. Existing eligible apps keep permission when the device upgrades, and media session notifications are exempt.
| Situation | What to do |
|---|---|
| User has just done something with an obvious follow-up (placed an order, booked, sent a message) | Show the pre-permission prompt now, naming that update |
| First launch, no action yet | Do not ask. On iOS, consider provisional authorisation instead |
| User tapped "Not now" on your screen | Offer again at the next relevant action, not on every launch |
| User refused the system prompt | Do not nag. Show the state in in-app preferences, with a link to system settings |
| You want to send marketing | Ask separately, with explicit consent wording, after service permission is settled |
Transactional vs marketing notifications
Transactional notifications (order shipped, payment failed, appointment tomorrow, new message) respond to something the user did or is waiting for. Marketing notifications (offers, new features, re-engagement nudges) are your agenda. They need different consent, categories and limits.
Apple's App Review Guideline 4.5.4 is the rule to know: push notifications "should not be used for promotions or direct marketing purposes unless customers have explicitly opted in to receive them via consent language displayed in your app's UI, and you provide a method in your app for a user to opt out from receiving such messages." The same guideline says pushes must not be required for the app to function and should not carry sensitive personal or confidential information.
Apple's Human Interface Guidelines add detail. Before sending marketing, create "an alert, modal view, or other interface that describes the types of information you want to send and gives people a clear way to opt in or out". Provide an in-app settings screen where people can change that choice. And: "Never use the Time Sensitive interruption level to send a marketing notification."
Google Play does not have a direct equivalent of Guideline 4.5.4 that we could verify. Its Ads policy is about ads, not your own messages: ads must not imitate system notifications. On Android the practical control is notification channels, so put marketing in its own channel that users can switch off without losing order updates.
Worth noting
Store rules are not the only rules. General marketing, consumer and privacy laws in your markets may apply to promotional messages whatever the channel. We have not found push-specific consent rules that we could verify for each market, so confirm the position with counsel rather than relying on store policy alone.
Interruption levels and Android channels
On iOS, interruption levels decide how loudly a notification arrives. Use Time Sensitive only for events that are happening now or within an hour, as Apple's guidance puts it, and never for marketing. Critical alerts need a special entitlement from Apple and are meant for health and safety. On Android, each channel has an importance level that the user can change but your app cannot change after creating the channel, so plan channels before launch.
| iOS level | What it does | Typical use |
|---|---|---|
| Passive | Delivered quietly, viewed at leisure | Recommendations, digests, most marketing |
| Active (default) | Normal alert | Messages, order updates |
| Time Sensitive | Breaks through Focus and scheduled summary | Account security issue, delivery arriving now |
| Critical | Also overrides the Ring/Silent switch; needs an entitlement | Health and safety only |
Frequency, timing and quiet hours
There is no reliable universal frequency figure; the numbers in vendor blogs are illustrative. Start from the user's events, cap marketing per user per week, and test changes against opt-outs rather than opens alone. Apple's guidance is to avoid sending multiple notifications for the same thing, so collapse updates ("3 new messages" rather than three alerts) and cancel reminders when the user has already acted. For the settings users need to control all this, see 10 notification preference patterns.
Send in the user's local time zone, hold non-urgent messages during quiet hours, and schedule reminders close to the moment they matter. Segment by what people have done and said they want, not by sending everything to everyone. Store each user's category preferences on the server, so every sending system honours them.
Send or don't send: a decision table
Use this as a team rule when someone proposes a new notification.
| Message | Send? | Why |
|---|---|---|
| Order shipped, with tracking | Send | Expected, personal, timely |
| Payment failed or card expiring | Send | The user needs to act to keep the service |
| New sign-in from an unknown device | Send, Time Sensitive if urgent | Security; affects the user directly |
| Reply to the user's message | Send, grouped by conversation | Expected; collapse bursts |
| Appointment reminder | Send once, at a useful time | Cancel it if the user has already confirmed or cancelled |
| Price drop on an item the user saved | Send only to marketing opt-ins | Useful, but promotional |
| Weekly offer to all users | Don't send by push | Use email or in-app messages; or marketing opt-ins only, at the Passive level |
| "We miss you" after a few days away | Don't send | Your goal, not theirs; a common reason to turn notifications off |
| Anything containing health, financial or other sensitive detail in the text | Don't send that text | It can show on a lock screen; send a generic message and show detail in the app |
| The same update a second time | Don't send | Apple advises against multiple notifications for the same thing |
Notification policy template
Write one line per message type and keep it with the product spec. Fill the frequency cap and quiet hours with your own numbers and revisit them when opt-outs move.
| Type | Consent | iOS level | Android channel | Frequency cap | Opt-out location |
|---|---|---|---|---|---|
| Account and security | Notification permission | Active or Time Sensitive | Account, high importance | As needed | System settings |
| Transactional | Notification permission | Active | Orders or bookings | Per event, collapsed | In-app preferences and system settings |
| Reminders | Permission plus a user setting | Active or Passive | Reminders | Your cap | In-app preferences |
| Marketing | Separate explicit opt-in shown in the app | Passive or Active, never Time Sensitive | Promotions, low or default importance | Your cap | In-app preferences (required on iOS) and system settings |
Signals to watch: opt-outs and uninstalls
Open rates show whether a message was interesting. Opt-outs show whether it cost you the channel. Track, by message type and campaign: Push is only one lever; improving app retention without leaning on notifications covers the others.
- Permission status on each launch (granted, denied, provisional) and changes since the last session
- Category and channel opt-outs in your in-app preferences
- Marketing opt-in rate when you ask, and opt-out rate after each campaign
- Tokens the push service reports as invalid, which often follow an uninstall
- Uninstalls and churn in the days after a campaign, compared with a holdout group
- Support complaints and store reviews that mention notifications
Hypothetical example: a food-ordering app
Hypothetical example: a food-ordering app asks nothing at first launch. After the first order, a pre-permission screen says "Get updates when your order is accepted and on its way". Order updates go to an Orders channel at the Active level. Two weeks later, the app asks separately whether the user wants offers, with clear consent wording and a link to preferences. Offers go to a Promotions channel at the Passive level, are capped per week, and are held during quiet hours. The team reviews opt-outs per campaign; when one campaign doubles the Promotions opt-out rate, they stop that format rather than sending more.
How Push Notification Systems Work
The app registers with the operating system and receives a device token from APNs or FCM. It sends that token to your backend, linked to the user. When something happens, your backend builds a payload and sends it to the push service, which delivers it to the device. The OS displays the notification, and a tap opens the app to the relevant screen. For where this sits in the backend, see mobile app backend development.
APNs and Firebase Cloud Messaging
Apple Push Notification service is the only route for delivering notifications to iOS devices. Firebase Cloud Messaging delivers to Android and can also send to iOS by forwarding through APNs. Many teams use FCM as a single sending API for both platforms, but APNs credentials must still be configured for iOS. Current FCM sending uses the HTTP v1 API.
Device Tokens
Tokens identify an app installation, not a person. A user may have several devices, and tokens change after reinstalls, restores or at the service's discretion. Send the latest token to your backend at every launch, associate it with the signed-in user, remove it on logout, and delete tokens that APNs or FCM report as invalid.
Android vs iOS Considerations
| Area | iOS | Android |
|---|---|---|
| Delivery service | APNs | FCM |
| Permission | Required; prompt shown once; provisional option | Runtime permission on Android 13+; off by default for new installs |
| User categories | Notification settings per app; interruption levels | Notification channels per category (Android 8.0+); importance fixed by the app at creation |
| Rich content | Notification service and content extensions | Expanded styles, images, actions |
| Background data messages | Throttled; not guaranteed | Subject to battery optimisations |
Payloads and Deep Linking
Keep payloads small (both APNs and FCM cap payload size) and include a route or deep link identifying where the tap should go, plus an ID for analytics. Don't put sensitive personal data in the visible text, which can appear on a locked screen, and write a generic preview for when previews are hidden. The deep linking guide covers routing, including signed-out users and missing content.
Rich Notifications and Handling Taps
Images, action buttons and grouped threads make notifications more useful when they carry real information. Write short, specific text, lead with what changed, and make the tap destination obvious. For store-specific uses such as restock and price-drop alerts, see ecommerce app personalisation.
The app may be closed, in the background or in the foreground when a tap arrives. Handle all three. Route to the destination screen, prompt sign-in first if needed and then continue to the destination, and show a helpful state if the content has been removed.
Analytics and Delivery Failures
Track sends, delivery results reported by the push service, opens, the actions taken afterwards, and opt-outs by category. Log errors from APNs and FCM, remove invalid tokens, and alert on sudden drops in delivery that may signal expired credentials. See mobile app analytics for measuring impact beyond opens.
Common Mistakes
- Requesting permission on first launch without context, and losing the one iOS prompt
- Sending marketing to people who only agreed to order updates
- Marking promotions as Time Sensitive
- One Android channel for everything, so muting offers also mutes order updates
- Several notifications for the same event
- Never refreshing or cleaning up device tokens
- Taps that open the home screen instead of the relevant content
- Sensitive data visible on the lock screen
- Ignoring push service error responses
Conclusion
Push notifications work when the plumbing is reliable (tokens, payloads, error handling) and the content is timely, relevant and easy to control. Ask for permission in context, keep marketing separate and opt-in, use interruption levels and channels honestly, and judge success by opt-outs as well as opens. For the privacy declarations that sit alongside notifications, see mobile app data privacy before launch. ZSpace Labs works on mobile app development, including notification systems. For the wider build context, see the mobile app development guide.
Want to plan your notification and permission strategy?
ZSpace Labs is a remote-first technology studio that works with clients globally on mobile apps and permission and onboarding UX. If useful, we can go through your message types, consent screens and channels with you.
Sources
Apple: App Review Guidelines (4.5.4 Push Notifications); Human Interface Guidelines: managing notifications; Human Interface Guidelines: notifications; asking permission to use notifications.
Google: notification runtime permission; create and manage notification channels; Google Play Ads policy.
Accessed 14 October 2026. Platform rules change; check the current pages before relying on them.
Common questions.
Your backend sends a message to the platform push service, Apple Push Notification service for iOS or Firebase Cloud Messaging for Android, addressed to a device token. The service delivers it to the device, and the operating system displays it or passes it to the app.
Usually not. Apple recommends asking in a context that shows people why the app needs it, for example after they schedule their first task, and Android's guidance also suggests asking from a user action. The exception is iOS provisional authorisation, which can be requested at first launch because it does not show a prompt.
On iOS, the system prompt appears only the first time you request authorisation; after that, people must change it in Settings, so link them there from your in-app preferences. On Android, apps targeting Android 12L or lower get one prompt at first channel creation, and a single "Don't allow" blocks re-prompting until the app is reinstalled or targets Android 13 or later.
Only with explicit opt-in. App Review Guideline 4.5.4 says push notifications should not be used for promotions or direct marketing unless customers have opted in through consent language shown in your app, and you provide a way in the app to opt out. Apple's design guidelines also say never to use the Time Sensitive level for marketing.
An identifier issued by APNs or FCM for a specific app installation. Your backend stores it and uses it to address notifications. Tokens can change or become invalid, so they must be refreshed and cleaned up.
On Android 13 and later, apps must request the POST_NOTIFICATIONS runtime permission, and notifications are off by default for new installs. iOS has always required users to grant notification permission.
Yes. FCM can deliver to iOS by forwarding messages through APNs, which is still required. You need APNs credentials configured either way.
A message that carries data to the app without showing an alert, for example to trigger a background refresh. Platforms limit how often these are delivered and don't guarantee timing.
On Android 8.0 and later, every notification belongs to a channel, such as order updates or promotions. Users can control each channel separately in system settings, and the app cannot change a channel's importance after creating it.
There's no universal number. Send when there's something timely and relevant to that user, let users control categories and frequency, and watch opt-out and uninstall signals.
The app should open directly to the relevant screen using a deep link or route in the payload, handling cases where the user needs to sign in first or the content no longer exists.
Invalid or expired tokens, disabled permissions, battery optimisations, payload errors, rate limiting or misconfigured credentials. Log send results and remove tokens the push service reports as invalid.