Wecap fantasy app — captain pick desk in your pocket
The Wecap app pairs the editorial captain pick desk with a clean contest engine. KYC, deposit, contest entry and withdrawal all live inside the same flow you use on matchday.
What the Wecap app does on matchday
Five working surfaces, one identity. The app is built around the same five-step matchday flow the editorial desk uses.
Read the daily C/VC matrix, see venue form, and lock the multiplier picks before toss. Mirror of the editorial column on the homepage.
Track your credits in real time. Drop a player, the ledger reruns, the cap stays at 100.
Enter mega contests, head-to-heads and practice matches with one tap. The contest window opens with the toss.
UPI deposits, UPI withdrawals once KYC clears. Withdrawal history is searchable by contest ID.
Toss, playing XI, last-minute changes, and result windows. Alerts are scoped to your contest type.
Reach the matchday desk from inside the app. Priority routing through toss and team-sheet release.
What the app accesses, and why
The Wecap app requests only the permissions it needs. Nothing more, nothing by default.
| Permission | Why it's needed | Opt-out |
|---|---|---|
| Camera | KYC document scan and QR scan for app install | Yes — required for KYC, optional for QR |
| Notifications | Matchday alerts: toss, playing XI, result windows | Yes — scoped to your contest type |
| Biometric | Login replacement after device binding | Yes — toggle in wallet menu |
| Storage | Cached contest data for slow networks | Yes — clearable from settings |
| Location | State-eligibility gate for paid contests | Yes — without location, contests are blocked per state law |
How the Wecap app ships
The Wecap app ships monthly during the cricket calendar with critical security patches out-of-cycle. The release cadence is documented on the changelog endpoint.
| Surface | Cadence | Lead time |
|---|---|---|
| Monthly release | First Tuesday of each month | Release notes published on the day |
| Security patch | As required | Out-of-cycle, 24–72 hour window |
| Critical fix | Same-day for live issues | Hotfix released once verified |
| End-of-support | 90 days after build | Notification in-app 14 days before |
What the app does without internet
Wecap supports a degraded offline mode for read-only surfaces. Live contests require a connection; cached contest data is refreshed on reconnect.
Read-only surfaces
- Captain pick desk (last cached version)
- Salary cap playbook (last cached version)
- Points matrix (last cached version)
- Account history (last cached version)
Connection-required surfaces
- Live contest entry
- Withdrawal requests
- Deposit requests
- Customer care chat
Reader questions about the Wecap app
Reader questions sent to the desk in the last quarter, answered in editorial voice. Send yours via /contact/.
Does the Wecap app support dark mode?
No. Wecap ships with the Slate Utility light palette as the default. Dark mode is not in the roadmap because the editorial voice depends on the light-surface / dark-ink contrast for legibility.
Can I install the Wecap app on a tablet?
Yes. The Android app runs on tablets with Android 8.0 and above. The iOS app runs on iPad with iPadOS 14 and above. The layout adapts to tablet dimensions.
What languages does the Wecap app support?
English is the only supported language in the current build. Hindi is in the roadmap; readers who want a Hindi edition can request it via the contact form.
Can I use the Wecap app on multiple devices?
Yes. Wecap supports up to five bound devices per account. Each device is bound with OTP confirmation; the bound-device list is visible in the wallet menu.
Does the Wecap app work on a Chromebook?
Yes, via the Android app on ChromeOS 96 and above. The web desk is the recommended surface on ChromeOS.
How the app performs under matchday load
Matchday load is the highest-traffic window for fantasy apps. Wecap is built for it. The performance targets are documented below.
The app preloads the LCP image and defers non-critical CSS. The LCP target on a stable 4G connection is under 1.5 seconds.
The app uses explicit width/height on every image and reserves space for dynamic content. Layout shift stays under 0.05 in typical use.
The app defers non-critical JS, inlines critical CSS, and lazy-loads below-the-fold images. Blocking time stays under 200ms in typical use.
What the first install looks like
The first install of the Wecap app runs through five steps before the play desk is reachable. Most users complete all five in under a minute on a stable connection.
- 1Welcome carousel
Three screens introducing the captain pick desk, the salary cap playbook and the verified winners ledger. Skip from any screen.
- 2Mobile number entry
The same identity as the web desk. Foreign numbers are gated until KYC review is complete.
- 3OTP verification
SMS OTP plus in-app push. Validity five minutes. Biometric upgrade is offered after a successful OTP.
- 4Device binding
The first device is bound with one tap. Subsequent logins on the same device skip the binding prompt.
- 5Welcome code
If you have an active welcome code, the app prompts you to apply it before you reach the wallet menu. See /bonus-code/ for the current campaign.
Bridge the web desk and the mobile app
Wecap runs a desktop bridge: when you scan a QR code on the web desk with your phone, the deep link opens the app at the same screen. The bridge is one tap from any web desk screen.
Open the app from the web desk
The web desk shows a QR code in the bottom-right corner. Scan it with your phone's camera; the deep link opens the app at the same screen.
Open the web desk from the app
The app's wallet menu has an "Open in browser" option for contest screens. The web desk opens at the same URL.
How the app is tested before each release
The Wecap app ships monthly with critical security patches out-of-cycle. The release process is documented below.
- 1Unit tests
Every commit runs the unit test suite. Coverage targets are above 80% for the contest engine and KYC modules.
- 2Integration tests
Integration tests run against the staging environment. The KYC partner and payment aggregator are mocked; the contest engine runs against staging data.
- 3UI tests
UI tests run on a device matrix covering the most common Android devices and iOS versions. Failures block the release.
- 4Performance tests
Performance tests measure LCP, CLS and TBT against the published targets. Regressions block the release.
- 5Security review
Security review runs against the OWASP Mobile Application Security Verification checklist. Findings block the release.
Matchday desk features, in depth
The matchday desk is the most-used surface in the Wecap app. Three features make the desk work.
- 1Format rail
The format rail lets you switch between T20, ODI, Test and T10. The matrix updates with the format selection.
- 2Captain pick matrix
The matrix is interactive: tap a player to see the column breakdown. The captain and VC badges update with the selection.
- 3Salary cap ledger
The ledger updates live as you build your XI. The cap stays at 100; the ledger shows the spent and spare amounts.
What to do in your first week
The first week on the Wecap app is about building familiarity. Three actions matter most.
- 1Read the captain pick desk
Open the captain pick desk daily. Skim the matrix, the C/VC picks and the differentials. Even without entering contests, the desk builds familiarity with how the matrix reads.
- 2Build a practice XI
Build a practice XI for the next matchday. The contest is free; the mechanics are identical to paid contests.
- 3Run KYC
Run KYC during the first week. KYC takes up to two hours during business hours; running it early means you can enter paid contests from day one.