App install

The first install on Android takes about seven minutes; the iOS route sits inside the App Store.

Beginners who follow the seven-step Android path land on the KYC screen in roughly seven minutes. The iOS path is a single App Store tap. Both end at the same login screen. Both share the verified first-party route /Login/playnow.

Editorial composition of an Android smartphone standing against a brass lamp on a sage felt desk pad showing an app install progress bar in ruby and ivory
Eight numbered steps

The first install path, beginning to first deposit

The eight steps below cover the install from the first tap to the first deposit. Steps 1 to 4 cover Android; step 5 covers iOS; steps 6 to 8 cover the post-install flow that runs on both platforms.

  1. Step 1, download source. Open the verified first-party path /Login/playnow from the device browser. Do not use third-party mirrors.
  2. Step 2, verify publisher. Confirm the publisher string on the download page matches the editorial product label. The first-party mirror carries the editorial brand string.
  3. Step 3, allow source. Toggle Install unknown apps for the browser used to fetch the APK. Toggle is per-app; revisit after browser updates.
  4. Step 4, install. Tap the APK file and accept the install prompt. The package is signed by the first-party publisher.
  5. Step 5, iOS path. Tap the App Store badge on the landing screen. The iOS install completes in one tap; no sideload toggle.
  6. Step 6, launch and sign in. Open the app and sign in with the registered mobile number. OTP verification runs on first launch.
  7. Step 7, KYC. Upload the document set listed on /wallet-kyc/. The KYC gate sits before the first withdrawal, not before the first deposit.
  8. Step 8, first deposit. Pick UPI or net banking and complete the first top-up. The deposit rail is shared across fantasy, casino and rummy lanes.
Android specifics

Play Protect toggle and the storage footprint

Two Android-specific points come up on a first install: the Play Protect prompt and the storage footprint. Both deserve a paragraph of their own.

Play Protect toggle

Play Protect scans every APK install. On a first-party APK, the scan completes in seconds and the install proceeds. If the scan is blocked, the toggle sits under Settings → Apps → Special access → Install unknown apps, scoped to the browser used to fetch the file.

Storage footprint

The captured install footprint sits between 60 and 90 MB. Once fantasy contests start caching scorecards, the cache grows to roughly 200 MB. Clearing the cache does not log you out; clearing data does.

iOS specifics

One tap inside the App Store

iOS users land in the App Store via a single tap. There is no sideload toggle and no APK file to fetch. The verification on iOS is the publisher string inside the App Store listing; the editorial product reads that string on the install page.

  • iOS minimum version is published in the App Store listing.
  • Push notifications require explicit opt-in; the default is off.
  • Face ID for login is optional; the OTP fallback always works.
First-launch KYC

What the KYC screen actually asks for

KYC runs on first withdrawal, not first deposit. The deposit rail accepts UPI and net banking before verification. The KYC screen asks for the document set listed on /wallet-kyc/. Rejections are visible in the wallet within minutes.

Identity document

Aadhaar, PAN or passport. The capture publishes three accepted forms; the in-app picker limits you to one.

Address proof

Aadhaar, utility bill or bank statement. The address line on the document must match the registered address.

Selfie

Front-facing camera capture. Lighting matters: a flat desk lamp gives the cleanest read.

Permissions

What the app asks for, and what it does not

The captured permission list is narrow. Camera is for KYC. Storage is for app updates and offline scorecard caching. Network is for live scorecard sync. The list deliberately omits background location, contact list and SMS read.

PermissionPurposeRequired for
CameraKYC document uploadFirst withdrawal
StorageApp updates and offline cacheFirst launch
NetworkLive scorecard syncAlways
NotificationsContest lock and scorecard changesOptional
Troubleshooting

Five things that go wrong on a first install

Most first-install failures fall into five buckets. The list below matches what the support queue sees most often.

  1. Install blocked by Play Protect: toggle Install unknown apps for the browser.
  2. OTP not received: confirm the mobile number prefix matches the registered number; SMS delays are common at night.
  3. KYC rejected for mismatch: re-check the address line against the registered address.
  4. App stuck on splash: clear cache from Settings → Apps; the login session survives.
  5. Deposit fails on UPI: confirm the UPI ID is the same one used at registration; mismatched UPI handles are the most common cause.
Sideload risk note

First-party APK versus third-party mirror

The APK that ships from the verified first-party path is signed and timestamped. A third-party mirror can look identical and carry a different signature. The signature check is the reason the install guide routes through /Login/playnow and not through a search result.

First-party APK

Signed by the editorial product publisher; carries the brand string; available only from /Login/playnow.

Third-party mirror

Unverified signature; possible repackage; possible injection. Install only if you can verify the SHA-256 against the publisher.

Internal links

Four routes to read after this one

The install guide is the first of four install-adjacent routes. The other three sit one click away.

FAQ

Six questions readers ask about the install

Is the APK first-party?

The download path is the verified first-party route /Login/playnow. Do not install APKs from third-party mirrors.

How large is the APK?

The captured install footprint sits between 60 and 90 MB. Storage footprint depends on device OS and asset cache.

Does the iOS app exist?

The 17 August 2026 capture lists the iOS App Store path as a separate install route. See the iOS step block further down.

What if KYC is rejected?

Re-upload the document set listed on /wallet-kyc/. If the second attempt is rejected, open the support route and attach a screenshot of the rejection notice.

What permissions does the app request?

Camera for KYC document upload, storage for app updates and network for live scorecard sync. No background location or contact-list access.

How do I uninstall?

Long-press the icon and choose Uninstall. The account stays open; reinstall any time using the same mobile number.

Next step

Two actions after the install

Once the install completes, run two actions before you join a contest: read the eight-step walkthrough and read the responsible play page. The walkthrough covers the post-install flow inside the app; the responsible play page covers the controls you can toggle from the wallet.