Choose the protocol from the product surface
WebsiteWeb Push
Native Apple appAPNs
Android appFCM
These routes solve related delivery problems but use different credentials, client integrations, and platform rules. A product with both a website and native apps normally needs more than one route.
Web Push for websites
The browser manages permission, creates a subscription, and chooses the push service behind its endpoint. The site registers a service worker to receive background push events and display notifications. The Web Push setup and delivery guide connects those browser and server responsibilities as one system.
A website can run its own campaign dashboard and subscriber database, but it still sends to the push endpoint issued by the browser. The Web Push architecture and product boundaries explain which parts the site controls and which remain with browser vendors. Self-hosting does not mean bypassing browser-vendor delivery infrastructure.
APNs for native Apple apps
Native iOS and iPadOS applications register with Apple Push Notification service and receive a device token for the app, device, and environment. The provider authenticates with Apple and sends payloads to APNs. Application capabilities, entitlements, user settings, Focus modes, and Apple platform rules determine delivery and presentation.
Safari Web Push and Home Screen web apps use standards-based Web Push from the website's perspective, even though Apple infrastructure participates in delivery. Follow the separate Web Push flow for iPhone and iPad rather than applying native-app APNs instructions to a website.
FCM for Android and cross-platform messaging
Firebase Cloud Messaging provides SDKs and server APIs for native Android and other supported application environments. On Google Play-enabled Android devices, FCM is the normal route for reliable background message delivery. Native application messages can include notification data, application data, or both, subject to platform restrictions.
Credentials are not interchangeable
- Web Push uses a VAPID application-server key pair plus per-subscription encryption material.
- Native Apple delivery uses APNs provider credentials and app-specific device tokens.
- FCM uses project credentials and registration tokens issued through its client SDKs.
Do not place all three token types in one unstructured audience field. Store channel, application or domain, environment, credential owner, token state, and last response explicitly. For the website channel, keep the VAPID identity and key lifecycle distinct from native provider credentials.
Choose by product surface
Website only
Use Web Push. A Firebase SDK or OneSignal dashboard is not required for a standards-based website implementation.
Native iOS app
Use APNs directly or a provider that sends through APNs on your behalf.
Native Android app
Use FCM for the common Google Play environment, while planning separately for device ecosystems without Google services if those users are in scope.
Website and native apps
Use one customer preference model with separate channel endpoints and credentials. A person may have several browser subscriptions and device tokens, each with its own permission and lifecycle.
Operational differences to preserve
Track provider response codes, expiration, token refresh, environment, payload limits, and click behavior per channel. A unified campaign can share purpose and audience logic, but the final payload and delivery adapter should be channel-specific.
Primary references
Use a channel adapter instead of a lowest-common-denominator payload
Define one internal message intent with a title, purpose, destination, urgency window, and audience rule. Then translate it through a Web Push, APNs, or FCM adapter that validates the fields and credentials for that channel. Do not assume actions, images, badges, collapse behavior, priority, or payload limits map identically.
Keep permission and endpoint state per installation
A customer preference may authorize a topic across products, but each browser subscription or native-app token has its own lifecycle. One endpoint can expire while the others remain valid. Uninstalling a native app, removing a Home Screen web app, clearing browser data, or rotating a token should update only the affected destination unless the person also changes the broader account preference.
Ask four questions before choosing the route
- Is the destination a website, a native app, or both?
- Which runtime will receive the background event?
- Which vendor issues the endpoint or device token?
- Which credential and payload rules apply to that exact environment?
Those answers select the delivery adapter. Marketing terminology such as “mobile push” does not.