Which iOS version added web push support?

iOS 16.4 — before that, Safari didn't support web push at all.

Do you have to add the PWA to the home screen for push to work on iOS?

Yes, that's a hard requirement — push only works for a PWA added to the home screen, not for the site opened as a regular browser tab.

Why does push still not work for some iOS users?

Because they either never completed the add-to-home-screen step or explicitly declined the notification permission — both are entirely user-driven and can't be forced.

How do you compensate for low push coverage on iOS?

Sell the install prompt hard at the earliest possible moment, and collect email or messenger contact as a backup recovery channel for users who never add the PWA to their home screen.

iOS Push Notification Limitations

iOS push notification limitations are the first thing a buyer needs to understand before building push into a retention funnel for iOS traffic. Apple didn't support web push at all for years, and even now keeps it well outside the simple allow-in-browser-and-get-notified flow. Here's what works, what doesn't, and how to design a PWA funnel around those limits.

When web push became available on iOS at all

Web push on iOS only started working with iOS 16.4 — before that, Safari didn't support it at all. Even now, it isn't available by default: notifications only work for a PWA the user has added to the home screen via the Add to Home Screen action, not for the same site opened as a regular Safari tab.

What's actually restricted

Even after the home-screen install, the permission prompt can only appear in response to a deliberate user action, not automatically on open, and the subscription is tied to that specific installed PWA rather than the domain as a whole. A meaningful share of users simply never reach the add-to-home-screen step — and for them, push is unreachable by design.

How this reshapes the funnel for iOS traffic

Since push depends entirely on the home-screen install, the install prompt for iOS users isn't a technical footnote — it's a distinct conversion step that has to be sold explicitly, framed around not losing access later. Plan for the share of iOS traffic that won't complete that step upfront, instead of being surprised by low push reach later.

Workarounds and backup channels

For the iOS segment, it's worth pushing the add-to-home-screen prompt harder on the prelander and right after the first PWA open — that's the one step that actually unlocks push. In parallel, collect an alternative contact (email, messenger) during offer registration so users who skip the install prompt aren't lost entirely.

Segmenting the push base by OS

Since the push mechanics for iOS and Android are genuinely different, segment your base by OS at collection time rather than after the fact — that lets you measure real reach and push CR per platform instead of one blended, not very useful number.

FAQ

Which iOS version added web push support?: iOS 16.4 — before that, Safari didn't support web push at all.
Do you have to add the PWA to the home screen for push to work on iOS?: Yes, that's a hard requirement — push only works for a PWA added to the home screen, not for the site opened as a regular browser tab.
Why does push still not work for some iOS users?: Because they either never completed the add-to-home-screen step or explicitly declined the notification permission — both are entirely user-driven and can't be forced.
How do you compensate for low push coverage on iOS?: Sell the install prompt hard at the earliest possible moment, and collect email or messenger contact as a backup recovery channel for users who never add the PWA to their home screen.

Build your PWA in APEX in minutes

Cloaking, anti-bot, push, split tests and your own domains — in one service.

Get started free