How to Get 12 Testers: Free vs Paid Options Compared

There are three realistic ways to get the 12 testers Google Play requires for closed testing: people you know (free, but hard to reach 12 who stay opted in for 14 days), tester-exchange communities where developers test each other's apps (free, but costs you time testing others), and paid tester services (fast, but you pay and should check the details). Whichever you choose, aim for 14 to 16 testers so a dropout does not break your 14-day window.

Below is an honest look at each option, including the trade-offs that are easy to miss.

What you are actually trying to get

It is worth being precise, because "12 testers" undersells it. For personal developer accounts created after November 13, 2023, Google requires:

• At least 12 testers
• Opted in to your closed test
• Continuously for at least the preceding 14 days when you apply

Google also lists insufficient tester engagement as a reason it may ask for more testing, and recommends encouraging testers to use as many features as possible. So you are not just collecting 12 email addresses. You need 12+ people (or devices) that stay opted in and actually open the app for two weeks while you ship updates.

Option 1: Friends, family, and coworkers

How it works

You add their Gmail addresses to your closed testing list, send them the opt-in link, and ask them to install the app and open it regularly.

Pros

• Free
• Trustworthy people who will give you honest feedback
• Easy to reach if something goes wrong

Cons

• Many people use iPhones and cannot help
• Hard to find 12+ Android users willing to stay for 14 days
• People forget to open the app after the first few days
• Wrong-account mistakes are common with non-technical testers

Best for

Developers with a large Android-using network, or as a supplement to another method.

Option 2: Tester-exchange communities

How it works

Developers in the same situation join groups (Reddit threads, Discord servers, Telegram groups, forums, and dedicated exchange apps) and agree to test each other's apps. You join their tests; they join yours.

Pros

• Free in money
• Other developers understand the requirement and the opt-in process
• You can find large numbers of participants

Cons

• Costs time: you are usually expected to install and open many other apps daily
• Reliability varies; some participants leave once their own test finishes
• Feedback is often minimal, which makes the production questionnaire harder to answer specifically
• You may need to recruit replacements mid-test

Best for

Developers who have more time than budget and are comfortable managing a group of strangers.

Option 3: Paid tester services

How it works

You pay a service that supplies testers or devices, adds them to your closed test, and keeps the app opened during the 14 days. Offerings range from individual freelancers to dedicated platforms.

Pros

• Fast to start
• Less management work for you
• Some services provide logs or help with the application

Cons

• Costs money
• Quality and transparency vary widely between providers
• Testers may not give the kind of detailed product feedback friends would

What to check before paying

• How many testers are provided, and is there a buffer above 12?
• How long is the test kept running, and is there margin beyond 14 days?
• Real devices or emulators?
• What happens if fewer than 12 testers end up opted in? Look for a clear refund policy.
• Requirements: country settings, SDK versions, paid app handling.
• Promises: be cautious of anyone who guarantees production approval. Only Google decides that.

Side-by-side comparison

You can combine them

These options are not exclusive. A common approach:

• Use a service or community to reliably reach the count.
• Add a few friends or real target users for meaningful feedback.
• Ship updates every few days based on that feedback.

That gives you both the numbers and the material you need for the production access questionnaire. For recruiting tactics in more depth, see How to Recruit Testers and Android Closed Testers: Who to Find and How.

Which option fits your situation?

A few quick scenarios to help you decide:

• You have a day job and one weekend a week for your app. Exchange communities can eat several hours a week, since you test other people's apps daily. A paid service, or friends plus a service, usually fits better.
• You are a student or between projects with plenty of time. Exchange communities are a reasonable free route. Keep a list of who joined and when, and recruit extras early.
• Your app targets a niche audience you can reach directly. Recruit real target users first. Their feedback is the most valuable material for the production questionnaire, even if you need another source to reach the count.
• You already got "more testing required" once. Reliability matters more than cost now. Pick the option most likely to keep 12+ testers opted in for a clean 14 days, and focus your own effort on shipping updates.

Whatever you choose, do these things

1. Recruit 14 to 16 testers, not exactly 12.

2. Track each tester's opt-in date.

3. Ship at least two updates during the 14 days.

4. Collect feedback in one place.

5. Write your application answers as you go.

About Doply

Doply is one paid option, so here are the plain facts. Doply costs $6.99 per app (plus tax depending on your country; paid via LemonSqueezy with card or PayPal). It provides at least 14 testers, usually 16, on 36 real Android devices (not emulators), and keeps the test running for 18 days (the required 14 plus a 4-day buffer). It checks for new versions daily, updates them automatically, and launches your app across devices every day. You get testing logs and a draft for the production application. If the app is not installed on 12 or more devices, you get a full refund.

Requirements to check first: Doply's tester accounts are Korean, so South Korea must be included as a country on your closed testing track; minSdk must be 33 or lower; targetSdk 36 or 37; paid apps need a 100% discount promotion during the test (not a switch to free). Doply does not guarantee Google's production approval. Details are in the docs.

FAQ

Can I get 12 testers for free?

Yes, through friends and family or tester-exchange communities. The cost is your time, both to recruit and to keep testers opted in for 14 days.

Is it allowed to use a paid tester service?

The official Play Console Help page on the testing requirement describes the tester count and opt-in rules and does not mention paid services. Read Google's current policies and decide for yourself; and avoid any provider that promises guaranteed approval.

How many testers should I actually recruit?

Google requires 12. Recruiting 14 to 16 gives you a buffer if someone opts out during the 14 days.

Do emulators count as testers?

Testers are Google accounts that opt in to your closed test. Prefer providers that use real devices, since the goal of the test is real-world usage on real hardware.