What is Google Play's 12 testers for 14 days requirement?

Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 consecutive days before applying for production access. Organisation accounts are exempt, and every new app clears the requirement separately.

What does opted in actually mean?

It means the tester accepted your invitation and joined the test - not merely that you added their email. Testers who never accept do not count toward the twelve, which is the single most common reason a self-organised test fails to qualify.

Are the testers real people?

Yes. Paid professional testers using their own Android phones and genuine Google accounts. No emulators, no bot accounts, no recycled device farms - all of which Google is good at detecting.

What if Google still declines my production access?

You get a full refund. If your test completed and production access was refused, the guarantee applies without argument. In practice this is rare, but the promise is unconditional.

How fast can we start?

Testers are typically opted in within six hours of you submitting your opt-in link. The 14-day clock starts the moment the twelfth tester joins.

Do the testers need to be in my target countries?

No. Google's requirement counts testers, not their locations. If you want country-specific coverage for genuine feedback rather than compliance, tell us at submission and we will match where we can.

Do I need to do anything during the 14 days?

No. Keep your build available on the closed track and leave it alone. You can watch progress in the dashboard, but there is nothing you need to action.

Does uploading an app update reset the 14 days?

No. Pushing a new build to the same closed testing track does not restart the counter, as long as the track stays live and your testers stay opted in.

Is this against Google's rules?

No. Google requires twelve testers; it does not require that you personally know them. What breaks the rules is fake accounts and simulated activity - which is exactly what we do not do.

My closed test was already rejected. Can you still help?

Yes, and it is a large share of what we do. We will look at why the previous attempt failed before starting, because re-running an identical test usually produces an identical outcome.

Can I test more than one app?

Yes. Pricing is per app with no subscription, and there is volume pricing for studios and agencies shipping several apps a quarter.

Which payment methods do you accept?

All major credit and debit cards through Stripe, plus local methods including UPI in supported regions. Payments are processed by Stripe; we never see your card details.

Google Play closed testing, handled

Get 12 testers for 14 days
& publish faster

Google needs twelve testers opted in for fourteen straight days before you can publish. We supply real ones on real devices within six hours, and they stay the whole window.

Approved or your money back
Testers within 6 hours
Trusted in 180+ countries

apps published: 10,000+apps published
success rate: 99.9%success rate
countries served: 180+countries served
from 3,000+ reviews: 4.9/5from 3,000+ reviews

Get your testers

Tell us about your app and we will reply within one business day.

The distinction that decides it

Invited is not the same as opted in

Most closed tests that fail did not fail on effort. They failed because adding an email address to a list does not put a tester into the count Google reads.

Invited

Twelve email addresses on a list
No notification is sent to anyone
Counts as zero until each person accepts
Play Console shows your list length, not your streak
Silently fails on day fourteen

Opted in

Twelve people who opened the link and joined
Visible in the opted-in tester count
Starts the fourteen consecutive days
Daily activity across the whole window
What Google actually measures

Simple process

Sixteen days from checkout to publishable

Your part takes five minutes. The rest is scheduling, and we do the scheduling.

15 minutes
Pay and submit your app
Checkout through Stripe, then paste your Google Play closed-testing opt-in link. That is the whole of your side of the job.
2Within 6 hours
Your testers opt in
15 to 25 real testers on real Android phones accept the invite and install your build. You watch the count climb in your dashboard.
3Days 1-14
They use it daily for 14 days
Genuine daily activity for the full consecutive window Google requires - not a single burst of installs that trips review.
4By day 10
Reports and form answers land
Written feedback plus pre-filled answers for every question on the production access form, ready to paste.
5Day 14
You apply for production access
Submit the form. Google typically returns a decision within 24 to 48 hours.
6Day 15-16
You are live
Production access granted. Your app is publishable to everyone on Google Play.

Your testing dashboard

Watch the fourteen days
build, day by day

You are not left guessing whether the test is working. The count Google reads is the count you see, updated as testers opt in.

Live opted-in tester count, straight from the track
Day-by-day streak so you can see the 14 days build
Feedback reports by day 10, nothing to chase
Pre-filled production access answers, ready to paste

