Free resource — no fake testers
Google Play closed testing checklist for indie Android teams.
Use this before you ask strangers to test your app. It turns the 12+ testers / 14-day grind into an evidence plan you can actually run, especially for Expo and React Native apps.
1. Readiness before Day 1
- Production access goal and target release date are written down.
- Closed testing track is configured with the exact package name you will ship.
- Tester onboarding message explains the app purpose, required actions, and how to report bugs.
- Privacy/support pages are live and match the app store listing.
- Crash-prone or login-blocking flows have been smoke-tested on at least one real Android device.
2. Tester roster and 14-day tracking
- Invite more than the bare minimum so inactive testers do not kill the run.
- Track tester ID, country/time zone, device, join date, last active date, and feedback status.
- Check activity daily; re-engage inactive testers before the window goes stale.
- Keep screenshots or console exports showing tester availability and activity trend.
- Do not buy fake installs, promise rewards for fake behavior, or ask for account passwords.
3. Evidence pack for production access
- Store daily activity notes and tester feedback in one sheet, not scattered DMs.
- Capture at least five meaningful app-flow screenshots from testers or test devices.
- Summarize bugs fixed during the closed test with dates and release versions.
- Prepare honest production access answers: who tested, what changed, and what evidence proves it.
- Export a ZIP with screenshots, feedback CSV, issue log, and a manifest before applying.
Beta intake
Turn the checklist into a concrete launch plan.
No approval guarantee. No Google Play Console custody. No fake testers.