---
title: How Do Push Notifications Work on iOS and Android?
description: Learn how push notifications work on iOS and Android, from server to screen, covering permissions, delivery, timing and rich media.
image: https://weareaffective.com/hubfs/learning-centre-images/how-do-push-notifications-work-on-ios-and-android.webp
---

[Skip to content](https://weareaffective.com/learning-centre/how-do-push-notifications-work-on-ios-and-android#main-content)

[![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com)

- [Home](https://weareaffective.com)
- About Us 
  
    - [Our Story](https://weareaffective.com/about)
    - [How We Work](https://weareaffective.com/how-we-work)
- Our Services 
  
    - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy)
    - [App Design](https://weareaffective.com/app-design-agency)
    - [App UX Design](https://weareaffective.com/app-ux-design)
    - [App UI Design](https://weareaffective.com/app-ui-design)
    - [App Technical Architecture](https://weareaffective.com/app-architecture)
    - [Existing App Audits](https://weareaffective.com/app-audit)
- [Case Studies](https://weareaffective.com/case-studies)
- [Pricing](https://weareaffective.com/pricing)
- [Learning Centre](https://weareaffective.com/learning-centre)

- [Get Started](https://weareaffective.com/get-started)

Expert Guide Series

# How Do Push Notifications Work on iOS and Android?

 Table of Contents

A push notification covers a surprising amount of ground before a phone buzzes. The message leaves your server, passes through a service run by Apple or Google, crosses a mobile network, and then arrives at an operating system that gets the final say on whether the person is interrupted at all. Knowing how push notifications on iOS and Android actually work changes the decisions you make months before launch, because the platforms have different permission models, different grouping controls and different reasons for quietly dropping a message.

> A notification is a request to interrupt someone, and the operating system treats it that way too.

We spend most of our time on the human side of this, because the technical side is well documented and [the emotional side almost never is](https://weareaffective.com/user-psychology-app-design). A notification lands in someone's pocket while they're cooking, driving, working or trying to sleep. The same message sent at two different moments produces two completely different feelings about your brand.

So this piece covers both. What the plumbing does, platform by platform, and what we've learned about asking for push notification permission, grouping messages into categories people actually want, and timing them so they read as help rather than noise.

## What Happens Between Pressing Send And The Phone Buzzing

Your app doesn't send notifications. Your server sends them to Apple or Google, and Apple or Google send them to the phone. That one detail explains most of what follows, including why delivery is never fully in your hands.

1. The app asks the operating system to register for remote notifications when it first runs.
2. The operating system talks to Apple's or Google's push service and gets back a token, which works like a postal address for that one app on that one device.
3. The app sends that token to your server, where it's stored against the user account.
4. Your server posts the message and the token to Apple's or Google's service over a secure connection.
5. That service finds the device on the connection it already holds open and passes the payload down.
6. The operating system decides how to display it, whether to make a sound, and whether to show it at all.

Tokens change more often than teams expect. They rotate when someone reinstalls the app, restores a phone from a backup, or moves to a new device. If your server never cleans out dead tokens, your sent numbers slowly drift away from the number of real people receiving anything, and your reporting starts flattering you.

The payload itself is small. A title, a body, a sound setting, a badge count and a handful of custom fields you define. Everything clever happens either side of that envelope.

## How Push Notifications Work On iOS

On iOS, everything goes through Apple Push Notification service, usually shortened to APNs. Apple keeps a connection open to every iPhone that's switched on and has a network, which is why a notification can arrive in under a second even when your app has been closed for a week.

Your server authenticates with APNs in one of two ways. The older route uses a certificate tied to a single app, and it expires every year, which is a quiet source of outages. The current route uses a signing key from your Apple developer account, which doesn't expire and works across apps. Use the key.

#### Permission comes first on iOS

Apple won't let you send anything visible until the user agrees. The system prompt appears once, and if someone taps don't allow, you can't show it again. Recovering that person means talking them into a trip to Settings, which almost nobody makes.

There's a softer route. Provisional authorisation delivers notifications quietly into Notification Centre with no prompt at all, and the user gets keep or turn off buttons on the message itself. It's a way of earning the decision with real examples rather than asking for it cold.

iOS also layers on Focus modes, scheduled summaries and interruption levels. A message marked time sensitive can break through a Focus, so long as the user has allowed that for your app. Everything else waits.

## UX/UI design built around *real* psychology

We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package.

[See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started)

No commitment

## How Push Notifications Work On Android

Android's equivalent is Firebase Cloud Messaging, or FCM. The shape is the same. Your app registers, gets a token, hands it to your server, and your server posts messages to FCM, which delivers them through the connection Google Play services already maintains with the device.

The real difference sits in how Android lets people manage what arrives. Since Android 8, every notification has to belong to a channel that you define, and each channel carries its own importance setting. The user controls sound, vibration, lock screen behaviour and blocking for each one separately.

> Android gives users a switch for every channel, so one bad category costs one stream, not all of them.

[The old shorthand that Android opts everyone in](https://weareaffective.com/learning-centre/what-happens-if-apple-or-google-changes-their-push-notification-rules) automatically stopped being true with Android 13. Notifications now need a runtime permission, like the camera or location, and you choose the moment the dialogue appears. That's more control than iOS gives you, and more rope.

#### Battery rules and manufacturer layers

Android devices sleep aggressively. Doze and app standby hold back normal priority messages until the phone wakes, and several manufacturers add their own power managers on top that close background processes more harshly than stock Android does. Marking a message high priority wakes the device, and overusing that flag gets your app throttled. Devices sold without Google services need a separate push service entirely, which is a build decision rather than a configuration one.

## iOS vs Android: The Differences That Change Your Strategy

The platforms diverge in ways that affect your product plan, not just your backend. Here's where they part company.

| Dimension | iOS | Android |
| --- | --- | --- |
| Permission prompt | One chance, denial is close to permanent | Runtime prompt since Android 13, still one real chance |
| Quiet delivery option | Provisional authorisation, no prompt | No direct equivalent |
| User controls | Per app, plus Focus and summaries | Per channel, set by your own taxonomy |
| Background behaviour | Consistent across devices | Varies by manufacturer power management |
| Rich content | Needs a notification service extension | Built into the notification styles |

#### Where push notifications on iOS and Android really split

Opt-in rates follow those rules closely. The overall figure sits at 67.5% across mobile apps, and the platform gap is wide, with roughly 43.9% on iOS against 91.1% on Android, according to [Mobiloud](https://www.mobiloud.com/blog/push-notification-statistics). Android's higher number is a product of its history rather than a sign that Android users want more messages.

So the practical effect is this. On iOS you're fighting for the permission itself, and every message afterwards is a vote on whether to keep it. On Android you'll have a larger audience with far more granular off switches, and people use them channel by channel as soon as a category stops being useful.

## Why Delivery Is Never Guaranteed

Both Apple and Google treat push as best effort. Neither promises that a message arrives, and both are explicit about it. If a device is offline, APNs holds the most recent notification for that app and drops older ones, so a run of five messages during a flight lands as one.

FCM works to a time to live value you set. Set it short and the message expires rather than arriving hours late. Collapsible messages replace each other, which is right for a score update and wrong for a one time code.

Things that stop a message reaching a human include a flat battery, a token that rotated after a restore, a Focus mode, a blocked channel, aggressive battery management on the device, or the user having turned your app off weeks ago and forgotten. Your dashboard can't see any of that.

Treat the sent count in your tool as accepted by Apple or Google, nothing more. Compare it against device level receipts from your SDK and against actual app opens, and you'll find the real delivery number is lower than the one you've been reporting.

This is why anything that genuinely matters needs a second route. Confirmations, security codes and anything with money attached belong in email or SMS as well, with push acting as the fast nudge rather than the system of record.

## Asking For Push Notification Permission Without Burning It

The single most useful change any product team can make is asking rather than telling. Instead of firing the system dialogue on first launch, say what you'd like to send and why, and let the person agree before the operating system ever gets involved. It's a framing and tone of voice change with no technical work behind it, and the response is reliably better, because [people who feel they have control over a product](https://weareaffective.com/learning-centre/when-users-blame-themselves-for-your-confusing-app-youve-already-lost-them) are more bought into it.

Running your own screen first also protects the one shot you get. If someone taps not now on your screen, nothing is lost and you can ask again after they've had more value from the app. If someone taps don't allow on Apple's screen, that door is shut.

Tie the ask to a moment where the notification is obviously useful, like just after someone saves an item, books something or completes a first order. Asking during onboarding, before anyone knows what your product does, is asking a stranger for their phone number.

Wording matters more than design here. Can we let you know when this is ready reads as a service. Enable notifications to get the most out of the app reads as a demand dressed up as advice. Say what will arrive, roughly how often, and what it's for.

On Android 13 and later, the same discipline now applies, because the prompt appears on your terms and carries the same weight as it does on iOS.

## Notification Categories And Granular Opt-Ins

A single on and off switch forces a bad choice. Someone who likes order updates but has had enough of promotions has one option, which is to turn the whole thing off, and you lose the useful messages along with the unwanted ones.

Android already assumes you'll break things up, because channels are required. The mistake we see is teams defining two channels, general and other, which hands the user a switch that does nothing meaningful. Build the channel list from the reasons people actually use the product, then let their behaviour in the app shape what sits in each one.

> Granular controls keep the conversation open when one category stops being welcome.

iOS gives you fewer system level controls, so the preference centre has to live inside your app. A short settings screen with four or five clearly named categories does the same job, and it gives you a place to send people from the notification itself.

Users do reach for these controls. Around 42% of people adjust their notification settings when an app sends too much, according to [Statista, 2021](https://www.statista.com/statistics/1242709/us-too-many-push-notifications-users-reaction/). Every adjustment is a person telling you something, and a granular setup lets them turn down one stream instead of walking away from all of them.

So the question for each message is whether the user asked for this kind of information, and whether it lines up with what they're using the product for.

## Timing, Context And Emotional Load: Lessons From A Concierge App

On a concierge app we built, we pushed for drip-fed, context-sensitive notifications instead of the default approach of giving people everything they needed upfront. The industry habit was to front-load the information and then stay quiet. We argued that the information should arrive in pieces, at the point each piece became relevant.

The client accepted the recommendation, and we tested it properly. [A/B testing and research with real users](https://weareaffective.com/learning-centre/what-are-the-different-types-of-mobile-app) showed that the group receiving the delayed, context-aware notifications reported measurably lower stress levels than the group that didn't.

What interested us most was how the messages were read. A notification arriving at the right moment wasn't taken as a warning or a demand. It was taken as the next bit of helpful information, arriving because it was needed. The mental model shifted from this app keeps bothering me to this app is looking after me, and that difference is what keeps people engaged over months rather than days.

Timing also shows up in open rates. Sending inside someone's preferred window lifts opens by up to 40%, according to [Wisernotify](https://wisernotify.com/blog/push-notification-stats/), though we'd argue the stronger case is the emotional one. A message that lands when someone is busy, stressed or asleep costs you more than a missed tap.

So design the sequence around the state the person is in, rather than around what your database happens to know first.

## Silent Pushes, Rich Media And Deep Links

Not every push needs to make a sound. Silent notifications, called content available on iOS and data messages on Android, wake the app in the background so it can fetch new content before the user opens it. The app feels current when it's launched, and nobody was interrupted to make that happen.

Both platforms limit them. iOS throttles silent pushes based on how the user engages with your app, and Android holds data messages during Doze unless they're marked high priority. Treat them as a nice improvement rather than a reliable delivery channel.

Rich notifications carry images, and on iOS that needs a notification service extension in the build, which also lets you decrypt or alter content before it appears. Android handles images through its own notification styles. [For a fashion or home interiors app](https://weareaffective.com/learning-centre/fitness-app-trends-2026-what-users-really-want-from-their-workout-apps), a product image in the notification does more than any amount of copywriting, and it's worth the extra build time.

Map every notification type to a specific screen before you write any of them. A message about an order that opens the home screen makes the person do the work twice, and that's the exact feeling that gets apps turned off.

Deep links are the part teams leave until last and then regret. Each notification carries a destination in its payload, the app reads it on open, and the person lands where the message was about.

## What To Decide Before Development Begins

Notifications get treated as a feature to add later, which is how apps end up with a single channel, no preference screen and a permission prompt on the splash screen. These decisions belong in the design phase, because they shape the data model and the onboarding flow.

1. What each notification is for, and whether the user has asked for that kind of information.
2. The category list, which becomes your Android channels and your in-app preference screen.
3. The moment you'll ask for push notification permission, and what your own screen says before the system prompt appears.
4. Where each notification type deep links to.
5. Which messages need a backup route through email or SMS because delivery can't be assumed.
6. Whether you need a non-Google push service for devices sold without Play services.

Budget-wise, the server work and the token handling are modest. The cost sits in the content design and the testing, because writing fifteen notification types that each sound like a person rather than a system takes real time, and so does checking behaviour across manufacturers with different power management.

One useful test before any of it ships is to imagine the product as a person in the room doing the job your app does, then read each notification aloud in that voice. If that person wouldn't say it at that hour, in that tone, for that reason, the message needs rewriting.

## Measuring Whether Your Notifications Are Working

Open rate is the metric everyone reaches for, and on its own it misleads. Push open rates average around 4% in Customer.io's platform data, described there as normal rather than a failure, which you can read at [Customer.io](https://customer.io/learn/mobile-marketing/push-notification-metrics). Published averages vary wildly depending on what each platform counts as an open, so your own trend line is worth more than anyone's benchmark.

Track the opt-in rate by platform and by the screen where you ask, because that tells you whether your permission wording is working. Then track the opt-out rate per category, which tells you which stream has worn out its welcome.

> Watch what people switch off, not just what they tap on.

The engagement signals that matter sit further downstream. Session time after a notification, how often someone comes back without being prompted, [what gets said about the product on social](https://weareaffective.com/learning-centre/how-do-i-create-viral-social-media-content-for-my-app), and whether people recommend it. Those behaviours come from an emotional connection to a product, rather than from a message that happened to get tapped.

Uninstalls deserve a place on the same dashboard. A category that produces a good click rate and a rising uninstall rate in the same week is not performing, it's borrowing against the relationship.

## Conclusion

The mechanics of push notifications on iOS and Android are straightforward once you can see them. Your server hands a message to Apple or Google, they pass it to a device, and the operating system decides what the person experiences. Apple makes you earn permission once and keeps the controls simple. Android gives you a bigger opted-in audience and a switch for every channel you create.

Everything that distinguishes a good notification programme from an irritating one happens above that layer. Asking permission instead of demanding it. Breaking messages into categories people recognise. Sending the next piece of information at the moment it helps, rather than everything at once because the data was ready.

That was the finding from the concierge app we built. The group receiving drip-fed, context-aware notifications reported lower stress than the group that didn't, and the notifications stopped reading as alarms and started reading as help. Same technology, different intent.

If you're planning an app, or you've got one where the notifications are doing more harm than good, we're happy to look at it with you. [Let's talk about your notification strategy](https://weareaffective.com/get-started) and what it should feel like to be on the receiving end.

## Frequently Asked Questions

Does my app send push notifications directly to the user's phone?

No. Your server sends the message to Apple's or Google's push service, and that service passes it down to the device over a connection it already holds open. This is why delivery is never entirely in your hands, because the operating system still gets the final say on whether anything is shown.

What is a push token and why does it keep changing?

A token works like a postal address for one app on one device, and your server stores it against the user account so you know where to send messages. Tokens rotate when someone reinstalls the app, restores from a backup or moves to a new phone, so you need a process for clearing out dead ones. Without that, your sent numbers drift away from the number of people actually receiving anything.

Should I authenticate with APNs using a certificate or a signing key?

Use the signing key from your Apple developer account. It does not expire and it works across multiple apps, whereas the older certificate route is tied to a single app and expires every year, which is a quiet and very common cause of outages.

What happens if a user taps "Don't Allow" on the iOS permission prompt?

The system prompt only appears once, so you cannot show it again after a refusal. Your only route back is persuading the person to change the setting manually in Settings, and almost nobody does that, which is why the timing of the first ask matters so much.

What is provisional authorisation on iOS?

Provisional authorisation lets you deliver notifications quietly without showing the standard permission prompt first. It is a softer route that lets people experience the value of your notifications before deciding, rather than making them commit blind on first launch.

What should go in the notification payload?

The payload is deliberately small. It typically holds a title, a body, a sound setting, a badge count and a few custom fields you define yourself. Everything clever happens either side of that envelope, in your server logic and in how the operating system chooses to present it.

When is the best moment to ask for notification permission?

Ask at a point where the value is obvious, such as just after someone has done something that clearly benefits from a follow up message. Asking on first launch, before anyone understands what your app does, wastes the single chance iOS gives you.

Why does timing matter so much for notifications?

A notification is a request to interrupt someone, and it may land while they are cooking, driving, working or trying to sleep. The same message sent at two different moments can produce two completely different feelings about your brand, so timing is as much a design decision as the copy itself.

## Related Articles

[![The Difference Between What a Survey Captures and What a Session Recording Reveals in a Fashion Checkout](https://weareaffective.com/hubfs/learning-centre-images/the-difference-between-what-a-survey-captures-and-what-a-session-recording-reveals-in-a-fashion-checkout.webp)](https://weareaffective.com/learning-centre/the-difference-between-what-a-survey-captures-and-what-a-session-recording-revea)

### [The Difference Between What a Survey Captures and What a Session Recording Reveals in a Fashion Checkout](https://weareaffective.com/learning-centre/the-difference-between-what-a-survey-captures-and-what-a-session-recording-revea)

A fashion brand runs a post-purchase survey. The scores come back good. Customers say checkout was...

by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee)

[![How Do I Find Out What Price Users Will Pay for My App?](https://weareaffective.com/hubfs/learning-centre-images/how-do-i-find-out-what-price-users-will-pay-for-my-app.webp)](https://weareaffective.com/learning-centre/how-do-i-find-out-what-price-users-will-pay-for-my-app)

### [How Do I Find Out What Price Users Will Pay for My App?](https://weareaffective.com/learning-centre/how-do-i-find-out-what-price-users-will-pay-for-my-app)

The short answer is that you find it out three ways at once, and you only trust the number when all...

by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee)

[![How Do I Choose the Right Font Size for My Mobile App?](https://weareaffective.com/hubfs/learning-centre-images/how-do-i-choose-the-right-font-size-for-my-mobile-app.webp)](https://weareaffective.com/learning-centre/how-do-i-choose-the-right-font-size-for-my-mobile-app)

### [How Do I Choose the Right Font Size for My Mobile App?](https://weareaffective.com/learning-centre/how-do-i-choose-the-right-font-size-for-my-mobile-app)

Take the app you're working on, step outside into bright sun, hold the phone at arm's length and...

by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee)

[![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com)

20-22 Wenlock Road  
London, N1 7GU  
United Kingdom

+44 20 4572 8062  
[hello@weareaffective.com](mailto:hello@weareaffective.com)

<https://linkedin.com/company/weareaffective> <https://instagram.com/weareaffective> <https://facebook.com/weareaffective>

Services

[App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit)

Legal

[Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70)

Case studies

[TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift)

About us

[Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work)

Guides

[Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth)

 Copyright © 2026, weareaffective.com. All rights reserved.