Push notification

Also known as: push notifications

On this page 7

A push notification is a short message that a server sends to an installed application through an operating system delivery service, so that the device can display an alert, update a badge or wake the app even when it is not in the foreground. In mobile app development, push notifications are the standard mechanism for server-initiated communication with phones and tablets, because a background app cannot keep its own network connection open without draining the battery.

The defining feature is the delivery path: the app publisher never connects to the device directly. Instead, every message travels through a platform push service such as Apple Push Notification service (APNs) on iOS or Firebase Cloud Messaging (FCM) on Android, which maintains one shared, power-efficient connection per device.

How push notification delivery works

Push notification delivery follows a registration-then-send model in which the device, the platform service and the publisher server each hold a distinct role. When the app starts, it asks the operating system for permission and for a device token (also called a registration token), an opaque identifier that tells the push service which app installation on which device should receive a message.

The app uploads this token to the publisher backend, which stores it alongside the user account. To send a message, the backend authenticates to the push service, typically with a signed JSON Web Token or a service account credential, and submits a payload addressed to the token. The push service queues the message and forwards it over its persistent device connection when the device is reachable.

The following table summarizes the components that participate in a single delivery and the responsibility of each one.

ComponentRoleTypical failure
Client appRequests permission, obtains token, handles tapsToken never uploaded after refresh
Operating systemDisplays alerts, enforces user settingsNotifications disabled by the user
Push serviceQueues and routes messages to devicesRejects expired or invalid tokens
Publisher backendStores tokens, builds payloads, sends requestsExpired signing key or credential
Device connectionReceives queued messages when onlineDevice offline beyond message lifetime
Components in the push delivery chain

Tokens are not permanent. They can change after an app reinstall, a backup restore or a periodic rotation, so a robust client re-registers on every launch and the server removes tokens that the push service reports as unregistered.

Message types and payload options

Push notifications fall into two broad categories: visible alert messages that the operating system shows to the user, and silent or data messages that wake the app to perform work without any visible output. The choice determines how the system prioritizes, throttles and displays the message.

Payload size is strictly limited. APNs accepts up to 4 KB for a standard notification, and FCM accepts up to 4 KB of data payload, so a push message should carry identifiers and short text, not content. Large content is fetched by the app after it wakes.

TypeVisible to userTypical use
Alert notificationYes, banner or lock screenChat messages, order updates
Badge updateYes, number on the app iconUnread counters
Silent or background pushNoContent sync, cache refresh
Rich notificationYes, with image or actionsMedia previews, reply buttons
Time-sensitive or critical alertYes, may bypass focus modesSecurity alerts, health warnings
Common push notification types

Background pushes are treated as best-effort hints, not guarantees. Both iOS and Android may delay or drop them when the device is in a low-power state, when the user has force-stopped the app or when the app sends them too frequently. Apple additionally limits critical alerts to apps that hold a special entitlement.

A push notification is often confused with other ways of informing a user, but it differs in who initiates the message and which channel carries it. The comparison below places push next to the alternatives that mobile teams evaluate most often.

MechanismInitiated byWorks when app is closedMain limitation
Push notificationRemote serverYesRequires user permission
Local notificationApp on the deviceYes, if scheduled earlierCannot react to new server data
In-app messageApp while openNoReaches only active users
SMSCarrier networkYesPer-message cost, no app context
WebSocket or pollingApp connectionNo, or at high battery costDrains battery in background
Push notification versus alternative channels

Push notifications also interact closely with deep linking. A well-built notification carries a link or route identifier so that a tap opens the exact screen the message refers to, rather than the app home screen. Cross-platform frameworks such as Flutter, React Native and Expo expose push through plugins, but the underlying delivery still depends on APNs and FCM.

Designing and configuring push notifications

Effective push design starts with permission strategy. Since iOS and Android 13 and later both require an explicit opt-in prompt, the timing of that prompt strongly affects the opt-in rate. Experienced teams show a short explanatory screen first and request permission only when the user performs an action that clearly benefits from notifications.

On Android 8 and later, every notification belongs to a notification channel that the user can mute individually, and on iOS, interruption levels control whether a message can break through focus modes. Configuring these categories carefully gives users fine control and reduces the risk that they disable notifications entirely.

DecisionRecommended choiceReason
Permission timingAsk in context after a relevant actionHigher opt-in, fewer permanent refusals
Message priorityHigh only for user-visible, urgent messagesPlatforms throttle apps that overuse it
Time to liveShort for time-bound eventsStale alerts confuse users
Collapse key or thread IDGroup related updatesPrevents a stack of outdated alerts
Content in payloadIdentifiers, not sensitive dataLock screens expose message text
Configuration decisions for a push implementation

Many teams send through a mobile backend as a service or a dedicated messaging platform, which handles token storage, segmentation and scheduling. This reduces implementation effort but adds a third-party data processor that must be covered in privacy documentation.

Limitations, risks and common mistakes

The most important limitation is that delivery is not guaranteed. Push services store a message only for a limited time, and when several messages share a collapse key, only the newest one is kept. Any information the user must not miss should also be available inside the app when it next synchronizes.

  • Over-messaging is the leading cause of users disabling notifications or uninstalling the app.
  • Placing personal or confidential data in the visible text exposes it on a locked screen.
  • Ignoring token refresh callbacks silently cuts off a growing share of users over time.
  • Using silent pushes as a background execution timer fails because the system throttles them.
  • Failing to localize text and handle time zones produces alerts at night or in the wrong language.

Regulation also applies. Under privacy laws such as the GDPR, marketing notifications usually require a lawful basis and an easy opt-out, and app store review guidelines prohibit using push for unsolicited advertising unless the user has explicitly agreed to receive it.

Stripped to the essentials

A push notification is a small message that a company sends to an app on a phone, even when nobody has the app open. The message does not travel straight from the company to the phone. It goes through a postal service run by Apple or Google, which already keeps one quiet line open to every phone.

Think of it as a doorbell for apps. The app itself can sleep to save battery, and the doorbell wakes it only when something new arrives. The key point is that the user stays in control: the user must allow notifications, can mute them at any time, and will switch them off if the app rings too often.

Where it is applied

A regional food delivery service operates apps for iOS and Android built with a single cross-platform codebase. When a customer places an order, the backend stores the device token of that phone. As the order moves through preparation, pickup and arrival, the backend sends three alert notifications through APNs and FCM, each with the same collapse identifier so that only the latest status stays on the lock screen.

Each message carries only the order number and a short status line. A tap opens the order tracking screen through a deep link, and the app then fetches the courier location from the server. Promotional offers go through a separate notification channel that customers can mute without losing order updates.

After the team moved the permission prompt from the first launch to the order confirmation screen and separated promotional messages, the opt-in rate rose noticeably and complaints about late or duplicated alerts dropped.