Download the rummy app
Two install paths lead to the same app. The official store is the default. The manual APK is the fallback for phones that do not have the store, or for users who want the version pinned by file checksum.
Store install
The fastest path is the Google Play Store on Android or the Apple App Store on iOS. The store handles the signature check, the update channel, and the refund window. Open the link from the operator's own site so the package name matches the operator's brand, not a lookalike.
What to confirm before tapping Install
The developer name on the store listing should match the operator's legal entity. The install count and the date of the last update are a soft signal. The reviews that mention real withdrawal timelines are the strongest signal.
APK install
Manual APKs are useful when the store is unavailable, or when the operator pushes a version ahead of the store release. The trade-off is that the signature check and the update channel shift from the store to your phone.
Four checks before installing
The APK must come from the operator's own domain. The SHA-256 checksum must match the figure on the operator's download page. The "Install unknown apps" toggle must be allowed only for the browser you are using in that moment. The first launch must show the operator's branded login, not a third-party prompt.
What to revoke later
After the install, turn the "Install unknown apps" toggle back off. The OS-level path is the only interception point that catches a drive-by APK on the next browser session.
Storage and battery
The app is roughly 60 to 120 MB on first install. Cache grows with use; the wallet screens cache more than the table screens. Set the OS-level data-saver for the app if you play on a metered connection.
Open the operator in a new tab
Continue to the operator's own download page to pick the store route or the manual APK route, and to read the version notes for the build they ship today.
The first install and every install after it
A first install asks for permission to send notifications, to access storage, and to use the network. A subsequent install on a phone that already had a previous version is faster because the OS preserves the user data directory. The first launch after either install forces the credential screen.
What the first install does differently
The first install creates the user data directory, registers the app with the OS, and pulls the initial lobby cache. The first install does not register a wallet, does not run the KYC, and does not charge the deposit. The KYC and the deposit are gated by the credential screen.
What the subsequent install preserves
The subsequent install preserves the local cache, the user data directory, and the OS-level notification token. It does not preserve the session; the player is logged out at the credential screen on every install. The wallet lives on the operator's server, not on the phone, so the balance is not at risk during the reinstall.
What to do before reinstalling
Before reinstalling, confirm the registered phone is in hand, confirm the registered bank account is accessible, and confirm the PAN is on file. The reinstall itself does not require KYC to be redone; the existing KYC is bound to the PAN, not the phone. The single action that helps is to log out from the session-management screen before the reinstall so the older session is closed cleanly.
For the related read on the in-app session and the second factor that gate the credential screen, see the login page. For the wider sweep of trust signals that matter on the install, see the safety checklist.
The store install or the manual APK: which one to pick
The store install is the default. The manual APK is the fallback for phones that do not have the store, for users who want a pinned version, or for users behind a corporate network that blocks the store. The two install paths converge on the same binary on the operator's server.
When the store is the right choice
The store is the right choice when the phone has the store, when the player wants auto-updates, and when the player wants the store's refund window. The store handles the signature check, the update channel, and the install count that shows the install size and the recent reviews.
When the manual APK is the right choice
The manual APK is the right choice when the store is unavailable, when the player wants a version pinned by SHA-256, or when the operator has pushed a build ahead of the store release. The manual APK shifts the signature check from the store to the player.
What the trade-off looks like
The store is easier. The manual APK is more transparent. The two paths share the same wallet, the same KYC, and the same session model. Switching from the store to the APK is a clean uninstall-and-reinstall; the wallet is bound to the PAN, not the install method. The point that follows is simple: pick the path that matches the phone and the network, not the path that matches a preference.
For the related read on the SHA-256 checksum that catches a corrupted APK, see the APK download page. For the related read on the install path that affects the resync behaviour, see the app page.
The OS-level data-saver toggle and the operator's handshake
The OS-level data-saver toggle limits background network use on a metered connection. The operator's app does a small handshake at first launch to confirm the cache directory and the lobby endpoint. The handshake is the first network call after the install.
What the handshake carries
The handshake carries the install ID, the OS version, the app version, and the lobby endpoint. The handshake does not carry the credential, the PAN, the Aadhaar number, or the wallet balance. The handshake is what lets the operator route the player to the closest table server.
What the data-saver toggle does
The data-saver toggle pauses the handshake when the app is in the background. The toggle does not pause the handshake when the app is in the foreground. The toggle also delays the lobby thumbnail cache rebuild by up to fifteen minutes on a metered connection.
What to do on a metered connection
Turn the data-saver toggle off for the operator's app during the first launch and during the table join. The lobby will load faster and the table will seat the player faster. The data-saver toggle can be turned back on once the player is at the table, where the network use is steady and predictable.
For the related read on the resync window that catches a network drop mid-hand, see the app page. For the related read on the OS-level data-saver toggle that affects update delivery, see the app page's updates section.
How the operator ships a patch and how a phone receives it
A patch is a small update that ships between full versions. The operator ships patches through the store on a roughly two-week cadence. Manual APK patches arrive as a new file on the operator's download page. The phone receives the patch as a delta against the installed binary.
What the patch contains
The patch contains the binary diff, the lobby endpoint update, and the responsible-play screen update. It does not contain the wallet ledger or the KYC documents. The patch is signature-checked by the store or by the SHA-256 checksum on the operator's download page.
When to apply a patch
Apply the patch when the store prompts, when the operator's download page shows a new build, or when the in-app version screen reports a mismatch. The patch is a low-risk action: it does not require a logout, does not require a KYC re-run, and does not affect the wallet balance.
What to do if the patch stalls
Confirm the phone has at least 200 MB of free storage, retry on the same Wi-Fi network, and reboot the phone once. If the stall persists across two retries, the manual APK is the next route. The patch and the APK are not mutually exclusive; the install picks the higher version and applies the delta from there.
For the related read on the manual install path and the SHA-256 checksum that catches a corrupted file, see the APK download page. For the wider sweep of trust signals that matter on the install, see the safety checklist.
Updates and version pinning
Store installs auto-update on the schedule you set. Manual APK installs do not · you re-download the new build from the operator's page when you want to move. Pinning a version is fine for a week; pinning it for a season is rarely worth the support gap.
Move the wallet, not the app
The wallet is on the operator's server. KYC and withdrawals follow the PAN, not the phone. Reinstalling the app on a new device is a one-tap process once the KYC is set.