Tier-1 EU Operator: How Native Mobile Apps Took 39% of Daily Active Players

Most of the operator’s audience already arrived on mobile, but the product lived inside a browser. Every return visit depended on a player recalling a domain or keeping a bookmark. Push messaging was out of reach, and authentication ran on passwords. Store distribution answered none of it, since review cycles and third-party policy stand between a brand and its own players. Kanggiten has built native apps since 2019, ahead of the point when they became standard in iGaming. What the operator needed was an owned entry point, controlled end to end, including how the app reached devices.

Kanggiten built native apps instead of a WebView shell. WebView is cheaper and faster to ship, and Kanggiten builds those where they fit, but it closes off the hardware. Native kept it open. Biometric login replaced password-only access, and every withdrawal now requires biometric confirmation. 2FA adds a second check at sign-in. A retention layer runs on top of that, with in-app cashback, timed pushes and accelerometer games. On Android, distribution and failover were built as part of the product rather than handled by a store.

Three mechanics run inside the app and nowhere else. In-app cashback collects a player’s losses into a savings bank that releases on a fixed weekday, which builds a weekly return habit and holds paying users. Trigger pushes fire at the moment a reward becomes claimable, so the message lands at peak intent rather than on a schedule. Accelerometer games turn the device itself into a mechanic. Players shake the phone to release a bonus, and shake intensity sets the reward size.

• Adoption: 76% of active users played at least once
• Repeat play: 81% played 2+ times
• Depth: 48% played 3+ times
• Conversion: 22% became paying users

Distribution runs outside Google Play. The Android app ships from a self-hosted server with its own install and update system, which keeps release timing with the operator instead of a store review queue. Three update modes cover different cases, from silent through recommended to forced. Smart domain rotation moves the app to a backup when a domain drops, so sessions hold. Cross-platform autologin carries a web session into the app and extends it while the player stays active.

• Android distribution: self-hosted, independent of store review cycles
• Update control: silent, recommended and forced modes
• Domain failover: automatic switch to backup, sessions uninterrupted
• Session handoff: web to app autologin, extended on activity