Nothing to download from a store. The site is a progressive web app: the browser is the client, and the phone carries the whole cashier — deposits, withdrawals and document uploads included.
There are two ways to use the site on a phone, running identical code. Open it in a browser tab and everything works at once. Or add it to the home screen, and the same site opens from an icon in a full-screen window with no address bar.
The second option is what people mean by the app. Nothing is installed in the usual sense: no store account, no package download, no permissions dialogue, no storage claimed. Because the code stays on the server, updates apply the moment you open it and there is no version to fall behind on.
The benefit is small but real: a full-screen window gives back the strip of space the address bar occupies, which matters on a slot reel.
Use Safari on iPhone or iPad and Chrome on Android. Other browsers run the site, but some omit the home-screen step.
Tap the share icon, scroll the list, choose Add to Home Screen and confirm the name.
Open the three-dot menu and pick Install app, or Add to Home screen where that wording appears instead.
Launch from the icon and log in. The session is remembered as a browser tab remembers it.
| Operating System | Minimum Version | Status |
|---|---|---|
| Android | Android 5.0+ | Fully supported |
| iOS | iOS 11.0+ | Fully supported |
| Tablet | Any modern | Fully supported |
Every payment function on the desktop site is on the handset: deposit, withdrawal, transaction history and the verification upload area share one account menu.
One part is better on a phone. Verification stalls over unreadable documents more often than anything else, and a phone camera captures a passport or a utility bill more legibly than a scanner. Shoot it flat, in daylight, with all four corners in frame, and the check usually clears first time. The login guide lists what each file must show.
Withdrawal speed does not change with the device. A phone request joins the same review queue as a desktop one, so the rail still decides the timing: 1–6 hours for e-wallets and crypto, 1–3 days for cards and bank transfer.
| Feature | Web App | Native App |
|---|---|---|
| Full game library | Yes | Download required |
| Live casino | Yes | Yes |
| Push notifications | Home screen only | Yes |
| Storage needed | None | Storage needed |
| Instant updates | Yes | Manual |
The honest gap is notifications. A native app can reach you when closed; a web app cannot, so alerts arrive by email instead — a loss if you want reminders, a gain if you do not.
Data use varies by game type. Slots and table games send little, because the animation runs on the handset. Live dealer tables are video, and video is expensive: a long live session on mobile data can cost as much as streaming a film. On a metered plan, save live play for a wireless network.
No. Real-money gambling apps face store restrictions in many regions, so the operator ships a web app instead. Anything claiming to be an official download is not.
No. Games and balances are served live, so a connection is needed throughout. The icon only changes how the window is drawn.
Android 5.0 and iOS 11.0 are the stated floors. Older hardware loads the lobby but struggles with live video, where a weak connection hurts more than a slow processor.
Yes. Registration, deposit and opting into the welcome package all work in the mobile cashier.
No. Each round resolves on the server, so an interrupted spin completes and the result appears when you reconnect. Live tables are less forgiving, since a bet must land before the timer ends.
It stores a session in the same way a browser tab does. Use a device passcode and do not enable an automatic sign-in on a shared handset.
A device you carry everywhere makes short sessions easy to start and hard to count. Set a deposit limit, switch on reality checks so a reminder interrupts a long session, and keep promotional email off if it tends to pull you back. Free confidential support is available if play stops feeling like entertainment.