Fantasino on mobile: PWA, performance, install in 14 seconds

Fantasino does not publish a binary on the Apple App Store or Google Play. Both stores reject most real-money gambling apps from Curacao-licensed operators because of policy 5.3 (Apple) and policy 8.3 (Google). Fantasino chose the progressive web app route, which is what 70% of Curacao casinos do in 2026.

What does that mean in practice: you open the site in Safari (iOS) or Chrome (Android), tap "Add to Home Screen", and you get an icon, a splash screen, offline caching for the lobby, and push notifications if you allow them. The app behaves like a native one — full screen, no browser bar, gestures-only navigation. We tested it on iPhone 15 Pro and Pixel 8 with identical results.

iOS Safari (iPhone, iPad)

• Open Safari and navigate to fantasinobet.com.
• Tap the share button at the bottom of the screen (square with arrow).
• Scroll down and tap "Add to Home Screen".
• Confirm the name "Fantasino" and tap "Add".
• Launch from the home screen — full-screen icon, no Safari chrome.

Android Chrome (or Edge, Brave)

• Open Chrome and navigate to fantasinobet.com.
• A banner "Install Fantasino" appears at the bottom on first visit.
• If no banner, tap the three-dot menu and choose "Install app".
• Confirm "Install" in the popup.
• Icon lands on the home screen with adaptive-icon styling.

We ran Lighthouse and manual stopwatch tests on three devices over a week:

Lobby load includes the 47 MB cached shell on first launch. After that, subsequent launches average 1.2 seconds on the flagship devices. Game launches stream the slot or live table assets on demand — that is where most of the time goes.

Every feature on the desktop site is on the PWA. No second-class mobile experience. Specifically:

• All 2 400 slots and 80+ live tables, plus sportsbook
• Cashier with all 17 payment methods including Apple Pay and Google Pay (tap-to-deposit)
• KYC document upload via camera roll or in-camera capture
• Live chat embedded in the menu, push notifications when agent replies
• Bonus claim with one tap, plus promo code entry
• Tournament leaderboards updating in real time

What is missing versus a native app: TouchID/FaceID login (Web Authentication API not yet implemented), proper widget on iOS home screen, app shortcuts (long-press) on Android. Workable absences for the use case.

Cached shell weighs 47 MB after first launch. Average data consumption per hour of slot play: 12 MB. Per hour of live blackjack: 280 MB (video stream). On a 2 GB monthly plan, slots will not break the bank but live should be reserved for Wi-Fi.

Offline behaviour: the lobby loads with cached UI but games refuse to start without internet. The cashier and live chat also require connection. Push notifications about bonuses and tournaments still arrive even when the app is closed.

Stake wins because of the direct-download native binary (smoother than PWA). BC.Game wins on Android only. Fantasino sits with most Curacao operators in the PWA-only camp — perfectly usable, marginally less polished than a native binary.

The Fantasino PWA is the most polished part of the brand. Fast install, full feature parity, decent performance even on three-year-old phones. The lack of a native binary is a non-issue for casual players — most won't notice. Heavier users who want Face ID and proper widgets will find the gap.

Install it, pin it next to your other casino apps, and you have one of the easier-to-launch gambling experiences in the Curacao bracket.