App specifications
Engineered for low-bandwidth, mid-range Android. We publish the spec sheet so readers can audit the build before downloading.
| Spec | Android | iOS |
|---|---|---|
| APK size | 22.4MB | Mobile-web fallback |
| Min OS | Android 8.0 (API 26) | iOS 14+ |
| Languages | English + 9 Indic | English + 9 Indic |
| Permissions | SMS read (OTP), Camera (KYC), Location (geo-restrict) | Location (geo-restrict) |
| Push notifications | Firebase Cloud Messaging | Web Push API |
| Offline cache | Last 4 lab reports | Browser cache + service worker |
| Storage required | 60MB after 6 months | Browser cache + service worker |
The APK is small by design — we use ProGuard to strip unused Kotlin/Java code paths, R8 to compress resources, and bundle only the fonts and icons used on the first three screens. The remaining fonts and icons are downloaded on first launch of the relevant screen. A typical reader's first-week APK+data footprint is 48MB — well under WhatsApp's footprint, despite carrying live scores and lab reports.
Feature parity matrix
Every Android feature has an iOS counterpart. The lab documents the parity matrix so readers know what to expect.
| Feature | Android | iOS mobile-web |
|---|---|---|
| Lab reports | Full text + charts | Full text + charts |
| Live scores | Ball-by-ball push | 10-second polling |
| Squad builder | Native UI | Web responsive UI |
| Contest entry | Native UI | Web responsive UI |
| Withdrawal | UPI/bank intent | UPI/bank redirect |
| KYC | Camera + gallery | Gallery only |
| Push notifications | FCM (full) | Web Push (limited iOS) |
| Dark mode | Native | Native |
Offline behaviour
Every screen has a text-only fallback when offline. We design for cricket fans with patchy 4G — about 18% of our reader base is on Jio low-bandwidth or BSNL 3G tier.
Lab reports
Last 4 reports cached on device. Older reports show as 'tap to refresh'. The text is fully readable offline; charts render only on first online load.
Live scores
Last match state cached at app close. On reconnect, the scoreboard refreshes in under 4 seconds and contest points recalc against the cached state.
Contest entry
Squad-builder offline → write to queue → submit on reconnect. We never lock a squad offline because the lock-time data is server-authoritative.
Withdrawals
Offline withdrawal requests are queued and rejected with a 'no connection' message. We don't queue money-movement requests offline because the audit trail matters.
App vs mobile-web
iOS users get mobile-web, not a wrapped app. The feature parity is 95% — the 5% gap is by design, not neglect.
iOS App Store policies make skill-based fantasy apps a special-case review category that can take 4-6 weeks. We chose mobile-web as the iOS surface for two reasons. First, the lock-in reduction — readers can switch devices without losing app state. Second, the cost — App Store fees are 15-30%, which we'd have to recoup from contests. Mobile-web preserves contest economics while delivering 95% of the feature set to iOS readers.
The 5% iOS gap is intentional: push notifications are limited to 'match starting' and 'your contest closed' events on iOS due to Web Push restrictions. We mitigate by sending the same alerts via SMS for opted-in readers. The full lab-report notification cadence is Android-only, but the lab publishes a weekly email digest for iOS readers at no charge.
Frequently asked questions
Common questions our research desk fields about this page.On app test, common questions our research desk fields about this page.
Does the app drain battery?
The PlayExch app is engineered for low-battery operation. Live scores use Firebase Messaging push, not polling — background sync runs every 15 minutes when the app is closed, not every second. Average battery impact during a 4-hour match is 2-3% on a 4,000mAh battery, comparable to a news app in push-only mode. We publish this data so readers can audit our engineering choices.
Why no iOS native app?
App Store policies treat skill-based fantasy apps as a high-friction review category. A 4-6 week review window delays every feature release. Mobile-web gives us same-day releases across Android and iOS. The 95% feature parity is documented above; the 5% gap (push notifications) is mitigated by SMS alerts for opted-in readers.
Can I use the app on multiple devices?
Yes — one account, multiple devices, all with full feature access. There is no concurrent-session limit. We log every login across every device so you can audit the activity from the Security tab. If a device is lost, customer-care can sign out all sessions within 30 minutes; you re-OTP on the new device as normal.
How the lab's mobile stack is built
The PlayExch mobile app is engineered for low-bandwidth Indian networks. The lab publishes the architecture overview for power users who want to understand the design choices.
Offline-first data layer
The app ships with an offline-first data layer. The captain-pick dashboard, the lab-report library, and the wallet screen all work without a network connection. The offline cache auto-syncs when the network returns. The cache is encrypted with the user's session key — no plaintext data is stored on the device.
WebSocket live-match sync
The live-match sync uses a WebSocket connection that maintains a persistent link to the lab's scoring engine. The connection auto-reconnects on network drops. The sync engine applies client-side prediction to fill in any gaps during reconnection — the user sees a continuous stream even when the network is patchy.
Progressive Web App fallback
The iOS fallback is a Progressive Web App built with the lab's mobile-first design system. The fallback installs to the home screen with a single tap and supports push notifications, offline reading, and live-match sync. The fallback is the lab's recommended install path for iOS users.
Update channel
App updates ship through the lab's own update channel — not through Google Play. The update channel respects the user's preferences: critical security updates are non-deferrable, feature updates are deferrable for up to fourteen days. The lab publishes release notes in the in-app notice board seven days before each rollout.
The lab's extended perspective
A longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.For the app test desk, a longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.
Methodology in depth
The lab's methodology is built on a five-stage pipeline. Every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. The pipeline is published in full on the methodology page. The lab's edge comes from data freshness and analyst expertise, not from a secret formula. Other analysts can re-run the experiments with the published datasets and the published model code. The lab publishes every dataset version and every model version. The lab never quietly updates a dataset after the conclusion lands.For the app test desk, the lab's methodology is built on a five-stage pipeline. Within the PlayExch framework, every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. Reports readers should note that the pipeline is published in full on the methodology page. The lab's edge comes from data freshness and analyst expertise, not from a secret formula This is why the app test desk treats it as a baseline. Other analysts can re-run the experiments with the published datasets and the published model code. On app test, the lab publishes every dataset version and every model version. For the app test desk, the lab never quietly updates a dataset after the conclusion lands.
Data sources in depth
The lab pulls data from four primary sources. Match data comes from official tournament data partners, cross-checked against broadcast records. Ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Contest result archives come from publicly published leaderboards. Self-collected squad logs come from volunteer readers who submit their picks at lock time. Each source has a published quality score and a published latency benchmark. The lab's data-quality framework is reviewed quarterly by the statistics team.For the app test desk, the lab pulls data from four primary sources. Within the PlayExch framework, match data comes from official tournament data partners, cross-checked against broadcast records. Reports readers should note that ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Contest result archives come from publicly published leaderboards This is why the app test desk treats it as a baseline. Self-collected squad logs come from volunteer readers who submit their picks at lock time. On app test, each source has a published quality score and a published latency benchmark. For the app test desk, the lab's data-quality framework is reviewed quarterly by the statistics team.
Reader-safety commitments
The lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. The lab publishes the safety commitments on the responsible-play page. The lab refuses to partner with operators that do not enforce responsible-play defaults. The lab's reader-safety framework is reviewed annually by an external auditor.For the app test desk, the lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. Within the PlayExch framework, the lab publishes the safety commitments on the responsible-play page. Reports readers should note that the lab refuses to partner with operators that do not enforce responsible-play defaults. The lab's reader-safety framework is reviewed annually by an external auditor This is why the app test desk treats it as a baseline.
Editorial principles
The lab operates by five public editorial principles. No sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Methodology is public — every model's code is published on the methodology page. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. Responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.For the app test desk, the lab operates by five public editorial principles. Within the PlayExch framework, no sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Reports readers should note that methodology is public — every model's code is published on the methodology page. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits This is why the app test desk treats it as a baseline. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. On app test, responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.
Quarterly transparency
Every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. The report is published on the 15th of the month following quarter end. The most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. The report is available on the disclosure page.For the app test desk, every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. Within the PlayExch framework, the report is published on the 15th of the month following quarter end. Reports readers should note that the most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. The report is available on the disclosure page This is why the app test desk treats it as a baseline.
