Get 12 real testers for 14 days

Google Play asks new personal developer accounts to run a closed test with at least 12 testers opted in for 14 continuous days before applying for production access (Play Console Help). Peerbeta gives you those testers: real people on real Android phones, most of them developers who publish apps too. You see what they do every day, you get structured feedback, and you finish with a report you can use in Google's application form.

This page explains exactly how it works, what it costs, and what we can't promise.

What Google actually checks

Before you pay anyone, know the rule:

• At least 12 testers opted in to your closed test when you apply.
• Each of them opted in continuously for the 14 days before you apply. A tester who leaves and comes back starts again from zero.
• A form with three parts: your closed test, your app, and your production readiness.

Google names two reasons it may ask you to keep testing: "fewer than 12 opted-in testers or insufficient tester engagement during the testing period" (Play Console Help). So the count matters, and so does real use of the app. Our whole setup is built around both.

The full rule is in our Google Play closed testing guide.

How it works

1. Set up your closed test. In Play Console, add the Peerbeta Google Group on your closed track's Testers tab ("Google Groups" option), publish the track, and copy the opt-in link. Our step-by-step setup guide has every screen.
2. Create your test on Peerbeta. Paste the opt-in link. We check that it is a real opt-in link (https://play.google.com/apps/testing/your.package, the format Google documents in Play Console Help) and that it matches your package name. List the 2 to 8 features you want tested, add test login details if your app needs them, and any special instructions.
3. Testers join. They join our Google Group once, open your link, opt in and install your app from Google Play. Our Android tester app confirms that your app is installed on their phone. If 2 of the first 3 testers can't find your app, we pause the test and send you a guided diagnosis instead of burning your days.
4. Day 1 starts when installations are verified. Not when testers are invited. On Express, day 1 starts once 15 testers have a verified installation; on Pro and Launch, once 20 do.
5. 14 days of daily use. Each day, testers open your app through the tester app and do one short task you care about ("add an item", "try the search"). They send structured feedback three times: first impressions on day 1, a feature check on day 7, a final review of the app on day 14. Bugs come with steps, severity, device and a screenshot.
6. You apply. Your dashboard shows the earliest date to apply. We recommend day 15, one day of margin.

What you see during the test

• Testers assigned, installed (verified), active today (verified), dropped.
• Day X of 14 and your earliest application date.
• Countries, device models and Android versions.
• Feedback by feature, as it arrives. Bugs with severity.
• Alerts when active testers fall too low or your link breaks.

You can announce an update ("v1.1 is out, please retest checkout"). Testers get notified and the update is recorded in your report. Shipping fixes during a closed test is something Google itself recommends.

What you get at the end

• A report (web, PDF, Markdown): who tested, on what devices, how many active days, which features got used, bugs found and fixed, updates you shipped, and a summary of feedback with quotes.
• Draft answers for the three parts of Google's production access form, built from your test's real numbers and feedback. Every draft is specific to your app. You edit them, then paste them into Play Console. Read how the production access form works before you apply.

Plans

Launch prices. Paid plans open as tester capacity allows: the order page shows the live start estimate before you pay. If we can't start your test on time, we tell you before you pay, not after.

Prefer to pay with time instead of money? Our free tester circles work on the same platform: you test 15 other apps, 15 developers test yours.

The guarantee, in plain words

Google decides who gets production access. Nobody can promise it, and you should be wary of anyone who does.

What we promise on Pro and Launch: if Google refuses production access because your app needs more testing, we rerun your test for free, with priority, for another 14 days. If Google refuses again, we refund you.

It applies when:

• you followed our setup guide;
• you applied within 7 days of your eligibility date;
• the refusal is about testing, not about a policy issue or a defect in your app;
• you send us the refusal message.

One guarantee per app.

Who this is for, and who it isn't

Good fit: a personal Play Console account created after November 13, 2023; an app that works; no time or network to find 12 people who will open your app every day for two weeks.

Not a fit:

• Organization accounts and personal accounts created before November 13, 2023. Google's rule is written for newer personal accounts. We ask at sign-up and tell you if you probably don't need us.
• Apps that break on launch. Fix crashes first. Google says its review "is not a troubleshooting step".
• Anyone looking for public visibility. Testers can't post anything public about a test version on Google Play (Play Console Help), and nothing here touches your public listing. This is a private beta test.

People, not a ticket queue

Questions go to a person. Our target for a first human reply is under 4 hours, between 8:00 and 23:00 Paris time, by chat or email. An assistant that reads your test's real status answers the common setup problems right away, and hands you over to a human with the context when it can't help. Support is available in English, French and Spanish.