Real testers for your Google Play closed test.
Google requires new personal developer accounts to run a closed test with at least 12 testers for 14 continuous days. Our testers do not just install your app and leave it alone. They use it, test it for quality, and send you feedback you can use before launch or in your next dev sprint.
Start your closed testSee how it works
15 testers enrolled. 12 or more opted in and active for 14 days in a row.
What Google requires
If your Google Play developer account is a personal account created after 13 November 2023, each new app needs its own closed test before you can apply for production access. Google lowered the bar from 20 testers to 12 in December 2024. Organization accounts and older personal accounts are not subject to the requirement.
Testers must be separate Google accounts and stay opted in for the whole 14 days. A tester who installs your app and never opens it again gives you a box ticked, no feedback, and possibly a closed test that looks thin when Google reviews your application. Dropouts are the other common problem, because they can break the 14-day count.
Rules change. Check Google Play Console Help ("Testing requirements for new personal developer accounts") for the current wording before you start.
Testers who actually use your app
Real use, not idle installs
Testers open your app throughout the testing window, work through its features, and report what is confusing, broken or slow.
Real devices and people
They come from our vetted network and use their own phones, across different makes, Android versions and regions.
Active for all 14 days
We enroll 15 against Google's minimum of 12, so up to three testers can drop out and your 14-day window still holds.
Feedback you can use
Use the window to catch problems before launch, or to plan your next dev sprint while your closed test runs.
How it works
You set up the closed testing track
Create the track in Play Console and send us the opt-in link. We walk you through it if it is your first time.
We enroll testers
Our testers join from their own Google accounts and install the app. The 14-day clock starts once 12 are opted in.
Testers use and test your app
They check in daily and run testing sessions over the window. You can tell us what to focus on at any point, such as a new feature or a flow you are worried about, and we adjust.
You get a short report every three days
Brief updates on what testers found, so you can fix things or change direction while the test is running. A final report arrives on day 15.
You apply for production access
When the window is complete you answer Google's production questions, with your testing history and reports to draw on.
Closed Test with Real Testers
One app, one 14-day closed test
- 15 testers enrolled, above Google's minimum of 12
- 14 days of active use and quality testing, not idle installs
- A three-tester buffer above Google's minimum, with replacements added if anyone drops out
- A short report every three days, with adjustments to testing focus at your request
- A final report on day 15
- Tester NDAs included, or your own NDA language if you send it
Want a deeper evaluation before launch? See our evaluation tiers.
Questions
Why does this cost more than other closed testing services?
Many services supply accounts that opt in and open your app now and then. We pay real testers to use your app through the window and report what they find, with reports to you every three days. If you only need the requirement ticked, a cheaper service may be enough. If you want to use the 14 days to improve the app, that is what we do.
Do you guarantee Google will approve my app?
No. Google makes the production access decision and reviews your app on its own policies. We make sure the testing requirement is met properly with testers who actually use your app.
Do your testers sign NDAs?
Yes. Every tester in our network signs a non-disclosure agreement before they get access to a client's app. If you would rather use your own NDA, send us the language before the test starts and our testers will sign it instead.
Can I change what the testers focus on?
Yes. Send us requests at any time during the 14 days, for example to test a new feature or a particular flow, and we pass them on. If a request goes well beyond the package, such as testing a large new set of features, we will tell you before we act on it.
Do I need this for Apple's App Store?
No. Apple does not set a minimum tester count before you can submit. Your app goes through App Review, and TestFlight beta testing is optional. If you want real-world feedback on an iPhone build before submitting, we can run a TestFlight evaluation separately.
What do you need from me?
An app build on a closed testing track, the opt-in link, and a short note on what the app does and what you most want checked.
What if my account is an organization account?
Then the requirement does not apply to you. Verify your account type in Play Console before buying.
Ready to start your 14 days?
Tell us your app name, your target launch date and whether your account is personal or organization. We reply within one business day.