TractionScout
← Back to the blog
Lifecycle messaging

Web push notifications in 2027: what works on iPhone, Android and desktop

Which browsers deliver web push, what iPhone needs, and how to ask for permission without getting blocked

7 Nov 2026 · 5 min read

Web push notifications work in every major browser on desktop and Android. On iPhone and iPad they work since iOS and iPadOS 16.4, but only for web apps the visitor has added to the Home Screen. Everywhere, you need a service worker, a page served over HTTPS, and a permission request that follows something the visitor did, like tapping a button.

Which platforms support web push

The Push API has been available across all major browsers since March 2023, when Apple brought it to iPhone and iPad. The table shows what each platform needs.

PlatformWeb pushWhat it needs
Chrome, Edge and Firefox on desktopYesService worker, HTTPS, permission
Safari on macOSYes, since Safari 16.1 on macOS VenturaService worker, HTTPS, permission
Chrome and Firefox on AndroidYesService worker, HTTPS, permission
Safari on iPhone and iPadYes, since iOS and iPadOS 16.4The site added to the Home Screen as a web app, then permission

The iPhone row is the one that surprises people. A visitor reading your site in a normal Safari tab cannot subscribe. They first add your site to the Home Screen, open it from there, and then accept notifications. If most of your audience is on iPhone and does not install your web app, email will reach them more reliably than push.

What every platform requires

  • A service worker. Push messages arrive at a small script your site registers, even when no tab is open. Without an active service worker, nothing is received.
  • HTTPS. The Notifications API only runs in secure contexts, so the page that asks for permission must be served over HTTPS.
  • A permission request after a visitor action. Safari on iPhone and iPad accepts a request made in response to direct user interaction, such as tapping a subscribe button. Asking on page load is the fastest way to be refused, on any browser.

Ask at the moment it makes sense

A permission prompt on page load asks a stranger for a favour before they know what you offer. Most say no, and a browser remembers a refusal. Ask instead when the visitor has a reason to say yes: a "Notify me when the report is ready" button, a "Get release notes" switch on a changelog, or a confirmation after they create an account.

The button should say what they will get and how often. "Get one alert when your weekly report is ready" earns more yes answers than "Enable notifications".

Write for the smallest preview

Every operating system cuts notifications differently. A title that fits on macOS can be truncated on Android; a long message can lose its last line on Windows. Put the useful part first: the event, then the detail. Keep the title to a few words and test it on the devices your subscribers use before you send.

Measure what push can actually tell you

Push services accept a message, but they do not confirm that it was shown. So be careful with "delivered":

MeasureWhat it means
AcceptedThe push service took the message for delivery
ShownThe device reported displaying it, where the subscriber allows tracking
ClickedThe subscriber opened it, where they allow tracking
Turned offThe subscriber revoked permission
ExpiredThe subscription is no longer valid and was removed

Rates should be calculated from accepted messages. And keep the frequency low: one or two notifications a day per person is already a lot, and every unwanted alert is a reason to turn you off for good.

How push works in TractionScout

Writing a push notification in TractionScout: the title and message are typed and the preview updates, beside the Write, Check, Approve and Send steps

Writing a notification in the TractionScout demo workspace on sample data; the preview updates as you type.

In TractionScout, push lives in Campaigns › Push. You download one service worker file, copy one script line into your pages, and add a "Get notifications" button with one attribute; the browser asks for permission only when a visitor clicks it. A built-in check confirms both pieces are reachable, and test notifications go only to your own browser.

The composer previews each notification as Android, macOS, Windows, iPhone and iPad cut it, and reminds you that Safari on iPhone and iPad shows notifications only for sites added to the Home Screen. You can send one-off notifications or sequences that branch on whether the last one was shown or clicked, with at most two notifications per contact a day by default. Scout drafts them; you approve and send. Push clicks get their own group in analytics, so you can follow them to sign-ups. See Push notifications.

Questions

Can I send web push to iPhone users who have not installed my site?

No. On iPhone and iPad, web push is available to web apps added to the Home Screen. A visitor in a regular Safari tab cannot subscribe.

Do I need a native app for push notifications?

Not for browsers. Web push reaches desktop and Android browsers directly, and iPhone users who add your web app to the Home Screen. Notifications inside a native app use Apple's and Google's native push services instead.

Why are my push open rates lower than reported elsewhere?

Often because yours are honest. If rates are calculated from accepted messages and count clicks only where subscribers allow tracking, they will be lower than figures that assume every message was shown.

Empfohlen

Add push to your site with one file and one line

Notifications your subscribers asked for, previewed per device and approved before they go out.