How to get 12 Google Play testers for free

Updated

Finding twelve people is not the hard part. Keeping twelve people opted in for fourteen continuous days is. If one drops out on day nine and you are at eleven, you are not meeting the requirement until you are back at twelve.

So this list ranks the free methods by how well each one holds testers, not just how many it finds. Most developers end up combining two or three.

Before you ask anyone

Get these ready first, so every person you ask can join in under two minutes:

  1. A closed testing track with a published release. The opt-in link only works once the release is live. Setting that up is covered here.
  2. The opt-in link, not your Play Store link. Testers must open the opt-in link and accept, or they do not count.
  3. A way to add them. A Google Group lets people add themselves; an email list means you add each address by hand.
  4. A target of fifteen, not twelve. The extra three are your margin.

1. Your own test-for-test exchange partners

Holds testers: well, because both sides need the same thing.

In an exchange, another developer tests your app and you test theirs, both for the full fourteen days. It works because nobody is doing you a favour: if they leave your test, you can leave theirs. That shared stake is what keeps people opted in on day nine, when goodwill has run out.

The catch is the obligation. You are promising fourteen days of someone else's test, and your reputation depends on keeping it.

TestersWiz is a free exchange built around this. Each tester's Google account is checked against the developer's Play Console tester list before they count, both sides are held to the full window, and there is no cap on how many testers you take. You never have to buy anything: the Wizbit that lists your app is earned by testing someone else's, and buying one instead is optional.

2. People you already know

Holds testers: well for a few people, badly at twelve.

Friends, family and colleagues are the best testers you will ever have, but few people have twelve with Android phones who will keep an unfinished app for two weeks. Ask individually, not in a group chat. A personal message gets answered; a broadcast gets a thumbs-up and no opt-in.

A message that works:

Hi [name], I'm launching my first Android app and Google needs 12 people
to test it for 2 weeks before I can publish it. Could you help?

1. Open this link on your Android phone: [opt-in link]
2. Tap "Become a tester", then install the app from the Play Store page
3. Keep it installed for 2 weeks. Opening it now and then helps a lot

Any feedback, even "this screen confused me", is really useful. Thank you!

Then check your Play Console count rather than trusting "done!" replies. Here is how to verify each one.

3. Your own audience

Holds testers: very well, because they want the app.

If you have a waitlist, a newsletter, a social following or users of an earlier project, these are the people Google's help page has in mind when it suggests reaching "communities where potential users exist". They are real users, their feedback is useful, and they have a reason to stay.

Most first-time developers do not have this yet, which is why it is third.

4. Developer communities

Holds testers: unpredictably.

App-testing subreddits, Discord servers and developer forums have people who will help, and plenty of developers asking for exactly the same thing. Many communities limit these posts because of the volume, so read each one's rules before posting.

What works: offer to test in return, give the link and the three steps above, and follow up. What does not: a bare link and "need testers pls".

Testers from communities are strangers with no stake in your test, which is why this method drops people most often. Recruit more than you need.

What not to do

  • Your own spare accounts or emulators. They do not make your testing real, and production review looks at whether it was. Why own accounts are a risk.
  • Counting invitations. Invited is not opted in. Only opted-in testers count.
  • Stopping at twelve. One opt-out and you are below the line.
  • Removing testers after fourteen days. Keep everyone until Google grants production access; the review comes after the test.

Keeping them for fourteen days

  1. Check the count every two or three days, not only at the end. Play Console shows the current number, not a history.
  2. Replace drop-outs immediately. Every day you spend below twelve costs you, so add a replacement the same day. What to do when someone opts out.
  3. Ship an update in the middle. It gives testers something to look at, and a new build does not reset the clock.
  4. Ask for feedback once, specifically. "What confused you on the first screen?" gets answers. "Any feedback?" does not. You will need that feedback for the production access form.

If free methods are too slow for your deadline, paying for testers is a reasonable choice too. The trade-offs are in free vs paid app testers.

Next steps

Still need testers? Get 12 testers for your closed test through a free test-for-test exchange - you test another developer's app, they test yours, and every opt-in is verified.

Common questions

