The Distribution Problem

Apple removed over 25,000 gambling apps from the App Store in a single policy update in 2019. Google Play restricts real-money gambling apps to a whitelist of 15 countries, with separate approval processes for each. For iGaming operators, app store distribution is not a channel — it is a dependency on two companies that can shut you down overnight with no appeal.

The business case for native apps was always about two things: push notifications and home screen presence. Progressive Web Apps now deliver both — without the gatekeeper risk.

What PWAs Actually Deliver

Install without a store: A PWA installs directly from the browser to the home screen. No app store listing, no review process, no risk of removal. The player taps "Add to Home Screen" and the app appears alongside native apps — with its own icon, splash screen, and full-screen experience.

Push notifications: Web Push API support on Android has been stable for years. iOS added PWA push notification support in iOS 16.4 (March 2023). The last technical gap between PWA and native for iGaming use cases has closed.

Instant updates: Native apps require users to accept updates through the app store. PWAs update automatically on launch — no user action required, no version fragmentation, no "please update your app" screens. A regulatory-required change deploys to 100% of users immediately.

Offline capability: Service workers enable offline caching of the app shell, meaning the PWA launches instantly even on poor connections. Game assets, player data, and UI elements are cached locally. Only live data (odds, game state) requires network connectivity.

The Performance Myth

The argument against PWAs has always been performance. For graphically intensive games — 3D slots, live dealer video streams — native code has a real advantage. But the iGaming app shell itself — the lobby, the account management, the sportsbook interface, the bonus dashboard — is UI, not computation. Modern browsers render this UI with performance indistinguishable from native.

The games themselves are already web-based. The vast majority of casino game providers deliver their content as HTML5/WebGL embedded in iframes. A native app wrapper adds nothing — the game performance is identical because the game is already running in a web view.

Unblockable Distribution

The strategic advantage of PWAs extends beyond app store independence. In markets where ISPs or governments attempt to block gambling sites, PWAs with service worker caching continue to function from the home screen even when the domain is blocked — because the app shell and core assets are already installed locally.

Combined with domain rotation strategies and CDN-level distribution, PWAs create a distribution channel that is significantly harder to disrupt than native apps (which require a centralized store listing) or standard websites (which require a reachable domain).

The Migration Path

Operators don't need to choose between native and PWA — but they do need to stop treating PWA as a fallback. The strategic play is PWA-first distribution with native apps as a supplementary channel in markets where app store presence is stable and valuable (primarily the UK and US regulated markets).

For operators targeting LatAm, Africa, or Southeast Asia — where app store gambling policies are restrictive or nonexistent — PWA is not the future of distribution. It is the present.