PWA Install Quirks on iOS 16 and Later

PWA install quirks on iOS 16 and later start with this: there's no familiar «Install» button, the whole process runs manually through Safari. Here's what install actually looks like for a user, and how to walk them through it without losing them at the halfway step.

Why there's no one-tap install on iOS

Apple doesn't let a PWA install directly from the browser with a button the way Android does — the only official path is Safari's Share menu and its Add to Home Screen option. That's not a bug in any particular funnel, it's a platform-wide restriction that applies to every PWA on iOS equally.

Step by step: what install actually looks like for a user

The user has to open the page in Safari specifically — no other iOS browser has this option, even Chrome — tap the Share icon at the bottom of the screen, find Add to Home Screen in the list, and confirm. After that, an icon appears on the home screen and opens full-screen with no address bar.

How to explain these steps right on the page

Since there's no system prompt with an «Install» button, you have to show the instructions yourself: a clear arrow pointing at the Share icon, short copy like «Tap ⬆️ → Add to Home Screen», with no extra screens between landing on the site and seeing that prompt. Every extra step in the explanation is a point where part of the audience just closes the page.

iOS limits worth planning around

Push notifications for PWAs added to the Home Screen only arrived on iOS starting with version 16.4, and only work for the installed app — a regular Safari tab never gets them. It's not yet safe to rely on push as your main channel the way you would on Android, since part of your audience may still be on older iOS versions. Installed PWAs can also clear cached data and localStorage more aggressively than regular Safari does if the app sits unused for a while.

How APEX helps walk a user through iOS install

APEX prelanders — a wheel of fortune or a quiz ahead of the main screen, for example — aren't just for engagement; they can explicitly prime the user for the next step, «now install this», before they land on the page with install instructions. That cuts the share of people who reach the install step but don't understand what they're supposed to do.

FAQ

Can you install a PWA on iOS through Chrome instead of Safari?
No — on iOS, Add to Home Screen for a PWA is only available through Safari. Chrome on iOS technically runs on Safari's engine under the hood, but its interface doesn't expose the PWA install option.
Do push notifications work for a PWA installed on iOS?
Yes, but only starting with iOS 16.4 and only for a PWA added to the Home Screen — a regular Safari tab never gets push. It's not as reliable a channel as push on Android, so don't build all your communication around it alone.
Why do some users never make it to actually installing on iOS?
Mostly because they don't realize «Share → Add to Home Screen» is the install step — there's no familiar «Install» button to click. A clear visual prompt on the page fixes most of that drop-off.
Does an installed PWA behave differently on iOS versus Android afterward?
Yes — besides the push limitations, iOS can clear an app's local data more aggressively after long periods of inactivity, so any logic that depends on saved state is worth testing separately on iOS.
Build your PWA in APEX in minutes

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

Get started free

Read also