The pitch for a native casino app usually leans on performance and push notifications. The counter-argument is simpler: a 95 MB download on a 64 GB iPhone is a storage tax most players will not pay twice. A UK-facing brand moved from an APK build to a progressive web app and watched uninstalls fall 34% over the following quarter. The mechanism was not better games or bigger bonuses. It was the fact that players stopped deleting photos to make room for a casino.
The storage math behind a 95 MB casino download
Start with the numbers a skeptic would demand. A 64 GB iPhone reports roughly 55 to 58 GB of usable space after the operating system and preinstalled apps. Photos, WhatsApp media, and a handful of streaming apps routinely eat 40 GB of that. The margin left for new installs is often under 5 GB. A 95 MB APK is not the real cost either: installation needs free space for the package plus the unpacked files, and cached assets push the true footprint past 200 MB within a week of play.
That is where the uninstall data gets interesting. The brand in this case study pulled session logs and found that churn clustered around storage warnings, not around losses or bonus complaints. Players on 128 GB devices churned at roughly half the rate of players on 64 GB devices. The pattern held across demographics, which killed the theory that small-storage users were simply less engaged. They were engaged. They were also being asked to choose between a photo library and a card game.
This is the part most operators miss when they defend native builds. The Britsino approach treats the mobile browser as the delivery channel rather than a fallback. Britsino offers a progressive web app that carries the same lobby, cashier, and bonus logic as the desktop site. There is no separate install budget, no package manager, and no storage line item in the player’s settings screen. For a 64 GB user, that difference is the whole decision.
What the switch actually involved: no APK, no store listing, no update queue
The migration was less dramatic than the phrase “app replacement” suggests. Britsino has no build in Google Play and no build in the App Store, and Britsino publishes no APK. That was true before the switch and stayed true after it. The change was in how the product was presented to players: instead of pointing them at a sideloaded package, the brand pointed them at the Britsino web app and a one-tap install flow.
On Android, the Britsino app is installed from the mobile browser. Android users install via Chrome Add to Home screen, which pins a shortcut that opens the casino full-screen without an address bar. On iOS, it is the same idea through a different menu: iOS users install via Safari and the Share sheet’s Add to Home Screen option. The web app adds a home screen icon that behaves like any other app tile. It launches without browser chrome, keeps its own session, and survives a phone restart.
The operational win is the update path. A native build means a new binary, a store review, and a staggered rollout that can take days. A PWA casino ships the update the moment the server deploys it. There is no app update prompt, no version fragmentation, and no support queue for players stuck on a build from three releases ago. If a cashier bug ships at 09:00, the fix is live at 09:30 for everyone, including the player who installed the icon six months ago.
The trade-off a skeptic should flag: you lose the store listing as a discovery channel. There is no Google Play search result, no App Store ranking, no “top free casino apps” placement. The brand accepted that because its acquisition ran through affiliates, email, and QR code campaigns anyway. Store discovery was never a meaningful traffic source for a UK-licensed casino, so giving it up cost less than it looks on paper.
Where the PWA falls short and how the team worked around it
Do not read the 34% figure as a claim that PWAs beat native on every axis. Push notification support on iOS is real but narrower than native, and it depends on the player adding the icon to the home screen first. Background sync is less reliable. Heavy animation on older Android hardware can stutter in a way a compiled app would not. The team’s answer was to trim the lobby to a lighter asset set and lazy-load game tiles, which cut first-paint time on mid-range devices by roughly a third.
Payment flows needed attention too. Some banking apps and 3D Secure redirects behave differently inside a home screen web app than in a full browser tab, and a handful of players reported the redirect landing in Safari instead of the app shell. The fix was to open the cashier in an in-app browser view with a clear return path. Britsino web app users get the same bonuses as desktop players, so there was no bonus parity problem to solve, but the cashier handoff needed testing on both platforms before launch.
The other honest caveat is the unknown sources warning. Anyone who has sideloaded an APK file knows the drill: Android throws a permissions screen, and a meaningful share of users abandon at that prompt. APK installation requires unknown sources permission, which is a security decision most players are right to be wary of. Removing that friction entirely is a quiet but real conversion gain, and it is the part of the switch that shows up in funnel data before it shows up in churn data.
For teams weighing the same move, the sequence that worked here is worth copying. Audit your install funnel for storage-related drop-off first, because if your churn is not correlated with device capacity, the PWA argument is weaker than it looks. Then build the home screen install prompt into the mobile browser experience with plain instructions for Android Chrome and iOS Safari, and put a QR code on desktop so players can carry the session to their phone without typing a URL. Keep a demo mode live so skeptical players can test the full-screen casino before they commit an icon to their home screen. Measure uninstalls, not installs, for the first 90 days. That is the number the switch actually moves.