Realtime Gaming’s migration from a Windows-only Flash and DirectX stack to HTML5 was slower than most of the industry, but it is now substantially complete for the Real-Series catalog. The result is a mobile experience that runs entirely in the browser, with no app store distribution, and which behaves noticeably differently on iOS than on Android for reasons rooted in platform policy rather than in the game code.
This page documents that behavior: how the instant-play bundle loads, what a Progressive Web App installation does and does not give you, where Apple’s WebKit constraints bite, how Android Chrome differs, and what latency budget an RTG table game actually operates within. It is a technical reference with no promotional content and no operator recommendations.
Why There Is No RTG App Store App
Apple’s App Store Review Guidelines require real-money gambling applications to be submitted by the licensed operator itself, geographically restricted to jurisdictions where that operator holds a licence, and reviewed against local regulatory requirements. Google Play applies an equivalent policy through its country-by-country real-money gambling programme. Neither store approves applications for offshore-licensed operators serving US states without state gaming licences.
The consequence is structural: RTG-powered properties cannot distribute native apps to US players through official channels. Every “mobile app” offered by such a site is one of two things — a bookmark to the mobile website, or a Progressive Web App installed directly from the browser. Any prompt to sideload an Android APK from an operator’s own server bypasses Play Protect scanning entirely and should be treated as a meaningful security decision rather than a convenience.
How the Instant-Play Bundle Loads
An RTG HTML5 lobby is a single-page application. On first visit the browser downloads a shared runtime containing the rendering engine, the wallet client and the lobby UI, typically in the region of 2 to 6 megabytes. Individual games are separate asset bundles fetched on demand, usually 3 to 12 megabytes each depending on animation density, and cached thereafter.
| Connection | Typical throughput | Lobby shell | Game bundle (8 MB) | Total to first spin |
|---|---|---|---|---|
| 5G mid-band | 100-300 Mbps | Under 1 s | 1-2 s | 2-3 s |
| LTE, good signal | 20-50 Mbps | 1-2 s | 2-4 s | 4-6 s |
| LTE, congested cell | 3-8 Mbps | 3-5 s | 10-20 s | 15-25 s |
| Home Wi-Fi, cable | 100-500 Mbps | Under 1 s | Under 1 s | 1-2 s |
| Public Wi-Fi, shared | 2-10 Mbps | 2-6 s | 8-25 s | 10-30 s |
Second and subsequent loads should be near-instant from cache. If they are not, cache storage is being evicted, and that eviction behavior is the single largest platform difference between iOS and Android.
iOS Safari: WebKit Constraints That Actually Matter
Every browser on iOS renders through WebKit, including Chrome, Firefox and Edge. Choosing a different browser on an iPhone changes the interface chrome, not the rendering engine, so an RTG rendering bug in Safari will reproduce identically in iOS Chrome.
Storage Eviction
Apple’s Intelligent Tracking Prevention purges script-writable storage, including cache storage, IndexedDB and localStorage, for origins the user has not interacted with in seven days. For a player who visits an RTG site weekly, this means periodically re-downloading the entire game bundle. Installing the site to the Home Screen as a PWA substantially improves persistence because installed web apps receive more durable storage treatment, but the guarantee is weaker than for a native app.
Audio Unlock and Autoplay
WebKit blocks programmatic audio playback until a user gesture unlocks the audio context. RTG bundles handle this with a tap-to-start overlay. If sound is missing after that, the usual causes are the physical ring/silent switch, which mutes web audio on iOS in ways it does not on Android, or a suspended audio context after the app returns from background. Reloading the game restores it.
Background Suspension
iOS aggressively suspends background tabs to reclaim memory. Switching away from a game mid-session — to answer a message, for example — can cause the page to be discarded and reloaded on return, presenting as a logout or a blank canvas. Because RTG’s architecture is server-authoritative, any committed spin result is recoverable on reconnect and the balance is safe; the interruption is a session-state problem, not a wallet problem. Installing as a PWA reduces but does not eliminate discard frequency.
Viewport and Safe Areas
Devices with a notch or Dynamic Island require the viewport-fit meta directive and safe-area inset padding to avoid clipping. Older RTG game bundles that predate these devices occasionally place a spin button or a bet control underneath the home indicator in landscape orientation. Rotating to portrait, where supported, is the reliable workaround.
Android Chrome: More Capable, Less Consistent
Android permits alternative rendering engines, and Chrome’s Blink engine offers capabilities WebKit restricts. In practice RTG bundles behave more predictably on Android in three specific respects.
- Storage persistence. Chrome does not apply a seven-day eviction window. Cached bundles survive until storage pressure forces eviction, so repeat loads are more reliably instant.
- PWA installation. Chrome fires a native install prompt when a valid web app manifest and service worker are present, and installed PWAs on Android receive a real launcher icon, a separate task-switcher entry and a WebAPK shell that behaves close to a native application.
- Background tolerance. Backgrounded tabs are throttled rather than immediately discarded on most devices, so brief app switches usually preserve session state.
The trade-off is hardware fragmentation. RTG’s WebGL renderer is comfortable on mid-range and better silicon, but budget devices with limited GPU memory can drop frames during high-density animation such as expanding wilds or cascading feature sequences. Because outcomes are computed server-side, dropped frames are cosmetic and never affect results, but they do degrade the experience. Manufacturer battery optimization is a second variable: aggressive power management on some Android skins can throttle a foreground browser tab during long sessions, producing intermittent stutter that resolves after disabling optimization for the browser.
| Behavior | iOS Safari / WebKit | Android Chrome / Blink |
|---|---|---|
| Alternative engines available | No, WebKit only | Yes |
| Cache eviction policy | 7-day inactivity purge under ITP | Eviction under storage pressure only |
| PWA install prompt | Manual, via Share then Add to Home Screen | Automatic prompt with valid manifest |
| Installed PWA integration | Home Screen icon, limited OS integration | WebAPK with launcher and task-switcher entry |
| Background tab handling | Frequent discard | Throttle, discard under memory pressure |
| Audio unlock requirement | Strict, plus silent-switch interaction | Gesture unlock, no silent-switch effect |
| Web push notification support | Installed PWAs only, iOS 16.4 and later | Broad support |
On iOS the browser choice is cosmetic and the meaningful decision is whether to add the site to the Home Screen, because installed web apps get materially better storage persistence and background survival. On Android the meaningful decision is device class: a mid-range or better GPU eliminates most RTG animation stutter, and no software setting compensates for a weak one.
Latency Budgets and Table Games
Slots tolerate latency well because the reel animation runs one to three seconds and comfortably hides a round trip. Table games are far less forgiving. An RTG blackjack hand involves several sequential server round trips — deal, then a request per hit, stand, double or split, then settlement — and each one is exposed to the player as a pause.
| Round-trip time | Typical network condition | Blackjack experience |
|---|---|---|
| Under 80 ms | Fiber or cable, nearby edge node | Feels instantaneous |
| 80-150 ms | Good LTE or 5G | Slight but unobtrusive delay |
| 150-300 ms | Congested mobile, distant server | Noticeable pause on each decision |
| 300-600 ms | Public Wi-Fi, weak signal | Disruptive; hand rhythm breaks down |
| Over 600 ms | Satellite, heavily congested cell | Frequent timeouts and reconnect prompts |
Live dealer content, where a property offers it, is a different technology entirely and is not RTG software. Live tables stream video and rely on optical character recognition to read physical cards and read the wheel, and platforms such as Visionary iGaming publish OCR-to-client latency in the region of 200 to 400 milliseconds on top of the video stream delay. That combined pipeline means a live table needs a stable 3 to 5 Mbps sustained uplink and downlink to avoid betting-window desynchronization, and it is far more sensitive to jitter than any RTG HTML5 game. On mobile data, video streaming also consumes roughly 0.8 to 1.5 gigabytes per hour, which matters on capped plans.
Practical Mitigations
- Prefer Wi-Fi over cellular for table games; jitter, not raw bandwidth, is what breaks them.
- Avoid VPN routing during table sessions. An extra hop through a distant endpoint can add 100 to 200 milliseconds, and it may also conflict with the operator’s own terms.
- Close background tabs and applications before long sessions to reduce memory pressure and discard risk.
- Load the game once on Wi-Fi to populate the cache before moving to cellular; the bundle download is the bandwidth cost, not the gameplay.
- If a spin appears to hang, reload rather than retapping. The result is already committed server-side and will be restored, whereas repeated taps only queue duplicate requests.
Security Considerations on Mobile
Mobile browsers hide most of the URL bar, which removes the strongest anti-phishing signal a user has. Verify the domain deliberately before entering credentials, prefer a Home Screen shortcut created from a verified session over following a link from an email or text message, and never install an APK offered by a gambling site. Public Wi-Fi is acceptable for browsing but is a poor environment for account authentication. Where a platform offers two-factor authentication, enabling it is the highest-value security action available, since account takeover is a far more common loss mechanism than any technical exploit of the game software.
Responsible Play Note
Mobile access removes the natural session boundaries that a desktop client imposed. A PWA icon on a home screen sits alongside messaging and social apps and invites the same reflexive opening, and short repeated sessions accumulate far more spins than most players estimate. Use the deposit, loss and session-time limits available in account settings, consider removing the shortcut if it is being opened out of habit rather than intent, and enable device-level screen-time controls if useful. In the United States, confidential help for gambling problems is available around the clock at 1-800-GAMBLER.