🔔 Push Notifications
Android delivers full web-push for bonus credit alerts, withdrawal confirmations and tournament leaderboard changes. iOS 17 partially restores push for installed PWAs — opt-in at install prompt.
Fatpirate ships its mobile build as a Progressive Web App rather than a Google Play or App Store release. This British-facing guide walks through why that choice exists, the exact taps to install on iPhone Safari and Android Chrome, the device requirements at the floor and the ceiling, the hourly data draw on slots and live tables, and the reasons every «Fatpirate APK» floating around search results should stay un-tapped.
Most casino-app searches end with a player chasing an APK download. At FatPirate the answer is different: the mobile build is a Progressive Web App (PWA) installed straight from the browser rather than a packaged app distributed through Google Play or the App Store. The architectural choice carries real consequences for the player:
For comparison, a third-party APK download carries three structural problems the PWA architecture eliminates: security risk (the file is by definition not signed by FatPirate), version mismatch (outdated builds cause slot-launch failures), and install friction (Play Protect warnings and manual permission dialogs). A PWA installs in under thirty seconds and has none of these issues.

The PWA installs from Chrome, Edge, Samsung Internet, Brave and Firefox — any browser that supports the Web App Manifest standard. The Chrome flow is the most consistent across devices:
The first launch from the home-screen icon will request notification permission. Declining is the recommended default — otherwise the casino sends daily promotional push notifications which is not the most useful pattern for self-controlled play.
On iOS the PWA installs only from Safari. This is an Apple restriction; Chrome, Firefox and other browsers on iOS still use Safari’s WebKit engine under the hood but cannot trigger the home-screen installation flow themselves. The procedure:
The new icon launches FatPirate in true fullscreen mode without the Safari address bar — visually indistinguishable from a native app. Apple Keychain auto-fills the login fields correctly, and Face ID or Touch ID prompts work through the standard password-manager autofill prompt.
| Component | Floor | Comfortable | Best-case |
|---|---|---|---|
| Android OS | Android 6.0, Chrome 90+ | Android 10+, Chrome 110+ | Android 12+, Chrome latest |
| iOS | iOS 13, Safari 13 | iOS 15+, iPhone 11+ | iOS 17+, iPhone 12 or newer |
| RAM | 2 GB | 3–4 GB | 6 GB+ |
| Screen | 5.0″ HD | 6.1″ Full HD | 6.7″+ OLED |
| Connection (slots) | 5 Mbps 4G | 15 Mbps WiFi | 20+ Mbps 5G or fibre WiFi |
| Connection (live casino) | 10 Mbps | 20 Mbps | 30+ Mbps for HD streams |
| Storage on device | 5 MB cache | 20–30 MB | 50 MB for offline assets |

