Installation paths and steps
We offer three installation methods for different user preferences. Android users can download our APK directly from our site without requiring Google Play Store access — useful in regions where store restrictions apply or for users who prefer direct-source installation. iOS users access the app through Safari or any iOS browser; we host a shortcut that installs our web app to the home screen with native-like behaviour. Web users on desktop or mobile can simply bookmark our responsive site, which functions as a full-featured app with offline caching.
Android APK
- Download the APK file from our site.
- Enable "Unknown sources" in device settings.
- Open the downloaded file and confirm installation.
- Log in with your svip9 h5 account credentials.
iOS and web
- Open our site in Safari.
- Tap the share button and select "Add to Home Screen".
- Name the shortcut and confirm.
- Log in with your svip9 h5 account credentials.
All three paths lead to the same account backend. A balance update on the Android app appears instantly in the iOS web view and desktop browser. Push notifications on Android and iOS alert you to market changes (new Liga 1 odds, live roulette table availability, settlement results) in real time. Browser notifications on desktop work similarly if you grant permission.
App vs. browser: strengths and differences
Our native Android app and iOS web app (PWA) offer offline caching that the mobile browser alone does not. Downloaded market data for upcoming Liga 1 rounds persists even if your internet drops; you can still review odds, check your account balance, and view settlement history. Once reconnected, any pending bets or withdrawal requests sync automatically. Push notifications on app installations deliver settlement alerts within seconds of official league confirmation, whereas browser-only users must refresh the page manually.
Speed is a measurable difference. The native Android APK loads blackjack and Sic Bo live streams with lower latency than a browser tab because it bypasses the browser rendering layer. Slot games like Sweet Bonanza and Mahjong Ways spin with smoother animations on app installs. However, the PWA (web app added to home screen) closes most of that gap; modern browsers use the same rendering engine whether accessed as an app shortcut or a regular tab. If you prefer not to manage APK updates or enable unknown-source permissions, the PWA delivers non-specific info of the app's performance with zero friction.
Device compatibility and requirements
We support Android 7.0 and later on phones and tablets. Older Android versions lack the security protocols our backend requires for encrypted session tokens, so installation on Android 6 or earlier will fail. iOS users need iOS 12.0 or later; iOS 11 devices cannot execute the web app's service-worker code. On both platforms, we recommend at least 150 MB of free storage for the app cache and initial asset download. Device RAM requirements are minimal — even a 2 GB RAM phone runs our app without lag, though 3 GB or more ensures smooth multitasking.
Common installation issues and solutions
Android users occasionally see "Unknown sources" warnings because our APK is distributed directly, not through the Play Store. This is normal and safe; we sign all APK releases with our private certificate, and you can verify the signature in your device settings. If installation fails, clear your Downloads app cache and retry. iOS users attempting to add our web app to the home screen sometimes experience a blank screen if Safari's offline storage is full; clear Safari cache and cookies, then try again. If the app icon appears but opens to a blank page, force-close Safari, clear its browsing data, and reinstall the shortcut.
We also recommend keeping your device's system software up to date. Running the latest Android or iOS patch ensures compatibility with new TLS certificate standards our backend periodically rotates for security. If you encounter persistent installation or login failures, you can verify your account status by logging in via desktop browser, checking your account settings, and ensuring two-factor authentication is enabled. This precaution prevents unauthorised account access if a device is lost or shared.
Data, permissions, and account security
Our mobile app requests only the permissions it needs: internet access, camera (if you choose to scan QR codes for deposit QR-code payments like QRIS, e-wallet, or mobile banking), and notification permission for push alerts. We do not access your contacts, location, or photo library. All communication between the app and our backend uses TLS 1.3 encryption; your username, password, and payment details never transmit in plain text. When you log in, the app stores an encrypted session token on your device; if you log out or uninstall, that token is deleted immediately.
KYC (know-your-customer) verification happens the first time you request a withdrawal or deposit above a certain threshold. We ask for a government-issued ID photo and sometimes a selfie; these documents are encrypted, stored separately from your account data, and deleted after verification (typically within 24 hours). We do not share your personal data with third parties except as legally required for fraud prevention or anti-money-laundering compliance. Your payment method information (bank details, e-wallet linked accounts) is tokenised — we store a reference ID, not the actual number. Deposits via local payment, online payment, e-wallet, mobile banking, local payment, or online payment are processed through official payment gateways; we never see your PIN or password.