Open your dashboard

app.optedin.app/dashboard

Aurora Notes

com.aurora.notes

Testing active

9of 14

Day

25of 25

Testers opted in

2of 2

Reports ready

14-day consecutive streak64%

Day 924 sessions across 25 testers
Day 825 sessions, 2 issues flagged
Day 723 sessions, 1 crash reported
Day 625 sessions, no issues

Pricing

One price, one app, no subscription

Both plans clear Google's requirement. Pro exists for the margin of safety and the store-listing report, not because Starter is missing something.

Starter

Everything Google asks for, nothing you do not need.

$15per app / one-time

15 Android testersThree above Google's minimum of 12
Testers within 6 hoursOpted in and testing the same day
Full 14-day testDaily activity for the whole window
Production access guaranteeApproved, or your money back
Feedback reportWritten tester feedback you can act on
Pre-filled form answersFor the production access questionnaire
Standard supportEmail replies within one business day

Pro

More testers, more margin for error, plus store-listing help.

$25per app / one-time

25 Android testersDouble the minimum, for a safe margin
Testers within 6 hoursOpted in and testing the same day
Full 14-day testDaily activity for the whole window
Production access guaranteeApproved, or your money back
Feedback reportWritten tester feedback you can act on
Pre-filled form answersFor the production access questionnaire
Detailed ASO reportStore listing fixes that lift installs
Priority supportSame-day replies, front of the queue

Deep Testing Package

Optional add-on

Two senior QA engineers spend two hours each inside your app - four hours of hands-on testing, returned as a 52-point report.

4 hours of hands-on senior QA
52-point structured audit
Crash, ANR and edge-case hunting
Prioritised fix list before you ship

$50

add-on / one-time

One-time payment per app. No subscription, no renewal. Cards and local payment methods handled by Stripe — we never see your card details. If Google declines production access after a completed test, you are refunded in full.

Why it works

Built around how the review is actually judged

Google is not counting installs. It is looking for a credible two-week test by real people, and an application that reflects it.

Real people, real devices

Every tester is a paid professional using your app on the Android phone they carry daily, signed in with a genuine Google account. No emulators, no farms.

Opted in, not just invited

Google counts testers who accept the invite. Ours do - that single distinction is where most self-organised tests quietly fail.

Approved or refunded

If Google declines your production access after a completed test, you get your money back. No forms, no argument.

Built for the 14-day window

Activity is paced across the full consecutive period, because a burst on day one and silence after is exactly what review flags.

Answers you can paste

The production access form asks how you recruited testers and what you learned. We hand you defensible answers drawn from your actual test.

Support that knows the policy

Questions answered by people who read the Play Console policy updates, not a script. Priority queue on Pro.

Loved by developers worldwide

What developers say after they publish

The pattern in the feedback is consistent: the compliance part is expected, the specificity of what came back is not.

“It did more than tick Google's box. The feedback was specific enough that I shipped three fixes before launch that I would never have found alone.”

Madeline PetersenIndie developer · Canada

“Rejected five times on my own. One run through this and production access came through. I wish I had stopped guessing sooner.”

Nirav K. PatelFounder · India

“The testers showed up in about four hours. What I actually valued was the honest read on why my earlier submission failed review.”

Adam TalMobile engineer · United States

“I had twelve names on a spreadsheet and four who ever opened the app. The difference between invited and opted in cost me a month.”

Lena FischerProduct lead · Germany

“We push four or five apps a quarter. This is now just a line item in the launch checklist instead of a fortnight of chasing friends.”

Rafael MoreiraStudio owner · Brazil

“The pre-filled production access answers were the part I underestimated. I had been writing two vague sentences and wondering why review stalled.”

Yuki TanakaSolo developer · Japan

FAQ

Questions worth answering properly

If yours is not here, email us and a person who knows the policy will answer.

Stop chasing twelve people

Checkout takes a minute, testers arrive within six hours, and the fourteen days start today rather than whenever your last friend gets round to it.

Start testing from $15 Try the free route first

Approved, or your money back. No subscription.

Get 12 testers for 14 days & publish faster