PWA on iOS: How Install Works & Why Campaigns Still Convert

What "PWA on iOS" actually means for advertisers

If you run app-install or web campaigns, PWA on iOS is one of the most misunderstood parts of mobile growth. A Progressive Web App (PWA) is a website that behaves like an app: it opens full-screen, gets a home-screen icon, and can work partly offline. On Android the install is almost frictionless. On iOS the same PWA still works, but the install path is different, quieter, and bound by rules Apple sets in Safari.

That gap matters because a large share of paid traffic in many regions lands on iPhones. If your funnel assumes an Android-style install prompt, your iOS cost per install quietly inflates and you blame the creative when the real culprit is the install step. This guide explains how an iOS PWA installs, what genuinely works versus the real limits, how iOS compares to Android, and — the part most articles skip — how advertisers still run effective iOS PWA install campaigns despite those limits.

For the broader strategy across both platforms, see our overview on progressive web apps for advertising. This piece zooms into the iOS-specific reality.

How a PWA installs on iOS: Add to Home Screen via Safari

There is no automatic install banner for a PWA on iOS. Installation happens through Add to Home Screen, a manual Safari action the user triggers. The flow is short but every step is a drop-off point:

1. Open the PWA in Safari. This is non-negotiable — see the Safari-only note below.

2. Tap the Share button (the square with an upward arrow) in the toolbar.

3. Scroll and tap "Add to Home Screen." It sits below the share targets, so users miss it without guidance.

4. Confirm the name and tap Add. The icon now lands on the home screen.

5. Launch from the icon. Only then does iOS render it full-screen, hiding Safari's chrome.

The takeaway: a PWA install on iOS is a guided action, not a one-tap prompt. The single biggest lever you control is whether your landing experience teaches that gesture clearly. A blank page that assumes the user already knows where the Share button hides will leak installs at every step. Cross-platform install flows like DeepClick's PWA-install layer exist to script that gesture — detecting iOS, surfacing the right Add to Home Screen instructions, and timing the prompt so it converts.

The real limitations of a PWA on iOS (and which ones matter)

Apple supports PWAs on iOS, but with guardrails. Knowing the real iOS PWA limitations keeps you from over-promising and helps you design around them.

• No automatic install prompt. Android can fire a beforeinstallprompt event and show a native banner. iOS cannot. Every install is a manual Add to Home Screen, so the instruction UX is your conversion surface.

• Safari-only install. Add to Home Screen for a true PWA works from Safari. If the user opens your link inside an in-app browser (an ad network's webview, a chat app's preview pane), the option is missing or degraded. Routing iOS taps into Safari is a real funnel decision, not a detail.

• Web push exists but is gated. iOS added web push for installed PWAs, but only once the app is added to the home screen and the user grants permission. You cannot rely on push to re-engage a visitor who never installed — plan a fallback.

• Storage and lifecycle caveats. iOS may evict cached data for PWAs that go unused for an extended period, and some background capabilities Android offers are absent. Treat the PWA as a fast front door, not a heavy offline data store.

• No deep OS integration. A PWA does not appear in the App Store, cannot use every native API, and lives somewhat apart from the system app catalog. For many growth and re-engagement plays that is perfectly fine; just set expectations accordingly.

None of these block a campaign. They simply mean iOS rewards a guided, fast, Safari-anchored experience and punishes a funnel copied straight from Android.

iOS vs Android PWA: capability comparison

The practical differences come down to how the install fires and what the installed app can do afterward.

The pattern is consistent: Android removes friction automatically, iOS asks you to remove it deliberately. That is a design problem you can solve, not a wall.

How advertisers still run effective iOS PWA install campaigns

This is the lead angle, and where iOS PWA performance is actually won or lost. The limits above are real, but advertisers ship strong iOS numbers by engineering around them.

1. Guide the install gesture explicitly. Because there is no prompt, your landing page must demonstrate Add to Home Screen with an animated cue or arrow pointing at Safari's Share button, ideally triggered at the right moment rather than on page load. A managed flow such as DeepClick's PWA install product handles iOS detection and the instruction overlay across both platforms so you are not hand-coding Safari quirks per campaign.

2. Make the landing fast and Safari-native. iOS visitors abandon slow pages quickly, and an install they cannot complete inside Safari is an install lost. Keep the page light, open it in Safari rather than a webview, and remove every tap that is not the install.

3. Route paid traffic cleanly and stay compliant. iOS campaigns face strict ad review, and messy redirect chains both break the Safari install and risk policy issues. Compliant traffic routing — separating real users from bot and review traffic, and keeping the path clean — protects the account that funds the campaign. DeepClick's compliant traffic routing layer is built for exactly this kind of paid iOS traffic.

4. Recover the drop-offs. Most iOS visitors will not install on the first visit, and without an auto-prompt you lose them silently. A re-engagement flow brings back users who bounced before Add to Home Screen — through web push once they do install, or through reminder surfaces that nudge a return visit.

Stacked together, these turn iOS from the platform that "doesn't support PWA installs well" into a channel that converts — because you stopped fighting Safari and started designing for it.

Key takeaways

• A PWA on iOS installs only through manual Add to Home Screen in Safari — there is no automatic prompt.

• The real iOS PWA limitations are: no auto-prompt, Safari-only install, gated web push, storage eviction, and no App Store presence.

• iOS vs Android: Android removes install friction automatically; iOS requires you to guide it deliberately.

• Advertisers still win on iOS by guiding the gesture, keeping the landing fast and Safari-native, routing traffic compliantly, and recovering drop-offs.

• The install step — not the creative — is usually what inflates iOS cost per install. Fix the step.

FAQ

Can you install a PWA on iOS?

Yes. A PWA installs on iOS through Safari's Add to Home Screen option in the Share menu. There is no automatic install banner like on Android, so the user performs the action manually, which is why a guided landing experience matters.

Why is there no install prompt for a PWA on iOS?

Apple does not implement the beforeinstallprompt event in Safari, so iOS cannot show a native one-tap install banner. Every iOS PWA install is a manual Add to Home Screen, and your instruction UX replaces the missing prompt.

Do PWAs support push notifications on iOS?

Yes, but only after the PWA is added to the home screen and the user grants notification permission. You cannot push to a visitor who never installed, so plan a re-engagement fallback for users who drop off earlier.

What are the main iOS PWA limitations for advertisers?

No automatic install prompt, Safari-only installation, web push gated behind install, possible eviction of cached storage after disuse, and no App Store listing. Each is workable with a guided, fast, compliant funnel.

Does a PWA on iOS work outside Safari?

Add to Home Screen for a true PWA is a Safari action. In-app browsers and other webviews often hide or degrade the option, so routing iOS taps into Safari is an important part of an effective install campaign.