How it works
Google's rule, stated plainly: a personal developer account created on or after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 continuous days before it can apply for production access. If the count drops below 12, the clock resets. Google also checks that testers used the app.
For developers
- Sign in with Google and add your app: name, package name, closed-testing opt-in link, and what testers should try.
- Buy a job: 15 testers for $19. Nothing is visible to testers until payment is confirmed by the payment provider.
- Testers accept, opt in on Play, and upload proof. We verify each proof by hand against the count in your Play Console.
- When 12 are verified, the 14-day clock starts. You see check-ins and feedback as they arrive.
- Ship at least one update during the window. Google treats a test with no update as suspicious.
- On day 14 you receive a draft of the ten production-access answers built from real feedback. Edit, paste, apply.
If testers drop out
Three spare testers are included. If completions still fall under 12 at day 14, the job extends by up to 7 days and replacements are pulled in at no charge. If it still fails, you are refunded in full.
For testers
- Sign in with the Google account you use on your Android phone. One account, one device.
- Pick a job, opt in through the link, install from Play, upload a screenshot showing the beta badge.
- Check in on days 1, 4, 8 and 12 with a screenshot from inside the app and one line about what you did.
- File at least two pieces of feedback, the first by day 7.
- Complete all of it and the payout is recorded. You are paid by UPI in India or PayPal elsewhere.
What Google sees
Only what happens in Play: opt-ins, installs and engagement from real accounts on real devices. App Testers never touches your Play Console. We record the evidence so your answers to Google are specific and true.