The whole casino, in your pocket

Reviewed by Anton VasilievMobile build last shipped June 9, 2026

Why a PWA, not a native app?

Both the Apple App Store and Google Play prohibit real-money casino apps in US states without a regulator-issued operator licence. Because our sweepstakes model doesn't require state gambling licences, we live in a grey zone that the platform reviewers occasionally tolerate and occasionally reject. Building around their policy was a choice: instead of risking app review limbo every quarter, we shipped a progressive web app. That means a fully native-feeling installable experience on every modern smartphone, with no store middleman, no in-app-purchase tax, and the ability to ship updates the moment they pass internal QA.

The technical wrap is a Service Worker that caches the full lobby for offline browsing of yesterday's reels, an installable manifest that produces a homescreen icon indistinguishable from a native app, and a push-notification subscription that lets the app wake up your device for the 4-hour wheel reset and surprise SC drops. The result feels native and is independently ranked above the McLuck and Pulsz native apps on every Lighthouse audit we have published since March 2026.

The feature set

Install in ten seconds

Performance benchmark — Lucky North PWA vs. native competitors

Where players are coming from

Network and battery — how the app behaves

Privacy on a mobile device

• No third-party SDK ships in the PWA. No Facebook pixel, no Adjust, no AppsFlyer.
• Push tokens are stored encrypted on our servers and rotated every 30 days.
• Biometric data never leaves your device — the OS handles authentication and gives us a yes/no.
• You can revoke push permissions at any time from your profile or your OS settings.

FAQ

The architecture under the hood

The Lucky North PWA is a single-page React application bundled with Vite. The lobby ships as a 220 KB gzipped JavaScript payload that hydrates on the device and then talks to our backend over WebSockets. WebGL is used for slot reel rendering; tables and live dealer use a thin Canvas overlay plus the studio video feed. Service Worker caches the lobby shell, game art, and the previous five game sessions, which is why the install size is only 3.4 MB versus the 100+ MB you see from native competitor apps that ship a duplicate copy of every slot's binary art bundle into your storage.

The audio path is worth a separate mention. Most casino PWAs route audio through plain HTML5 audio elements, which is convenient but adds 200–400 milliseconds of latency between the slot reel stop and the win sound. We use Web Audio with a custom mixer to drop that to under 30 milliseconds, which means the bonus trigger sound lands exactly on the reel snap and not noticeably late. Players never notice a problem fixed in advance. They do notice a problem fixed late.

Push notifications without the spam

Push is the lever that breaks most casino apps. Send too many notifications and the user disables them within a week. Send too few and the user forgets the app exists. We landed on a soft cap of one push notification per active calendar day per opted-in user. Within that budget the rotation prioritises hourly wheel resets if the player is mid-cycle, daily login reminders if it has been more than 20 hours since the last visit, and surprise SC drops at intervals weighted toward weekend evenings. Players who actively disengage from push are reminded once by email after seven days and then never again. Marketing teams hate this rule; we keep it because the alternative is a 30-day churn curve that looks like a cliff.

Offline mode — what actually works without a signal

You cannot spin a slot or place a bet without an internet connection — sweepstakes wagering is server-authoritative and we do not trust offline state. But the PWA caches enough that you can still browse the lobby, view yesterday's session history, read your VIP statement, and queue an email to support. When the device reconnects, the queued message uploads automatically. We see this matter most on flights and on subway commutes: the player opens the app, browses while disconnected, queues a question to support, and the message lands the moment they emerge into signal. Compared with native apps that show a "no connection" screen and lock the entire interface, this is a small but meaningful difference.

Service Worker, cache, and what happens on app update

The PWA uses a versioned Service Worker that handles offline caching and update delivery. Every time we deploy a new version of the lobby — typically twice a week — the Service Worker fetches the new asset manifest in the background while the player continues their current session, swaps the cache atomically when the player next backgrounds the app, and brings up the new shell on the next foreground without a visible reload. There is no "your app is updating, please wait" interstitial. Compared with native apps that force a Google Play or App Store download cycle for every change, the median time-to-update on Lucky North is under 90 seconds for the entire player base.

Web Push permissions: granular, granular, granular

When you tap the bell icon and grant Web Push permission, you are not handing over a single binary switch. The permission flow surfaces a four-checkbox grid: daily login reminder, hourly wheel reset, surprise SC drops, and weekly tournament alerts. Each category is independently toggleable from your profile screen at any later moment. The Service Worker keeps the toggles in sync between devices, so disabling tournament alerts on your iPhone disables them on your Android tablet too. This is more granularity than any major native casino app currently offers, and it is a direct response to the player feedback we collected during the PWA beta in early 2026 — what users hated most about native apps was the all-or-nothing push permission ask.

Privacy: what we choose not to collect

We log enough to operate the casino safely and not a byte more. The PWA reports the user agent string and the screen resolution so we can match the right rendering profile, the device clock (used to drive bonus timers), and an encrypted session token. We do not log GPS location, contact lists, the contents of other applications, microphone audio, camera images, or any data Apple or Google labels "sensitive". Compared with the native apps that ship with three to seven third-party analytics SDKs each, the Lucky North footprint is invisible.