All 13,000+ titles on FatPirate are mobile-compatible without exception. The lobby uses responsive design so the filtering, search and category navigation work identically to desktop. Category breakdown on mobile:
The PWA loads the casino lobby in under 4 seconds on a 5G or fast WiFi connection. Individual slot launches are sub-2-second on modern devices; live casino tables take 4–6 seconds due to the additional stream initialisation. Older devices on 4G see proportionally slower load times but still remain inside playable bounds.
Typical observed loading benchmarks across hardware:
| Device class | Connection | Lobby load | Slot launch | Live table |
|---|---|---|---|---|
| Older 4G phone | 4G EE / Three | 3.5–5.0 s | 2.0–3.0 s | 5.5–7.0 s |
| Mid-range 5G phone | 5G O2 / Vodafone | 2.5–3.5 s | 1.5–2.0 s | 4.0–5.5 s |
| Tablet (home WiFi) | 50–100 Mbps WiFi | 2.5–3.5 s | 1.5–2.0 s | 4.0–5.5 s |
| Flagship 5G phone (2023+) | 5G EE / fibre WiFi | 2.0–2.5 s | 1.0–1.5 s | 3.5–4.5 s |
For UK players on metered mobile data plans, WiFi is recommended for extended live-casino or live-sports sessions. The Evolution stream-quality control inside individual tables allows manual downgrades, which cuts data consumption roughly in half while preserving playability.
Periodically, search results surface third-party sites offering «FatPirate APK download.» None of these are legitimate. Three concrete reasons to ignore them:
The safe and supported route is the official PWA installed from fatpirate.com directly into the browser.
Every cashier function works identically on mobile and desktop:
The 24/7 live chat is fully available on mobile. The chat panel opens as an overlay above the current page, which means players can stay in the slot lobby while waiting for a support response. Email support runs through the standard contact form, accessible from the mobile menu.
The absence of a native app is not a downside. The PWA installs faster than any store download (30 seconds versus 3–5 minutes), stays automatically updated, weighs almost nothing on the device and matches the desktop experience function-for-function. Once pinned to the home screen, the player loses any sense of using the browser at all.
Mobile experience score: 8.4 / 10. Half a point off for the limited iOS web-push notification support (an Apple platform restriction), and half a point for slightly slower live-table load times on older devices. Otherwise solid across the board.
Continue: Login & KYC · Bonus mechanics · Mobile withdrawals
The Progressive Web App rests on standard Web App Manifest and Service Worker APIs, which means it runs across every mainstream browser shipping since 2020. The table below maps the practical experience across the device classes British players actually carry, including the edge cases where the install flow needs a workaround.
| Platform | Version | Browser | Supported? | Notes |
|---|---|---|---|---|
| iOS / iPadOS | 13–14 | Safari only | Yes — baseline | Add to Home Screen works; fullscreen launch; no web-push |
| iOS / iPadOS | 15–16 | Safari only | Yes — comfortable | Full PWA parity; biometric autofill via Apple Keychain |
| iOS / iPadOS | 17 or later | Safari only | Yes — optimal | Web-push partially restored, badge counts supported |
| Android | 6.0–9 | Chrome 90+ | Yes — baseline | Install via three-dot menu → Add to Home screen |
| Android | 10 or later | Chrome, Edge, Samsung Internet, Brave, Firefox | Yes — full feature set | «Install app» option in Chrome; biometric login via Android Credential Manager |
| Windows desktop | 10 / 11 | Edge, Chrome | Yes | Installs as a desktop PWA window; pinnable to taskbar |
| macOS desktop | Big Sur or later | Safari, Chrome, Edge | Yes | Safari 17+ adds proper PWA-to-Dock install on macOS Sonoma |
| Older Android (5.x) | 5.0–5.1 | Chrome legacy | Partial | Browser play works; home-screen pin uses shortcut rather than PWA |
The only outright unsupported configuration is iOS through a non-Safari browser for the install step itself — Chrome, Firefox and Edge on iOS still render the casino correctly but cannot trigger Add to Home Screen because of Apple platform rules.
The most common mobile-casino question is whether to install a PWA or hunt for an APK. The comparison below sets the two architectures against each other across the dimensions a UK player actually cares about. The result is decisive in one direction, but the reasons matter.
| Criterion | FatPirate PWA | Third-party APK |
|---|---|---|
| Source | Direct from fatpirate.com | Unofficial mirror sites — not signed by FatPirate |
| Install time | Under 30 seconds via Add to Home Screen | 3–5 minutes including permission overrides |
| Install size | Under 5 MB cache | 30–80 MB APK package |
| Updates | Automatic server-side, no player action | Manual download of each new APK build |
| Security signing | HTTPS-served by the casino domain | Unverified; common malware vector targeting login and payment data |
| Play Protect warnings | None — not flagged by Google | Frequent «Harmful app» warnings; install-source override required |
| Slot-launch reliability | Always current with provider integrations | Version drift breaks newer slot releases |
| Account safety | No anti-tamper triggers | Risk of compliance lock if modified client detected |
| Storage hit on device | Negligible | Significant; grows with cached assets |
| Removal | Long-press icon → Remove (instant) | Standard Android uninstall; cached data may persist |
The verdict reads off the table: every criterion favours the PWA. The third-party APK route exists in search results because affiliate-style sites monetise the download, not because the casino itself ships one.
A Progressive Web App is more than a desktop site shrunk to phone size — it taps into native mobile capabilities that browser-only access cannot reach. The six cards below cover the features that make a UK player’s phone genuinely more useful for FatPirate than the desktop browser tab.
Android delivers full web-push for bonus credit alerts, withdrawal confirmations and tournament leaderboard changes. iOS 17 partially restores push for installed PWAs — opt-in at install prompt.
Face ID and Touch ID on iOS, fingerprint on Android. The login fields integrate with Apple Keychain and Google Password Manager so re-entry takes a single tap rather than a password.
The PWA launches without the browser address bar or tab strip — identical to a native app. Slot reels and live tables get the full screen, and there is no accidental tab-swipe to lose the session.
Static pages (terms, FAQ, contact, payment-method guides) cache for offline reading. The cashier, live lobby and game launches require connectivity; the Service Worker caches the shell to skip cold loads.
Live casino streams support PiP on supported Android 8+ and iOS 14+ devices. The dealer feed floats over the home screen or other apps while the bet panel sits in the main PWA window.
One-tap toggle between casino and sportsbook wallets without re-authenticating. Crypto wallets (Trust Wallet, MetaMask, Exodus) deep-link into the deposit flow without leaving the PWA window.
The cumulative effect is that the home-screen FatPirate icon behaves like a native app in every meaningful way — without consuming the storage, the install time or the security risk that comes with a downloaded APK.