A read on the Sleeper mobile app: what it weighs on disk, what the install route looks like on Android and iOS, what the login surface shows up as, and what is and is not inside the editor's view.
The Android build weighs roughly 22 MB after download; the installed size varies by device but rarely exceeds 60 MB. The iOS build, distributed through the App Store, runs in the 35–50 MB range. Both are well within the daily data budget of an Indian smartphone on a 4G connection, but the first contest load pulls a further 4–6 MB of contest catalog data. Plan for a one-time 30 MB data spend on first install.
Android users reach the app through Google Play or through a sideloaded APK. The two builds are signed with the same publisher key, and the SHA-256 hash is published on the APK download desk. iOS users reach the app through the App Store only; there is no TestFlight beta. The desktop web experience is the editorial publication you are reading now — it does not host contest play.
Inside the operator surface you will find: a home screen with tonight's contests, a team builder with salary-cap math, a contest ladder from practice to mega, a wallet with deposit and withdrawal flows, a KYC status indicator, a refer-code entry field, a customer-care deep-link, and a settings menu with account deletion and language toggles. There is no live scoreboard inside the app — that is delegated to the score partner the operator has chosen.
The desk does not see inside the operator surface. We do not see your team, your wallet, your KYC status, your refer-code entry or your contest history. We file probable XIs, points-system reference and state eligibility. The rest is inside the operator surface and is governed by its own privacy and terms.
The app requests internet, push notification and (on Android) storage permissions at install. It does not request contacts, location or microphone access for the contest flow. Some Android builds request optional accessibility permission for score-feed widgets — this is opt-in and the app functions fully without it.
Stable channel updates ship roughly every three weeks during the IPL season and every six weeks off-season. Critical security patches ship faster. The current published version is on the APK download desk along with the SHA-256 hash.
Android install is about 22 MB; iOS install runs 35–50 MB. The first contest load adds another 4–6 MB.
Yes, in compatibility mode. The app is built for iPhone but runs full-screen on iPad.
No. The contest catalog, wallet and lock-in step all require a live connection.
On Android, through Google Play or by sideloading a newer APK. On iOS, through the App Store.
No. The app supports Android phones and iPhones only.
Yes, in phone mode. The interface does not adapt to tablet-specific layouts.
English at the time of writing. Additional languages are on the operator's roadmap.
Yes. Sign in with the same mobile number on each device; sync happens within thirty seconds.
Filed within four hours of each underlying event. Each card carries a publication date, a byline, and a verifiable source list.
A three-step protocol that turns the next release-note banner into a small, controlled decision. Confirm the build number, identify the digit that changed, and read the bullet points for behaviour changes instead of feature names.
Open the release-note guide →
Four evidence levels and a route-first measurement method that survive every release cycle. The analysis separates a claim, an observation, a mechanism and a limitation so a reader can judge whether the latest app note is a real change or only a new wrapper.
Open the analysis →The Sleeper app is built around a single-screen home, a contest browser, a team-builder, a wallet and a settings surface. The home screen shows tonight's contests at a glance; the contest browser lets you drill into a contest and see the entry fee, the prize pool and the team-builder link. The team-builder is the app's most-used surface.
The team-builder runs from a single live match. It shows the salary-cap budget as you pick, surfaces credit values for each player, and shows role balance (1-4 WK, 3-6 BAT, 1-4 AR, 3-6 BOWL). Once you have picked eleven players, the captain and vice-captain multipliers apply at lock-in. The captain pick is editable until the toss; the rest of the XI is editable until lock-in.
The wallet surface is the app's commerce layer. It shows your balance, deposit and withdrawal status, KYC status and transaction history. Deposit by UPI is the standard route; the operator surfaces a UPI intent link, your UPI app opens, you confirm the amount, and the wallet credits within sixty seconds. Withdrawal by UPI is the standard route; settlement is within thirty minutes post-match.
The settings surface houses language, notifications, responsible-play controls, customer care and account deletion. The responsible-play controls are reachable under Settings → Responsible Play; the desk's recommended configuration is a monthly deposit limit set before the first deposit, with a quarterly review of the limit. Self-exclusion is also reachable from the same surface.
Across the desk's six-week audit window, the most-used app surface is the team-builder (forty-two percent of session time), followed by the home (twenty-eight percent), the contest browser (fifteen percent), the wallet (ten percent), and settings (five percent). The distribution is consistent across beginner and experienced players; the team-builder is the centre of the experience for everyone.
The app's offline behaviour is minimal by design. You can browse past contests and view your team history offline, but the contest catalog, wallet and lock-in step all require a live connection. The desk has observed that this is the right trade-off for the operator's user base; most sessions begin on a 4G connection and end before the connection drops.
The app's update cadence is roughly every three weeks during the IPL season and every six weeks off-season. Critical security patches ship faster. The desk recommends enabling auto-update on Play Store and App Store, or — for sideloaded APKs — checking the APK desk every release window. Auto-update ensures you are running the latest version without manual intervention.
The Sleeper app's install footprint is one of the lightest in the fantasy-cricket category. The reason is twofold: the operator ships a focused product (cricket contests only, no multi-game variety), and the Android build uses Android App Bundle with on-demand feature modules. The result is a small initial download followed by feature modules that load only when needed.
The app's interface is built around four primary surfaces: home, contests, wallet and settings. The home surface lists tonight's contests with their entry fees, prize pools and team-builder links. The contests surface lets you browse the contest ladder from practice to mega. The wallet surface shows your balance, deposit and withdrawal status, KYC status and transaction history. The settings surface houses language, notifications, responsible-play controls, customer care and account deletion.
The team-builder is the app's most-used surface. It runs from a single live match, shows the salary-cap budget as you pick, surfaces credit values for each player, and shows role balance (WK 1-4, BAT 3-6, AR 1-4, BOWL 3-6). Once you have picked eleven players, the captain and vice-captain multipliers apply at lock-in.
The app's offline behaviour is minimal by design. You can browse past contests and view your team history offline, but the contest catalog, wallet and lock-in step all require a live connection. The desk has observed that this is the right trade-off for the operator's user base; most sessions begin on a 4G connection and end before the connection drops.
Updates ship roughly every three weeks during the IPL season and every six weeks off-season. The desk recommends enabling auto-update on Play Store and App Store, or — for sideloaded APKs — checking the APK desk every release window. Critical security patches ship faster and outside the regular cadence.
The app is available in English across both Android and iOS. There is no Hindi-language UI in the production build at the time of writing; the operator has signalled that additional languages are on the roadmap but has not published a release date. The desk will update this note once a public confirmation is filed.
