Push Notifications on iPhone: Web Push vs Native App Notifications (2026)

Step 1: the user adds your site to the Home Screen

On iPhone, a page open in Safari can’t request notification permission. MDN’s compatibility data for the Notification interface on iOS says it is undefined unless the page is a web app saved to the Home Screen. So the first step is always the user tapping Share, then Add to Home Screen.

Since iOS 16.4, Safari, Chrome, Edge, Firefox and other iOS browsers can all add sites to the Home Screen. And with iOS 26, WebKit says every website added to the Home Screen opens as a web app by default, even without a web app manifest, though users can switch “Open as Web App” off when adding it.

Step 2: the user taps a button to allow notifications

Inside the Home Screen web app, your page can ask for permission, but only in response to a direct user action. Apple’s documentation says the subscription call must run from the handler of a tap or click. A permission dialog that appears on page load won’t work. The usual pattern is a clear button such as “Remind me before my class,” followed by the system prompt.

Step 3: your server sends, Apple delivers

Your server sends web push messages to Apple’s push service, which delivers them to the phone. Apple’s documentation says your server must be allowed to reach https://*.push.apple.com, that payloads are limited to 4 KB, and that every push must show a visible notification. “Safari doesn’t support invisible push notifications”; if your service worker doesn’t display one, Safari revokes the permission.

In March 2025, WebKit introduced Declarative Web Push, testable from iOS and iPadOS 18.4. The push message itself is standard JSON that the system can show without running a service worker, which WebKit describes as more energy-efficient and more private. Older browsers fall back to the classic service worker approach.

Asking for permission

Native apps show the system permission prompt once. Apple’s guidance is to ask “in a context that helps people understand why,” rather than on first launch, because a refused prompt can’t simply be shown again. People can later turn notifications on in Settings.

Provisional notifications

Native apps have one option web apps don’t: provisional authorization. The app can send notifications without showing a prompt at all; they arrive quietly in Notification Center history with Keep and Turn Off buttons. It’s a gentle way to show value before asking for full permission. Apple documents it in its guide to asking permission to use notifications.

What native push requires

You need an app distributed through the App Store or TestFlight, so you need an Apple Developer Program membership at US$99 a year, App Review for each release, and push credentials configured for your app. On Android, native apps use Firebase Cloud Messaging and their own permission prompt, which Android 13 and later show before an app can post notifications.

Where web push wins

Web push is strong when people already use your site and trust you: members of a club, staff using an internal tool, customers of a booking site. You can show a short “Add to Home Screen for reminders” guide right where it’s useful, skip App Review, update instantly, and avoid the Apple developer fee. On Android, Chrome supports web push without installation at all, so the friction is mainly an iPhone issue.

Where native push wins

Native wins when notifications are central to the product and you want strangers to find you in the App Store. Push vendor Airship’s 2026 benchmarks, based on its own customers’ native apps in 2025, put the median opt-in rate at 48.85% on iOS and 53.3% on Android. We found no comparable first-party figures for web push on iPhone, so we can’t give you a like-for-like number; what we can say is that web push has an extra install step before the opt-in even starts.

Doing both

Many products run both: web push for people who use the website, native push for people who install the app. If your app and website share one backend, the server simply sends to whichever subscriptions a user has. This is often the best answer for small teams, because the website can start sending reminders on day one while the native app goes through review.

Can a website send push notifications to an iPhone?

Yes, since iOS 16.4, but only after the user adds the site to the Home Screen and allows notifications from a button tap inside that Home Screen web app. A site open in Safari can’t ask for permission on iPhone.

Do I need an Apple Developer account for web push?

No. Apple’s documentation says you don’t need to join the Apple Developer Program to send web push notifications. Native app push requires the US$99-a-year membership.

Why don’t my web push notifications work on iPhone?

The most common reasons are that the site wasn’t added to the Home Screen, the permission request didn’t come from a user tap, the iPhone is on a version older than iOS 16.4, or a push didn’t display a notification and Safari revoked the permission.

Do web push notifications look different from app notifications?

Not much. WebKit says they appear on the Lock Screen, in Notification Center and on a paired Apple Watch, and users manage them per app in Settings, like native apps.

Can I show a badge number on the Home Screen icon of a web app?

Yes. iOS 16.4 added support for the Badging API in Home Screen web apps, so your app can set and clear a badge count.

Does web push work in the EU?

Yes. Apple had planned to remove Home Screen web apps in the EU with iOS 17.4, but reversed that in March 2024 and kept the existing capability, built on WebKit.