Question 1

What is Google Play's closed testing requirement?

Accepted Answer

Many Android developer accounts must run an active closed test with a minimum number of testers who opt in and use the app continuously for a set period before the app is eligible for production access. Google introduced this to reduce spam and low-quality app submissions. Requirements can vary by account type and may change, so always confirm the current requirement in your Play Console.

Question 2

How is your service different from just adding friends as testers?

Accepted Answer

You can absolutely use friends or colleagues if you have enough who'll genuinely install and use the app for the full window — that satisfies the requirement too. Our service exists for developers who don't have that many people readily available; we provide a coordinated panel of real testers instead.

Question 3

Are the testers real people?

Accepted Answer

Yes. Every tester in our panel uses their own Google account and their own device to opt in, install your app from the Play Store, and use it across the required window. We manage scheduling and coordination; the testing itself is genuine.

Question 4

What do I need to prepare before booking?

Accepted Answer

A working build uploaded to a closed testing track in Play Console, and the track's tester opt-in link. See the How It Works page for the full setup walkthrough.

Question 5

How do testers join my closed track?

Accepted Answer

You add closedtestersapp@googlegroups.com as a tester list (via Google Groups) in your Play Console closed testing track. Our panel members are members of that group, so adding it gives them access to opt in.

Question 6

How long does a full test cycle take?

Accepted Answer

Cycles run for the continuous period Google's current policy requires for your account type. Most cycles start within 1–2 business days of booking once your track and opt-in link are ready.

Question 7

Will my app definitely be approved for production afterward?

Accepted Answer

We confirm that the testing requirement itself has been met. Production approval is decided by Google and also depends on factors outside testing, like policy compliance, content rating, and app content — those are your responsibility, but we'll flag anything obvious we notice along the way.

Question 8

Can I get feedback from testers, not just completion?

Accepted Answer

Yes — every cycle includes a structured feedback summary covering install experience, crashes, and general usability notes from the panel.

Question 9

What happens if my app has a bug that blocks testers?

Accepted Answer

We'll flag it as soon as it's noticed so you can ship a fix. Depending on timing, we can resume the remaining days of the window once an updated build is live on the track.

Question 10

How do I pay, and when?

Accepted Answer

Payment is collected when you book your cycle. It's $20 per app, $50 for 3 apps, and $10 for each additional app after that.

Frequently asked questions