What the app does and does not do
The companion app mirrors the same 973 titles as the in-house lobby: provider shelves, search by name or ID, and a short path to the operator's game launcher. It does not replace the lobby; it extends it into a touch-first surface.
Inside the package you will find the same eight provider rooms, the same filter set, and the same shortlist behavior. Account state, balance, and bonus timers are shared - what changes is the chrome around them.
Install path by platform
Android: the operator publishes a native package on the canonical store. If your store does not surface it, the profile page lists the verified fallback URL. Never install a package from a third-party APK mirror - that path is the most common cause of compromised accounts.
iOS: in regions where the store does not list the operator app, the operator hosts an in-browser launcher. The launcher is not an app-store install; it is a progressive web entry that the operator owns and signs.
Network restrictions: if the operator package is unavailable in your region, the app surfaces a clear compliance notice. We do not recommend bypassing that notice via VPN; doing so violates the operator's terms and may freeze withdrawals.
Troubleshooting playbook
Stuck on launch: confirm the device is on the latest stable store build. If the launcher still hangs, send a screenshot to the support desk via /contact/ - the team will cross-check the operator's status page.
Login loop: reset your password from the operator's website, not the app. Browser-side reset triggers account recovery emails faster because the operator's mail pipeline treats web sessions as trusted.
Slow search: the search index lives in the operator's app, not in your local cache. Switch to a stable network, clear the in-app cache, then retry - most slow-search reports resolve after a cache flush.
Operational facts
Companion app vs progressive web entry
The companion app is a native package: faster cold-start, lower battery use on long sessions, and direct integration with the device biometric prompt. The progressive web entry is a launcher that opens in your default browser; it does not require an install but does rely on a stable network connection.
For users on Android devices with limited storage, the progressive web entry is the safer choice because no package footprint accumulates on the device. For users who play daily sessions of 30 minutes or longer, the native package is the smoother experience because it avoids browser-side memory reclamation.
Account sync and shared state
Account state is owned by the operator, not the lobby or the app. Balance, bonus timers, recent activity, and VIP progression all sync from the operator's account server. Sign in on one device and the same view appears on the other within a few seconds.
If you see stale state, the most common cause is the device running the app in background-suspended mode. Force-quit and reopen; the app re-pulls account state on launch.
Permissions the app requests
Notifications: optional. Used for promotion reminders and race-cutoff warnings. Disable in-app from the settings panel.
Biometric prompt: optional. Used for fast re-entry. Fall back to PIN if your device biometric sensor is unreliable.
Storage: minimal. Used for cached room thumbnails to reduce repeat-fetch latency. Clear from the in-app cache settings if you need a fresh fetch.
Update cadence
The app follows a regular update cadence. Major versions land monthly with new provider integrations; minor versions land weekly with bug fixes and lobby-link refreshes.
Auto-update is enabled by default on most stores. If you keep auto-update off, the lobby surfaces the latest version on the app profile page so you can confirm before opening the store entry.
Regional availability and fallback
If the operator's native app is not available in your region, the app profile page surfaces the verified progressive-web launcher URL. The launcher opens the same operator lobby in your default browser without requiring an install step.
When the operator changes its regional availability list, the lobby updates the app profile within one crawl window. The change is also reflected in /news/ under the operator-updates tag.
Operational facts
App vs progressive web launcher
The operator offers two ways to reach the same room surface: a native app distributed through the canonical store entry, and a progressive web launcher that runs in any modern browser without installation. Both surfaces share the same account state, the same KYC flow, and the same cashier. The choice between them is environmental, not strategic.
Native app strengths: faster cold-start because the launcher binary and the asset bundle are preinstalled on the device. Push notifications for promotion timing and account-state changes. Background presence means the operator can pause and resume a session without a re-auth round-trip. Touch-optimised gesture handling for live-dealer camera controls and slot bet sizing.
Progressive web launcher strengths: zero install, no APK mirror risk, runs on devices the operator does not ship a native binary for. Always the latest version because there is no binary to upgrade. Cleaner for shared devices and for users who prefer not to install commercial apps. The downside is no background presence and a slower cold-start on the first session because the bundle is fetched on demand.
If you switch between the two, your session cookie travels with the operator account, not with the device. Logging out on one surface logs you out on the other. The lobby does not store your login state; it only stores the filter cookie. Treat any "remember me" tickbox as scoped to the operator, not to the lobby.
Installing safely
Install the native app from the canonical store entry only. The operator does not distribute APKs through APK mirror sites and does not ask you to enable "install unknown apps" to reach the lobby. If a third-party download link arrives via SMS or chat claiming to be a faster installer, it is not the operator; close the message and use the store entry.
For the progressive web launcher, the URL is the operator domain surfaced by the lobby PLAY NOW button. The launcher prompts you to add a shortcut to your home screen the first time you visit; accepting the prompt installs an app-style icon that opens the launcher in full-screen mode without the browser chrome.
The lobby surfaces a small status flag on each provider room card indicating whether the operator route is verified on the day of your visit. The flag is informational; it does not block you from clicking through. If you want to be extra cautious, open the operator route in a private window first, confirm the domain matches the lobby expectation, then continue in your normal browser.
What the lobby never does: it never asks for your operator credentials, it never emails you a login link, it never stores your account state. If a screen inside the lobby claims to be a login surface, it is the operator's screen - confirm the domain before you type anything. The lobby is editorial, not transactional.
Troubleshooting the install
If the native app does not appear in your store search, the operator may not have shipped a binary for your region. The lobby cannot override the operator's distribution policy; the right next step is to use the progressive web launcher, which runs in any modern browser without installation and shares the same account state.
If the progressive web launcher fails to load, the most common cause is a regional network restriction on the operator domain. The lobby surfaces the regional availability flag on each provider room card, but the flag is informational; if your region is restricted, the lobby will not unblock it. A VPN is not recommended because the operator's KYC step will catch mismatched regions and withdrawals freeze until the mismatch is resolved.
If you install the native app and it refuses to update, the most common cause is the auto-update toggle on the device. The lobby cannot toggle the setting for you; the operator's support channel is the right path. The lobby's editorial position is that the canonical store entry always carries the latest version, so reinstalling from the store is a safe recovery path.
If you switch between the native app and the progressive web launcher, your session cookie travels with the operator account, not with the device. Logging out on one surface logs you out on the other. The lobby does not store your login state and does not know which surface you prefer; the operator knows both.