There is nothing to download, and that is a feature rather than a gap. The whole casino runs in a mobile browser, and a home-screen shortcut gives it an icon and a full screen while taking a vanishingly small share of your storage.
An installable casino app has to be fetched, updated and granted room on your device. A browser site is fetched on each visit and updated the moment the operator ships a change, so the version you are using is always the current one.
The differences run in your favour on nearly every axis. Nothing to download before the first spin. No storage claimed. No manual update that leaves you a release behind the cashier. And no app-store account in the loop, which matters because gambling apps are restricted or absent in several stores.
What you give up is narrow: the notification behaviour an installed app has, and offline access — which a casino cannot offer in any case.
The site is a progressive web app, so both major platforms will pin it.
| Feature | Installed app | This site in a browser |
|---|---|---|
| Getting started | Download, then install | Open and play |
| Storage used | Hundreds of times more | Effectively none |
| Updates | Manual, and can lag | Automatic on every load |
| Full game library | Supported | Supported |
| Live dealer tables | Supported | Supported |
| Cashier and bonuses | Supported | Supported |
| Notifications | Full | Browser only |
The library is not trimmed for mobile. Slots are built responsively by the studios themselves, live tables stream at whatever your connection supports, and the cashier is identical. What genuinely differs is screen area: a phone shows perhaps a third of the lobby rows a desktop does, so search and filters earn their keep.
Not every part of the casino costs the same to run on a mobile connection. A slot spin is a short exchange of instructions with the server, because the graphics arrived when the game loaded. A live table is continuous video, so a minute at a live table moves roughly an order of magnitude more data than a minute of spinning reels, and it drains the battery in proportion.
On a metered connection that makes slots the cheap option and live game shows the expensive one. Connection stability matters more than raw speed: a stream tolerates a slow but steady link far better than a fast one that drops, because the betting window closes on the dealer's clock whether or not your video has caught up. If the signal is unreliable, play slots — a spin resolves on the server and credits when you reconnect.
| Operating System | Browser | Min. Screen | Status |
|---|---|---|---|
| iOS 13+ | Safari, Chrome | 4.7″ | Supported |
| Android 8+ | Chrome, Firefox | 4.5″ | Supported |
| Windows | Any modern | Any | Supported |
| Tablet / iPad | Any modern | 7″+ | Supported |
The requirement is a current browser rather than a fast phone. The games are HTML5 and scale to whatever screen they find, so a device several years old runs the lobby perfectly well.
No download is needed, and gambling apps are restricted in several stores. Use the browser and pin the site. If you find an app claiming to be this casino, check it against the official site before installing.
No. Games, balances and bonus progress all sit on the operator's servers, so a connection is always required.
All of them. Portrait works for most, though landscape gives the betting grid noticeably more room.
Yes. Balance, bonus turnover and verification status belong to the account rather than the device.
Slots, by a wide margin. Live tables carry continuous video; slots exchange short messages once the initial load is done.
Not on the same device. The session persists between openings, although the operator signs you out after a period of inactivity.