Get 12 testers for Google Play.

Yes, if your Google Play personal developer account was created after 13 November 2023.

If it was, here is the rule (checked 22 October 2026). When you apply for production access, at least 12 testers must have stayed opted in to your closed test, without a break, for the 14 days before. Internal testing does not meet it.

Meeting the rule lets you apply. Google reviews the application.

If your account is older, or it is an organization account, Google's page does not describe this gate for you. Play Console is the authority, so check what it asks of yours. Our advice: don't register a different kind of account just to avoid the test.

Source: Google Play Console Help, App testing requirements for new personal developer accounts, checked 22 October 2026.

Closed testing is a test where only the people you invite can install your app. A tester counts when they have opted in to it.

Google Play Console Help, checked 22 October 2026:

Tester feedback is private. The first test link can also take hours to become available.

Ask real people who would plausibly use your app, tell them exactly what to do, and ask more than 12.

The extra people are our advice, not Google's minimum. But anyone who leaves breaks their own 14 days, and a spare keeps you at 12.

Start with people you know. Google's page suggests friends, family, colleagues and classmates, and they do count. They are quick to ask and they answer messages.

Then add people like your intended users. Google also advises testers who represent your app's intended future audience. They are harder to find. A solo builder on Reddit said so in March 2026: the app was written, and finding the right business managers to try it was the hard part. They give better feedback, because they use the app as the people you built it for would.

Places to look: customers you already work with, a mailing list, a community you belong to, and people you spoke to about the problem before you built the app.

Ask each person for a Google account email, and permission to message them during the 14 days. Tell them what to do: open the link, opt in, stay in, and use the app on their own phone. Give an end date. People say yes to a clear request.

Twelve kind people who never use the app give you a count and little to learn from. Google's page says too little engagement can lead to more testing.

For paid services and swap groups, see the section on paying for testers below.

Create the closed test, add testers by email list or Google Group, then send each person the test link and ask them to opt in on their own phone.

Follow Play Console as it looks today. Menu names change, so we don't list them. These steps come from Set up an open, closed, or internal test, checked 22 October 2026.

1. Set up the test before you ask anyone. The first link can take hours.
2. Add testers by email list or Google Group.
3. Send the link and ask each person to opt in. Being on the list is not opting in.
4. Check anyone who tested internally. They must leave that track first.

A message you can send. This is our draft, not Google's text:

Hi [name]. I'm testing my new app before it goes on Google Play. Could you help for 14 days? Tap this link on your phone, opt in, and install the app. Please stay in the test and use it for [its main job]. I'll message you in the first week and near the end. If something breaks, tell me what you tapped and what you saw. Thank you.

They stay opted in, use the app for its real job, and tell you what breaks.

Google sets the count and the 14 days. It does not set a plan for inside them. This plan is ours, not Google's rule.

Our plan

• Day 0, testers opt in. Check each person got in.
• Day 1 or 2, the first task on their own phone. Ask each tester to do the app's core job once.
• Around day 7, a check-in message and fixes. Ask what broke and what confused them. Fix what you can and release an update. Google recommends updating your app during the closed test. Its page says nothing about updates resetting the 14 days (checked 22 October 2026).
• Around day 12, a closing message. Ask what they would change first, and thank them.
• Day 14, check the console, then apply. Play Console is the authority on who has stayed in.

Two things improve the feedback. Use different phones, because different makes and Android versions show different problems. And give people one easy way to report a failure: what they tapped, what they expected, what happened.

We set no number of opens or minutes a day. Google's page sets none, so any figure would be invented. Don't ask people to install the app and leave it. Don't write feedback yourself, share one account between people, or script what testers say.

This plan gives you a way to use the 14 days. It does not make Google approve you.

Play Console is the authority. Keep your own list as a second check.

The list is our suggestion, not Google's. It helps you spot a drop-out early and gives you facts for your application. One row per tester:

• Tester: a name or ID you can trace to a person.
• Contact permission: whether you may message them.
• Device: make and Android version.
• Date opted in.
• Still opted in: yes or no, and the date you checked.
• What they reported.
• What you fixed.

The number that matters is 12 people who have each been in for 14 days in a row. A tester who leaves and rejoins breaks their own run, not anyone else's. A replacement counts only after their own 14 days.

When the count and the 14 days are met, Play Console lets you apply. Answer from what actually happened.

Google asks about engagement, feedback, audience and readiness. Review usually takes seven days or less, and can take longer (Google Play Console Help, checked 22 October 2026).

Use your list. Say what your testers did, what feedback you got and what you changed. Say who the app is for. Keep it honest, specific and short. If nothing broke and you changed nothing, say that. Don't copy or script your answers.

We can't promise Google will approve, and we can't give you a date.

Read the notice, fix what it points at, and keep testing.

Google's page says more testing can be required if engagement is low or there are too few testers (checked 22 October 2026). We won't guess how long more testing should run. Use the notice and what your testers did to decide what to improve.

If you are short of testers:

• Recruit more, through the same email list or Google Group.
• Remember who counts. Someone who opts in, tests for fewer than 14 days and opts out does not count. Someone who rejoins needs 14 consecutive days.
• Count a replacement from their own start.

A solo developer wrote in April 2026 of two apps and one tester. The way out is to keep asking, make the request clearer, and ask people who will use the app.

Yes, both exist. Paid tester services are sellers. Swap groups are exchanges, where you test other people's apps and they test yours. We don't recommend either, and we can't say what Google will decide.

Hold any route to what Google asks for:

• Real use of the app. Your application asks about engagement.
• Feedback you can summarise. Your application asks about feedback.

A person who installs the app and never uses it gives you neither. Nobody, paid or free, can promise Google's decision. Check what you hand to a stranger: your test link and your app. An install with no use is not testing.

Find your people, set up the closed test and follow the plan above. For the whole path to the stores, see Getting your app into the stores.

One free step helps. The Free Beta Review is where two or three people on our team use your app as new users would and send you what they hit, worst first. It helps you catch what a first-time user trips on before your 12 do.

It is not Google's test. Those people are not your 12 testers, it is not a 14-day closed test, it does not count toward the 12, and it does not give you production access.