Two ways in from a phone: the browser build, which needs no install, and an Android package that adds biometric sign-in and alerts. The catalogue and the cashier are identical in both.
The site is written in HTML5, so every game streams from the server and renders inside the browser. Nothing is stored on the handset beyond a session token, and updates appear without any action from the user.
The Android package wraps that same site in a shell. Sign-in becomes a fingerprint, promotions arrive as notifications, and the shortcut lands on the home screen. The games and prices do not change.
The result behaves like an app and occupies almost no storage. For an iPhone this is the only installation route, since the operator publishes no iOS package.
Android users download the file from the site rather than from a store, so installation from unknown sources has to be permitted once in the security settings. Updates then arrive from the same place, which means checking the site occasionally rather than relying on automatic upgrades.
| Operating system | Browser | Min. screen | Status |
|---|---|---|---|
| Android 7.0+ | Any modern | 4.5" | Full support plus installable package |
| iOS 13+ | Safari / Chrome | 4.7" | Full browser support, home-screen shortcut |
| Windows / macOS | Any modern | — | Full support |
| Feature | Android package | Mobile browser |
|---|---|---|
| Full game catalogue | Yes | Yes |
| Live dealer tables | Yes | Yes |
| Sportsbook and cash out | Yes | Yes |
| Push notifications | Yes | No |
| Biometric sign-in | Yes | No |
| Storage used | Yes | None |
The full catalogue is present, but browsing it is slower. Filters collapse into menus, so finding a specific title by studio or mechanic takes more taps than it does on a desktop lobby.
Live play suffers most. Multiple tables side by side are impractical, side-bet panels overlap the video, and roulette statistics are cut down to fit the width.
The betting slip is the other compromise. Long accumulators and detailed bet histories are harder to check on a phone, which matters because an unchecked slip is where margin compounds unnoticed.
A slot is light once loaded, because each spin exchanges a small instruction and a result. Live dealer tables are the opposite: a continuous video stream that runs for as long as the table is open.
Keeping live play on Wi-Fi and slots on mobile data is the sensible split. Document uploads for verification are also better done on Wi-Fi, since a rejected photograph usually means repeating the upload.
A phone does not change the house edge, but it changes how often the edge is applied. One-tap repeat betting, autoplay and in-play markets all raise the number of settlements per hour, and settlement count is what sets the bill.
Deposit limits and session reminders travel with the account, so a limit set on desktop still applies on the handset. Setting one before the first mobile session is the simplest control available.
No package is published for iOS. Safari runs the full site, and a home-screen shortcut gives the same full-screen behaviour without an install.
No. The catalogue, the live tables and the sportsbook are identical, because the installed build loads the same site.
The file comes from the site rather than a store, so the system asks for permission once. Download only from the operator's own address.
Yes. The cashier, the document upload tool and the account area all work on mobile, with the same limits as desktop.
Slots use very little after loading. Live dealer video is far heavier, so a long session at a table is best kept on Wi-Fi.
The app clears turnover faster, which is not the same thing. Faster play means the same edge is charged more often per hour.