Do push notifications work in a PWA on iOS?

Yes, but only starting with iOS 16.4, and only for PWAs already added to the home screen — visitors on older iOS versions won't get push at all.

Which OS converts better in PWA arbitrage overall?

There's no universal answer — Android usually delivers more installs thanks to its simpler flow, while iOS can bring a more affluent audience in certain verticals. The right answer depends on geo, vertical, and offer, and needs a test, not a blanket rule.

Do I need a separate landing page for iOS and Android?

Not necessarily a separate page, but key moments need adapting — like a clear add-to-home-screen instruction for iOS, which Android doesn't need thanks to its automatic banner.

How do I detect a visitor's OS for cloaking?

Through User-Agent plus additional device signals, such as WebKit behavior on iOS versus Chromium on Android, which antibot filters read on the landing page before the offer is shown.

Should I drop one OS entirely if it converts worse?

Only after a fair, separately budgeted test on each platform — sometimes a weak conversion rate comes from a creative or landing page that wasn't adapted to that OS, not the OS itself.

PWA Traffic: iOS vs Android

PWA traffic on iOS vs Android isn't just a matter of taste — the two platforms offer different technical capabilities, different audience behavior, and different traffic costs. Safari and Chrome implement PWA features differently, so the same setup can convert quite differently depending on which OS a visitor arrives on. Here's what actually differs and how to adjust a campaign around it.

Technical differences between PWA on iOS and Android

Android Chrome offers the fullest PWA experience: an automatic 'add to home screen' banner, fully working push notifications, and a service worker with no major restrictions. Safari on iOS has historically been more closed off to PWA — several capabilities arrived noticeably later than on Android and still come with version-specific caveats. That means the same PWA landing page technically behaves differently depending on the OS, and that needs to shape conversion and engagement expectations upfront, not after the fact. Before launching a campaign, check the landing page separately on a real iPhone and a real Android device, not just in an emulator.

Adding to the home screen: a different UX on each platform

On Android, installation is often offered automatically through a system banner right in the browser — one tap is enough, which lowers the barrier to install. On iOS the path is longer and less obvious: the visitor has to manually open Safari's Share menu and choose 'Add to Home Screen,' and plenty of people simply don't know that option exists. Because of that, the gap in install willingness between platforms isn't just about interest in the offer — it's also a UX barrier built into the OS itself. A good practice is to spell out that step clearly on the landing page for iOS visitors instead of assuming they'll find the button on their own.

Conversion and engagement: what to actually expect

Thanks to its simpler install flow, Android typically converts a higher share of landing-page visitors into PWA installs. iOS traffic is often pricier per click and per install in ad accounts, but in some verticals, such as finance or premium offers, iOS audiences have historically skewed more affluent. Final ROI depends on the combination of OS, geo, and vertical, not the OS alone — no platform wins outright in every case. Check both directions separately in your own analytics before cutting budget on either OS.

Push notifications: where Android has the edge

On Android, push notifications in a PWA have worked fully for a long time — one of the main tools for bringing a user back after install, whether it's an offer reminder or a triggered send. On iOS, web push inside a PWA only became available starting with iOS 16.4, and only for apps already added to the home screen, meaning a chunk of the audience on older iOS versions can't receive push at all. Because of that, retention and re-engagement strategy needs to differ by platform: on Android you can count on push right after install, on iOS only on current system versions and only after the visitor has completed the add-to-home-screen step. APEX's push engine — list building, segmentation, triggered and scheduled sends — accounts for these platform limits, so segmenting by OS from the start is worth building in early.

Moderation and cloaking, platform by platform

Antibot filters on the landing page typically read User-Agent and device signals, so cloaking logic can and should treat iOS and Android traffic as distinct streams rather than one undifferentiated flow. Platform reviewers also browse from different devices, and bot and reviewer behavior patterns differ by OS — solid antibot coverage needs to handle both scenarios, not just be tuned for one. Some checks, such as Safari and WebKit-specific quirks, need extra attention if you're running custom cloaking logic instead of a built-in solution. APEX's built-in antibot filters, keyed on User-Agent and device signals, cover both platforms without per-OS configuration.

What to optimize budget and creatives around

If the vertical and offer target mass reach and a low ticket size, Android usually delivers more installs for the same budget thanks to its simpler flow. If the offer is premium or targets a more affluent audience, it's worth testing iOS separately even at a higher cost per click — the final ROI can justify the price gap. Creatives and messaging can be adapted per platform too: spell out the add-to-home-screen step clearly for iOS, and lean more on the offer itself for Android, where the banner does the install work automatically. Don't average stats across both OSes in one report — separate analytics for iOS and Android show immediately where money is actually being lost.

Practical traffic-split recommendations

When launching a new setup, test iOS and Android separately with small budgets rather than running one undifferentiated campaign. Track not just install CR but downstream behavior too — push open rates, return visits, final CPA — separately for each platform. If one segment is clearly losing on ROI after a fair test, don't hesitate to pause it and put budget where the setup actually performs. Revisit the split periodically — the iOS and Android traffic mix for a given geo and vertical shifts over time, and what was true six months ago may no longer hold.

FAQ

Do push notifications work in a PWA on iOS?: Yes, but only starting with iOS 16.4, and only for PWAs already added to the home screen — visitors on older iOS versions won't get push at all.
Which OS converts better in PWA arbitrage overall?: There's no universal answer — Android usually delivers more installs thanks to its simpler flow, while iOS can bring a more affluent audience in certain verticals. The right answer depends on geo, vertical, and offer, and needs a test, not a blanket rule.
Do I need a separate landing page for iOS and Android?: Not necessarily a separate page, but key moments need adapting — like a clear add-to-home-screen instruction for iOS, which Android doesn't need thanks to its automatic banner.
How do I detect a visitor's OS for cloaking?: Through User-Agent plus additional device signals, such as WebKit behavior on iOS versus Chromium on Android, which antibot filters read on the landing page before the offer is shown.
Should I drop one OS entirely if it converts worse?: Only after a fair, separately budgeted test on each platform — sometimes a weak conversion rate comes from a creative or landing page that wasn't adapted to that OS, not the OS itself.

Build your PWA in APEX in minutes

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

Get started free