No download, no store listing, no package to sideload. The whole platform is a browser build that can be pinned to a home screen in about ten seconds — and the phone is also where the account produces its most revealing data.
The mobile site runs on iOS, Android, tablets and desktops from the same address, resizing rather than stripping features out. The table below sets out what each platform needs.
| Operating system | Browser | Min. screen | Status |
|---|---|---|---|
| iOS 14+ | Safari / Chrome | 320px | ✓ |
| Android 9+ | Chrome / Firefox | 320px | ✓ |
| Windows / macOS | Any modern | — | ✓ |
| Tablet | Any modern | 600px | ✓ |
Open the site in Safari, tap the share icon, then choose Add to Home Screen. The icon launches in full screen with no address bar.
Open the site in Chrome, tap the three-dot menu, then choose Install app or Add to Home screen. Chrome keeps the session cookie, so the login survives.
The shortcut behaves like an installed app but occupies no meaningful storage, and updates arrive with the website rather than through a store.
| Feature | Dedicated app | Mobile browser |
|---|---|---|
| Full game library | Download required | ✓ |
| Live casino | Download required | ✓ |
| Push notifications | ✓ | Home screen only |
| Storage needed | ✓ | None |
The library, the live tables, the cashier, account settings and every bonus screen all survive the move to a small display. Support is reachable from the same menu.
Three things are genuinely worse. Feature-heavy slots redraw more slowly on older handsets, multi-table live play is impractical below tablet size, and detailed account history is easier to read on a wide screen.
Live dealer tables are by far the heaviest part of the platform, because a video stream runs continuously whether or not a hand is in play. Slots are light by comparison, since the reels render on the handset and only results travel.
On a capped mobile plan the sensible split is simple: play reels on mobile data, save live tables for wi-fi. Lowering stream quality in the table settings cuts the load further.
A desktop account tends to produce one long session a week. A phone account produces many short ones, often late at night and often squeezed between other tasks, and a scoring model reads frequency more loudly than duration.
That matters because frequency is one of the clearest triggers for a VIP invitation. Pinning a shortcut removes the friction of typing an address, and lower friction raises session count — which raises the very number the recruitment model watches.
The missing push notification is, unusually, a point in the browser build's favour. A website cannot interrupt an evening the way an installed app can, so the timing of any contact stays under your control.
If a host already has your telephone number, the phone becomes the channel by default. Asking for messages through the on-site message centre instead is a reasonable request, and a host with authority can set that preference.
Deposit limits, loss limits, session reminders and time-outs all work identically in the mobile build. Setting them takes a minute from the account menu, and a tightened limit applies at once.
No. The platform is delivered as a browser site, so nothing installs and nothing needs updating. A home-screen shortcut supplies the icon and the full-screen launch.
Yes. The library, the live tables and the cashier are identical to the desktop build, because the same site is being served to a narrower screen.
Usually. The shortcut uses the browser's session cookie, so a login survives until the cookie expires or the browser data is cleared.
Effectively none beyond the browser cache. That is the main practical advantage over a downloaded package on a handset with limited space.
Yes. Promo codes, deposits and the wagering counter all behave the same way on mobile as they do on a desktop machine.
Indirectly. Mobile play tends to raise session frequency, and frequency is a stronger signal in a retention model than the length of any single visit.