Getting your app built is only half the battle. For personal Google Play developer accounts, Google requires you to apply for production access — and a surprising number of indie developers get declined on the first try.
Here is why, and how to avoid it.
1. The 12-tester count was not actually held
The requirement is 12 testers opted in continuously for 14 days. The most common failure: the count dipped below 12 at some point. A friend uninstalled the app on day 9. Someone's phone broke. You were at 11 for two days and did not notice.
Play Console shows your tester count. Check it daily. Aim for 15 to 20 testers, or use a service that replaces dropouts so the count never falls.
2. Testers installed but never used the app
Google's production access form asks what you learned from testing. If your testers installed the app and never opened it, you have nothing to say — and Google can see engagement data.
Give every tester a simple task list: open the app daily, complete the main user flow, and send you one short note per week. Real usage is the whole point.
3. No feedback, no fixes, no evidence
The form asks about tester feedback and what changed because of it. "Nobody reported any bugs" is a weak answer when you had zero engagement. Keep a simple log: screenshots, daily check-ins, and at least one bug or improvement you shipped during the test. That log is your answer.
4. Applying on day 14 with testers who joined on day 10
The 14 days are counted backwards from the moment you apply, per tester. Testers who joined late in the window have not been opted in for 14 days. Either wait until every tester in your count has completed 14 days, or apply only once the full group qualifies.
5. Treating the requirement as a checkbox
Developers who treat the 14 days as dead time to be endured get declined. Developers who actually test — real users, real feedback, real fixes — pass. Google's review is not just counting days; it is checking that testing happened.
If finding testers is the hard part
Recruiting 12 to 20 reliable testers as a solo developer is genuinely hard. That is why services like VerifiedTesters — 12 real testers for 14 days exist: testers on their own Android phones, a dashboard to follow every day, free replacement for dropouts, and a final report you can use for the production access form.
Pass the review the first time. Run a real test, keep the evidence, and keep the count above 12.
Top comments (0)