A push notification is a message that an app’s server sends to your phone through Apple’s or Google’s push service, and that appears even when the app isn’t open: a new message, a delivery update, your team scoring. Apple’s service is Apple Push Notification service (APNs); Google’s is Firebase Cloud Messaging (FCM). You can turn notifications off for each app in Settings.
This guide follows Apple’s and Google’s own pages and the web standards, quoted and linked, as read on 10 November 2026. It starts with what you see: where notifications appear on iPhone and Android, how to turn them on or off, why apps ask first, and what web push is. Then, for app makers: how a push travels, when to ask for permission, and the App Store and Google Play rules.
What are mobile push notifications?
Mobile push notifications are the alerts, sounds and badges that apps on a phone or tablet receive from their servers. The meaning is in the word push: the app’s server decides when to send, and the message reaches your device even when the app isn’t running. Apple’s developer documentation puts it this way:
Use remote notifications (also known as push notifications) to push small amounts of data to devices that use your app, even when your app isn’t running. Apps use notifications to provide important information to users. For example, a messaging service sends remote notifications when new messages arrive.
Every push involves four parts: the app’s server, which Apple calls the provider server; the push service; your device; and the app on it. On Apple devices the push service is APNs. On Android, Google’s developer guide points to FCM, “a cross-platform messaging solution that lets you reliably send messages” to Android, Apple and web apps. Android defines what you then see as “a message that Android displays outside your app’s UI”: a reminder, a message from someone, or other timely information. A tap opens the app, and some notifications carry buttons that act without opening it.
Apple says the system makes every attempt to deliver notifications on time, “but delivery isn’t guaranteed.” A push can also arrive without showing anything, to tell an app to download new content and update itself. Websites can send push notifications too, through your browser; they have their own section below.
Push notifications vs local notifications: what’s the difference?
A local notification is created and scheduled by the app on your device; a push notification is created on a server and delivered by the push service. Apple’s framework handles both:
You can generate notifications locally from your app or remotely from a server that you manage. For local notifications, the app creates the notification content and specifies a condition, like a time or location, that triggers the delivery of the notification. For remote notifications, your company’s server generates push notifications, and Apple Push Notification service (APNs) handles the delivery of those notifications to the user’s devices.
Apple’s example of a local notification is one that the app asks the system to deliver “every Tuesday at 2pm”, with no server involved. Its example of a push is a messaging service telling you that a new message arrived. On your phone the two look alike and share one permission: Apple tells apps to check it before scheduling local notifications, and an Android app you refused can’t send notifications of either kind, apart from a few exempt ones such as media playback controls.
Where do push notifications appear on iPhone?
On iPhone, notifications appear on the Lock Screen, as banners while you use the phone, in Notification Center, as badges on app icons and, if you turn it on, in a scheduled summary. Unless a Focus silences them, iPhone shows them as they arrive, and you choose the places app by app.
- Lock Screen: new notifications “roll in from the bottom of the screen”. Pinch them to switch between a list, a stack and a count. Show Previews decides whether their text shows there: Always, When Unlocked or Never.
- Banners: a notification that arrives while you use another app shows as a banner. Tap it to view it, or swipe it up to dismiss it.
- Notification Center: the history of your notifications. Swipe down from the top-left corner of the screen, or swipe up from the middle of the Lock Screen.
- Badges: a number on the app icon. Apple’s design guidelines call it “a small, filled oval containing a number” that counts unread notifications.
- Scheduled Summary: the notifications of the apps you pick, delivered together at the times you set.
- StandBy and Apple Watch: “In iOS 17 and later, you can also view notifications while your iPhone is in StandBy”, and a paired Apple Watch shows them too.
A Focus, such as Do Not Disturb, Sleep or Work, keeps notifications quiet for a while without losing them: “the notification itself is available as soon as it arrives.” Apps give each notification one of four interruption levels, and two of them get through anyway. Here is what each level does in a Focus and when your iPhone is muted:
| Level | Focus | Muted |
|---|---|---|
| Passive | Silenced | Silent |
| Active | Silenced | Silent |
| Time Sensitive | Breaks through | Silent |
| Critical | Breaks through | Plays sound |
Time Sensitive is for information that needs your attention now, “like an account security issue or a package delivery”; it also skips the scheduled summary, and you can turn it off per app. Critical is for urgent health and safety information: an app needs a special permission from Apple, an entitlement, to send it, and you turn on Critical Alerts for each app that offers them. People and apps you allow in a Focus get through at any level.
On an iPhone 15 Pro, iPhone 15 Pro Max or iPhone 16 model or later, iOS can also use AI to summarize long or stacked notifications and to put time-sensitive ones first, in the languages and regions where Apple offers it.
Where do push notifications appear on Android?
On Android, a notification first appears as a small icon in the status bar at the top of the screen. Swipe down from there to open the notification drawer, where you read it in full, expand it and act on it; it stays there until you or the app dismiss it. Google’s developer guide lists the other places:
- Heads-up notification: an important notification can show for a moment in “a floating window” over the app you’re using, and it “only appears if the device is unlocked”.
- Lock screen: you choose how much detail shows, or hide notifications there altogether.
- Notification dot: on Android 8.0 and later, with launchers that support it, a dot on the app’s icon. Touch and hold the icon to see that app’s notifications.
- Watch: a paired Wear OS watch shows them too.
Each app sorts its notifications into categories, called channels in Android’s code, so you can silence one kind and keep another: in Google’s example, a payment app has one channel for withdrawals and one for deposits. Android 15 added notification cooldown, which “reduces the appearance, sound volume and vibration intensity for repetitive notifications for up to two minutes”; calls, alarms, priority conversations and emergency alerts are exceptions. Some phones also keep a notification history, with snoozed and recently dismissed notifications.
How do you turn push notifications on or off on iPhone?
On iPhone, each app has its own switch in Settings:
- Open the Settings app.
- Tap Notifications, then tap the app below Notification Style.
- Turn Allow Notifications off, or on.
The same screen decides how the app reaches you: Time Sensitive Notifications if the app uses them, Alerts (Lock Screen, Notification Center, banners), Sounds, Badges, Show Previews, and Notification Delivery, immediately or in the Scheduled Summary. Some apps add Customize Notifications, to pick which kinds you get, or a link to their own notification settings at the bottom.
You can also act from a notification: swipe left on it, tap Options, then choose Mute for 1 Hour, Mute for Today, View Settings or Turn Off. Muting “sends them directly to Notification Center”, so they stay off the Lock Screen and make no sound. iPhone may also suggest turning off notifications from an app you haven’t used for a while.
To be interrupted less, get some apps’ notifications in batches: open Settings, tap Notifications, then Scheduled Summary. Turn it on, set the times, then tap A to Z and choose the apps. To silence everything for a while, open Control Center, tap Focus, then turn on Do Not Disturb. To choose which people and apps get through a Focus, open Settings, tap Focus, tap a Focus, then People or Apps. Government alerts, such as emergency alerts, have their own section at the bottom of Settings, Notifications.
How do you turn push notifications on or off on Android?
On Android, open Settings, tap Notifications, then App notifications, tap the app and turn its notifications off or on. Google warns that “Settings can vary by phone”, so the names may differ on yours. Android Help gives three ways:
- In Settings: Notifications, then App notifications. Apps that sent notifications recently come first; choose All apps in the menu for the rest. Tap the app, then turn off all its notifications or only some categories.
- From a notification: swipe down from the top of the screen, touch and hold the notification, tap Settings, then turn off All notifications or only the kinds you don’t want.
- In the app: many apps have their own notification settings, for example to choose a sound.
On some phones, you can also make an app’s notifications Silent instead of Alerting: no sound or vibration, and they still show when you swipe down from the top of the screen. Under Settings, Notifications, Notifications on lock screen, you choose what the lock screen shows, sensitive content included. And since Android 13, an app you install starts with its notifications off until you allow them, as the next section explains.
Why do apps ask before sending notifications?
Apps ask because both systems leave the choice to you. Apple tells developers: “Because a person might consider notification-based interactions disruptive, you must obtain permission to use them.”
On iPhone, an app gets one chance to show the system’s prompt:
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.
So if you said no, the app can’t ask again: turn its notifications on in Settings. Some apps skip the prompt and send quiet trial notifications instead, which Apple calls provisional authorization. They arrive quietly, without a sound, a banner or a place on the Lock Screen, and appear only in Notification Center, with buttons to keep or turn off that app’s notifications.
On Android 13 and later, notifications need a runtime permission called POST_NOTIFICATIONS:
If a user installs your app on a device that runs Android 13 or higher, your app’s notifications are off by default. Your app must wait to send notifications until after you request the new permission and the user grants that permission to your app.
An app built for Android 13 or later picks the moment to ask; for an app built for older versions, the system shows the prompt itself, usually when the app starts. Swiping the prompt away leaves everything as it was. If you refuse a permission more than once, Android stops showing that prompt for the app, and for an app built for Android 12L or older, one refusal is enough. Apps already set up for notifications before your phone moved to Android 13 keep them, unless you had turned them off.
What are web push notifications?
Web push notifications are push notifications from a website or web app: the site’s server sends them through your browser’s push service, and they show like an app’s notifications, even when the site isn’t open. Apple describes web push as “push notifications that use the cross-browser Push API, Notifications API, Badging API, and Service Worker standards”. The W3C’s Push API sets out the idea:
The Push API enables sending of a push message to a web application via a push service. An application server can send a push message at any time, even when a web application or user agent is inactive.
The WHATWG’s Notifications API then defines how a page shows a notification outside its own window. Where it works, and how to control it:
- On a computer: by default, Chrome asks you whenever a site wants to send notifications. To change your answer later, open Chrome’s Settings, then Privacy and security, Site Settings, Notifications. There you can block or allow sites one by one, or turn on quieter messaging, which swaps the prompt for a bell icon next to the address. Chrome blocks notifications from sites that send intrusive or misleading ones and may remove the permission of sites you haven’t visited in a while; Google adds: “If you browse privately, you won’t get notifications.” Safari supports web push too, for “Webpages in Safari 16 for macOS 13 or later.”
- On Android: in Chrome, tap More, Settings, Site settings, Notifications, and use the switch at the top for all sites. For one site, open it, then tap More, Site controls, Permissions. On some devices, a site’s notification has its own Unsubscribe button.
- On iPhone and iPad: web push works for web apps on the Home Screen, since iOS and iPadOS 16.4. In Safari, open the site, tap Share, then Add to Home Screen, make sure Open as Web App is on, and tap Add. Since iOS 26, that option is on by default for every site you add. The web app can then ask to send you notifications after you tap something, such as its subscribe button, and you manage them in Settings, Notifications, like any app’s. A Focus can allow or silence a web app too.
Apple’s iPhone User Guide sums up the result:
When you tap the icon, the website opens just like an app. You can receive notifications from the web app and quit the web app like you would any app.
For site owners, the work follows the standards. The page subscribes the visitor after a click or a tap, stores the push endpoint and encryption keys with the account, and handles incoming pushes in a service worker; the server signs its requests with a VAPID key pair and sends them by the IETF’s web push protocol, RFC 8030. Apple’s service needs no membership: “You don’t need to join the Apple Developer Program to send web push notifications.” It does require every push to be shown, since “Safari doesn’t support invisible push notifications”: a site that receives a push without showing it loses its permission.
How do apps send push notifications?
A push takes four steps, on Apple’s service and on Google’s alike: the app gets an address from the push service, passes it to the app’s server, the server sends the message to the push service with that address, and the service delivers it.
- The app registers. At each launch, an iOS app asks APNs for its device token, “unique to both the device and your app”. An Android app gets an FCM registration token for its install; Firebase is moving these to Firebase Installation IDs and supports both in the meantime.
- The token goes to your server, which stores it with the person’s account, one per device. Apple warns: “Never cache device tokens in local storage.” A restored backup, a new device or a reinstalled system brings a new token. FCM calls a registration stale after a month without contact, and expires an Android one after 270 days of inactivity.
- Your server sends the message. For APNs, a POST request over HTTP/2 and TLS to
api.push.apple.com(api.sandbox.push.apple.comwhile you develop), authenticated with a token or a certificate, with a JSON payload. For FCM, the Firebase Admin SDK or the HTTP v1 API, from Cloud Functions for Firebase or your own server. - The service delivers it. If the device is offline, APNs keeps the notification “for 30 days or less”, depending on the expiration you set, and in most cases only the latest one per app. FCM sends a message when the device is online.
Each kind of device has its push service, and each service its own kind of address:
| Device | Via | Address |
|---|---|---|
| iPhone, iPad | APNs | Device token |
| Android | FCM | Registration token |
| Browser | Web push | Endpoint |
An app that uses FCM on iPhone still goes through Apple: you upload your APNs authentication key to Firebase, and FCM hands messages for Apple devices to APNs. On Android, FCM delivers through Google’s own transport layer, which Google restricts to approved Android devices with Google Play Services.
All three carry about 4 KB. APNs refuses a payload over 4 KB (4,096 bytes), or 5 KB for a VoIP call. FCM’s maximum is 4,096 bytes, or 1,000 characters from the Firebase console. And a web push service may not refuse a message of 4,096 bytes or less for its size.
Urgency is a setting. On APNs, apns-priority 10 sends the notification at once and is the default, 5 follows the device’s power considerations, and 1 puts power first. With FCM on Android, a normal-priority message may wait while the device is in Doze, and a high-priority one can wake it, though Google adds: “High priority messages generally should result in user interaction with your app or its notifications.”
To set this up on iPhone, enable the Push Notifications capability in Xcode and the push notification service for your App ID in your Apple Developer account; on Android, add Firebase to your project. Our guides to making an app and to Android app development cover the projects themselves. The same path also updates Live Activities on the Lock Screen and in the Dynamic Island, with the liveactivity push type, as our guide to Live Activities explains.
When should an app ask for permission, and what should it send?
Ask when the person can see why. Apple’s advice is to “Make the request in a context that helps people understand why your app needs authorization”: in a task app, after the person schedules a first task, rather than at first launch. Google’s Android guide says the same, with examples such as a tap on a bell button, following someone, or ordering food. On iPhone, provisional authorization lets people judge your quiet trial notifications before they decide.
Then, what to send, from Apple’s Human Interface Guidelines and Google’s Android guides:
- One notification per event. “Avoid sending multiple notifications for the same thing, even if someone hasn’t responded.” On Android, update the existing notification rather than posting a new one, or group them.
- Nothing private. “Avoid including sensitive, personal, or confidential information in a notification.” Apple’s payload guide adds that sensitive data you must send has to be encrypted first.
- Honest urgency. Keep Time Sensitive for “an event that’s happening now or will happen within an hour”. On Android, the importance of each channel (Urgent, High, Medium or Low) decides sound and pop-up, and once a channel exists, “The user has complete control at that point.”
- Categories. One Android channel per kind of notification lets people mute one kind instead of the whole app.
- Badges that count. Use a badge only for the number of unread notifications.
Promotions need consent, from Apple’s guidelines:
Don’t use notifications to send marketing or promotional content unless people explicitly agree to receive such information.
Apple also asks for an in-app settings screen where people can change that choice, and states: “Never use the Time Sensitive interruption level to send a marketing notification.” Its example of a promotion people might welcome is an offer to become a subscriber; our guide to in-app purchases covers how apps sell those.
What do the App Store and Google Play rules say about push notifications?
Both stores set limits: Apple’s rules forbid making notifications required, putting sensitive information in them, or sending promotions without consent, and Google Play allows system notifications only for an app’s integral features. Apple’s App Review Guidelines, last updated on 16 October 2026, give push notifications their own rule, 4.5.4:
Push Notifications must not be required for the app to function, and should not be used to send sensitive personal or confidential information. 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. Abuse of these services may result in revocation of your privileges.
Four more rules mention them. Rule 4.5.3 bans using Apple services, push notifications included, “to spam, phish, or send unsolicited messages to customers”. Rule 5.1.2 (i) says an app “may not require users to enable system functionalities (such as push notifications, location services, tracking)” to be used or to earn a reward. Rule 4.10 forbids monetizing built-in capabilities “such as Push Notifications, the camera, or the gyroscope”. And rule 2.5.18 keeps display advertising out of notifications.
Google Play states its rule in its Mobile Unwanted Software policy:
We don’t allow apps or ads that mimic or interfere with system functionality, such as notifications or warnings. System level notifications may only be used for an app’s integral features, such as an airline app that notifies users of special deals, or a game that notifies users of in-game promotions.
The policy’s example of a violation is a system notification used to serve an ad, and its checklist adds: “Don’t trigger notifications to promote a different app or a third-party service.” Google Play’s Ads policy also bans ads that imitate a notification. For apps that target Android 14 or later, full-screen intent notifications, meant for “high-priority messages that require the user’s immediate attention”, are granted by default only to apps whose core function is an alarm or phone and video calls. Other apps must ask the person, and no app may use them “to force user interaction with disruptive ads or notifications.”
What to do
On your phone:
- Turn off what you don’t read: on iPhone, Settings, Notifications, the app; on Android, Settings, Notifications, App notifications.
- Keep the useful kinds: turn off only some categories on Android, or use Customize Notifications on iPhone.
- Batch the rest in iPhone’s Scheduled Summary, or make them Silent on Android.
- Hide previews on the Lock Screen if other people see your phone.
- Refused by mistake: turn the app’s notifications on in Settings, since it may not be allowed to ask again.
- For websites, use Chrome’s site settings; on iPhone, add the site to your Home Screen as a web app to get its notifications.
If you make an app:
- Ask in context, after an action that shows what notifications bring, and request
POST_NOTIFICATIONSyourself on Android 13 and later. - Send the token to your server at each launch, one per device, and drop stale ones.
- Keep payloads under 4 KB, with nothing sensitive in them.
- Keep Time Sensitive and high priority for what matters now.
- Promote only after an explicit opt-in, with an opt-out inside the app.
- Offer categories and an in-app settings screen.
- Make sure the app works with notifications off.
Sources
- Apple, iPhone User Guide, View and respond to notifications on iPhone: the Lock Screen, Notification Center, banners, muting.
- Apple, iPhone User Guide, Change notification settings on iPhone: the per-app switches, previews, Scheduled Summary, AI summaries, government alerts.
- Apple, iPhone User Guide, Set up a Focus on iPhone: Focus and Do Not Disturb.
- Apple, iPhone User Guide, Allow or silence notifications for a Focus on iPhone: people, apps and web apps in a Focus.
- Apple, iPhone User Guide, Turn a website into an app in Safari on iPhone: web apps and their notifications.
- Apple, Apple Support, Use notifications on your iPhone or iPad: the Options menu, StandBy, Critical Alerts.
- Apple, Apple Developer, User Notifications: local and remote notifications, delivery.
- Apple, Apple Developer, Setting up a remote notification server: the definition, the four parts.
- Apple, Apple Developer, Registering your app with APNs: device tokens, the capability.
- Apple, Apple Developer, Asking permission to use notifications: the prompt, provisional authorization.
- Apple, Apple Developer, Scheduling a notification locally from your app: local notifications.
- Apple, Apple Developer, Sending notification requests to APNs: servers, storage, priority, push types.
- Apple, Apple Developer, Generating a remote notification: payload size, sensitive data, silent updates.
- Apple, Apple Developer, Sending web push notifications in web apps and browsers: web push in Safari and web apps.
- Apple, Human Interface Guidelines, Notifications: badges, content best practices.
- Apple, Human Interface Guidelines, Managing notifications: Focus, interruption levels, marketing.
- Apple, Apple Developer, App Review Guidelines: rules 2.5.18, 4.5.3, 4.5.4, 4.10 and 5.1.2.
- Apple, WebKit blog, Web Push for Web Apps on iOS and iPadOS: web push in iOS and iPadOS 16.4.
- Apple, WebKit blog, WebKit Features in Safari 26.0: every site added to the Home Screen as a web app.
- Google, Android Help, Control notifications on Android: the settings, cooldown, history.
- Google, Android Developers, About notifications: where notifications appear, channels, importance.
- Google, Android Developers, Notification runtime permission:
POST_NOTIFICATIONS. - Google, Android Developers, Create and manage notification channels: the user’s control of channels.
- Google, Android Developers, Request runtime permissions: permissions refused more than once.
- Google, Firebase, Firebase Cloud Messaging: FCM.
- Google, Firebase, FCM Architectural Overview: registration, transport layers.
- Google, Firebase, Firebase Cloud Messaging message types: payload limits.
- Google, Firebase, Set and manage Android message priority: normal and high priority.
- Google, Firebase, Best practices for FCM registration management: Firebase Installation IDs, stale registrations.
- Google, Firebase, Get started with Firebase Cloud Messaging in Apple platform apps: the APNs authentication key.
- Google, Google Chrome Help, Use notifications to get alerts: Chrome on a computer, and on Android.
- Google, Play Console Help, Unauthorized Use or Imitation of System Functionality: Google Play’s rule on notifications.
- Google, Play Console Help, Ads: ads that imitate notifications.
- Google, Play Console Help, Understanding foreground service and full-screen intent requirements: full-screen intent notifications.
- Google, Play Console Help, Device and Network Abuse: full-screen intents and disruptive ads.
- W3C, Push API: the Working Draft of 9 November 2026.
- WHATWG, Notifications API Standard: showing notifications.
- IETF, RFC 8030: Generic Event Delivery Using HTTP Push: the web push protocol and its 4,096 bytes.
Checked on 10 November 2026.