Install, allow, sign in: the three stages on Android

Grant the two permissions Android asks for

Who the Come app is for, and who it is not

The install path, end to end

The Android install flow below was reviewed against the materials in the staged profile on 2026-08-25. Every step assumes a stock Android phone running a recent release with notifications enabled, at least 200 MB of free storage and a stable mobile or Wi-Fi connection. The flow does not require a desktop browser, a QR scan from a third-party site or a referral code from a Telegram channel. The single verified install route is the one linked from the Install Come app button on every page of this product profile.

The two steps that catch out new users most often are the "Install from unknown source" prompt and the first sign-in. The unknown-source prompt appears because the Come APK is distributed directly from the destination operator's CDN, not from the Play Store. The destination operator handles this by routing the install through a verified HTTPS endpoint that the Android package installer trusts once you approve the source for the duration of the install. The first sign-in step then asks for a phone number, a one-time code and a display name. None of those three pieces are optional, and the destination operator does not allow sign-in through a third-party identity provider.

What the APK actually contains

The package you download from the verified route is a single Android APK that bundles the four product surfaces - fantasy, rummy, sports, and games - behind one sign-in. The bundle approach is why the install size is bigger than a single-game app and why the permission list on first launch is short: the surfaces share a runtime rather than each shipping their own engine. Storage and notifications are the two system permissions the install asks for; nothing else is requested during install. Camera, contacts, and location are not in the install-time manifest.

The package signature is what Android uses to decide whether a future update is allowed to overwrite the installed app. Because the verified route always points at the same operator-hosted CDN, the signature stays consistent across updates and you do not see the "install failed because the package appears to be from a different source" error. That error is what happens when a user accidentally tries to install a copy of the APK from a third-party mirror; the publisher does not publish mirrors, so the only way to hit that error is to bypass this product profile.

The four install errors worth recognising

Four install-time errors cover most of what goes wrong on a fresh Android device. First, "App not installed" usually means a previous copy of the package is on the device from a different source - uninstall it through Settings then re-install from the verified route. Second, "Parse error" means the download was interrupted; redownload the file rather than retrying the install. Third, "Install blocked" means the "Install unknown apps" toggle for the source browser is off; toggle it on, install, then toggle it back off. Fourth, "Signature mismatch" means you tried to update an APK that came from a mirror; the publisher does not publish mirrors, so this error is the result of bypassing the verified route.

If none of the four patterns match what you see, capture the exact error string and the Android version on the support form on /contact/. The publisher desk cannot debug your device remotely but can usually tell you whether the error is one of the four above or something else - and, if it is something else, route the question to the in-app support surface where the operator can see your account state.