Can I get 12 testers for Google Play without paying?
Yes. People you know, your own audience, a test-for-test exchange and developer communities are all free. What they cost is time, and the hard part is not finding twelve people but keeping twelve opted in for fourteen continuous days.
How many testers should I recruit to be safe?
Aim for fifteen. The requirement is at least twelve opted in for the whole fourteen days, and one opt-out or lost phone below twelve breaks the window. Nothing penalises a larger cohort.
Can I use my own Google accounts as testers?
Do not rely on it. The requirement is about real people testing your app, and accounts that exist only to fill the count are the kind of participation production review is designed to catch.

Apps currently in closed testing

Real developers running the test described above. Test one, and get testers for your own app back.

Closed testing

In Between is a free card game. Join the group, opt in, install, open it and play a hand. Keep it 14 days. Not available in South Korea. I test your app back the same day.

Games

Available in all countries

Open to testers · 14-day test

Closed testing

# BAYAA — Closed Testing: Instructions for Testers Thank you for participating in the BAYAA (بياع) closed testing program. BAYAA is a Mauritanian marketplace designed to connect customers with shops, restaurants, pharmacies, hotels, and service providers. ## 1. What testers are expected to do - Install BAYAA through the official Google Play closed-testing link. - Keep the app installed throughout the 14-day testing period. - Open and use the app regularly during the testing period. - Create an account and test registration and login. - Browse available shops, products, and services. - Test search and navigation. - Test merchant features if you have a merchant account. - Check WhatsApp contact options where available. - Report bugs, errors, confusing screens, and suggestions. ## 2. What feedback should you provide? Please tell us: - What worked correctly? - What did not work? - Were any pages slow or difficult to use? - Did you experience crashes or unexpected errors? - What features would you like us to improve? Honest feedback is very important. You do not need to give positive feedback if you encounter a problem. ## 3. Important testing rules - Use the app with your own tester account. - Do not share your login credentials. - Do not enter real payment or sensitive personal information. - Do not make fake purchases or transactions. - Do not uninstall the app during the testing period unless instructed. - Keep your Google Play testing enrollment active. ## 4. Reporting problems Send your feedback and screenshots of errors to the BAYAA development team. Thank you for helping us improve BAYAA and prepare it for its official launch in Mauritania. **BAYAA — بياع | Supporting Mauritanian Businesses**

Shopping

Available in all countries

Open to testers · 14-day test

Closed testing

PocketLedger helps you know your money and own your month — without handing your financial life to anyone. Everything stays on your phone. There is no account to create, no bank login, no SMS reading and no internet access at all. PocketLedger works fully offline. TRACK EVERY RUPEE (OR DOLLAR, EURO, POUND) • Add income and expenses in seconds, with category, account, date, merchant and notes • Mark refunds so they reduce your spending instead of counting as income • Search by merchant or note, filter by type, and tap any category to see its transactions for the month • INR, USD, EUR and GBP supported — amounts in different currencies are never mixed or converted SEE YOUR MONTH AT A GLANCE • Net cash flow, total income and total expenses for any month • Spending by category with an interactive chart • Recent transactions and account balances on one screen BUDGETS THAT KEEP YOU HONEST • Set a monthly limit for any category • See what you have spent, what is left, and when you go over ALL YOUR ACCOUNTS • Cash, bank accounts, UPI, credit cards and wallets • Pick from popular banks (SBI, HDFC, ICICI, Axis, Kotak and many more) and UPI apps, or type any name • Live balance for every account NOTHING IS EVER LOST • Every transaction keeps a full version history: see exactly what changed, when • Deleted transactions can be restored • An activity log records every add, edit, delete and setting change PRIVATE BY DESIGN • No sign-up, no ads, no tracking, no analytics • No internet permission — your data physically cannot leave the app • Not backed up to the cloud PocketLedger is a personal budgeting and expense-tracking tool. It does not offer loans, payments, banking or investment services and does not connect to any bank. Made by Technopreneurs Technolabs.

Finance

Available in all countries

Open to testers · 14-day test

Related guides

May we use analytics and ad measurement? Analytics (Vercel, and Ahrefs on our public pages) count page views without cookies. Ad measurement lets Google's tag on our public pages see which visits came from our Google ads, using a Google cookie. The site works the same either way. Cookie Policy · How Google uses data ·