Frequently Asked Questions
Straight answers about closed testing, our tester team, packages, and the production-access process.
Closed Testing Basics
Closed testing is a Google Play release track where a limited, invited group of testers installs and uses your app before it goes public. For many newer personal developer accounts, Google requires a closed test with a minimum number of testers over a continuous period before you can apply for production access. It is Google's way of confirming that a real app has been genuinely tested by real people.
The requirement depends on your Play Console account and the policies in effect when you created it. Many personal accounts are asked to run a closed test with at least 12 testers opted in for 14 consecutive days, but Google has adjusted this requirement over time. Always confirm the exact number shown in your own Play Console dashboard — our Standard and Premium packages both provide 12 or more testers to cover the common requirement with a safety margin.
All testing happens on real physical devices running Android 10 or newer, across a mix of manufacturers and screen sizes. We do not use emulators.
Yes. Google alone reviews and decides production-access applications. What we provide is a complete, genuine closed test — real testers, real devices, continuous daily activity — plus guidance through the application, so the testing requirement is properly and verifiably satisfied. No third-party service can guarantee Google's final decision, and you should be cautious of anyone who claims otherwise.
Yes, and they have. Google has adjusted closed-testing requirements since introducing them, and the exact tester count or duration can differ between accounts and programs. Treat any article — including ours — as orientation rather than authority, and always confirm the requirement shown in your own Play Console dashboard. If yours differs from the common case, send us a screenshot and we will size the testing round to match it.
The Testing Process
A standard round runs 14 consecutive days, matching the continuous-testing period Google commonly requires. Setup (adding tester emails, publishing the closed-testing release, and having testers opt in) usually takes less than a day once your testing link is ready. Premium orders can include extra testing days when your situation needs them.
Yes. Our testers opt in through your official closed-testing link and stay opted in for the entire testing period. We monitor participation daily, and if any tester drops out we replace them promptly so your tester count does not fall below what your requirement needs.
They do. Testers install your app on real physical Android devices, open it regularly, navigate through its screens, and use its core features throughout the testing period. This is genuine daily activity — not simulated installs or emulator sessions.
Once your required continuous-testing window is complete, Google Play Console lets you apply for production access. We help you verify that the testing requirement is fully satisfied before you apply, and we guide you through the application questions so your answers accurately reflect the testing that was done.
Yes. Premium includes closed-testing setup assistance: creating the closed-testing track, uploading tester lists, configuring countries, and publishing the testing release. If you have never used Play Console before, we can walk you through every step over chat or a screen-share session.
Standard includes 8–12 honest feedback reports and Premium includes 12–15. Feedback covers usability, navigation, crashes or errors encountered, and first-impression notes from testers — practical input you can act on before your public launch.
We monitor opt-in status daily. If a tester drops out, we add a replacement immediately so your continuous-testing count is protected. This monitoring is part of every package.
Yes. Before you apply, we verify that your Play Console shows the testing requirement as satisfied, and we help you prepare accurate, specific answers to Google's questions about how testers were recruited, what testing was done, and what feedback you acted on. Because your round used real testers with genuine daily activity, those answers match what Google can observe.
App Compatibility
Yes. Our Standard and Premium packages cover apps with custom sign-up flows and user accounts. Testers register real accounts inside your app and use it as a normal user would.
Yes. Apps that use Google Sign-In are supported in every package, including Basic. Testers sign in with real Google accounts on their own devices.
Choose Premium. It covers apps that need full profile creation — onboarding questionnaires, profile photos, preference setup and similar multi-step flows. Testers complete the full setup so your app is tested the way real users experience it.
Packages & Pricing
If your account requirement allows a smaller tester group or you simply want a QA round, Basic works well. If your Play Console asks for 12+ testers, choose Standard or Premium. If your app needs sign-up with full profile setup, or you want setup assistance and priority support end to end, Premium is the most complete option.
Still have a question?
Every app is a little different. Tell us about yours and we'll give you a straight answer — no obligation.
Ask Us Directly