There is no native download in either store. The platform runs in the mobile browser instead. For payments that is an advantage rather than a compromise. Your banking app, your wallet app and your authentication codes all live on the same handset as the cashier.
A native app is a downloaded shell around the same web content. Removing the shell removes the store review queue, the storage cost and the update cycle, and leaves the game catalogue untouched.
What you lose is small but real. There are no push notifications, nothing works offline, and the site does not appear in an app store listing where you might expect to find it.
| Device | Supported | Access Method |
|---|---|---|
| iOS (iPhone/iPad) | Yes | Mobile browser (Safari) |
| Android | Yes | Mobile browser (Chrome) |
| Desktop (Windows/Mac) | Yes | Any modern browser |
Open the site in Safari, tap the share button in the toolbar, scroll to Add to Home Screen and confirm the name.
Open the site in Chrome, tap the three-dot menu and choose Install app or Add to Home screen when the prompt appears.
Chrome and Edge show an install icon in the address bar, which pins the site to a window without browser tabs.
The pinned icon opens a full-screen frame with no address bar. Sessions and saved preferences carry over, because it is the same browser engine underneath.
Card payments increasingly finish inside your banking app rather than on a web page. On a handset that handoff happens automatically; on a desktop it needs a second device and a code typed across.
Wallet payments follow the same pattern. Skrill and Neteller approvals arrive in the wallet app, so a phone deposit is usually one tap where a desktop deposit is a login.
Crypto is the clearest case. The wallet holding your keys is normally on the phone, and scanning an address on the same screen removes the copy-and-paste step where mistakes happen.
One warning: do not start a payment on one device and finish it on another. Switching mid-transaction breaks the session and the attempt fails without any money moving.
Slots send game state rather than video, so they are light on data and tolerate a weak signal. A round simply resolves a moment later.
Live dealer tables are a video stream and use far more data. They also cannot be paused, so a dropped connection during a hand is settled without you.
On a metered mobile plan, keep live tables for a stable connection and use slots when you are moving between networks.
No. Access is through the mobile browser, and the home screen shortcut is the closest thing to an installed app.
No. The catalogue is the same, because both versions load the same titles from the same providers.
Safari and Chrome on iOS 14 and above, Chrome and Firefox on Android 8 and above, and Edge or Chrome on desktop.
Yes, and the rules do not change with the device. The same minimums and the same method matching apply as on a desktop.
The bank confirmation step is usually the reason. On a handset it hands off to the banking app; on a desktop it needs a code that can time out.
Yes. It loads the live site each time, so there is nothing to update manually and no version to fall behind.
