How I Found 12 Testers for Google Play Closed Testing, Twice

Friends and family for my first app, Reddit “test for test” for the second, plus a Reddit post template you can copy.

Over the past months, I built and shipped two Android apps on my own. I wanted hands-on experience with Kotlin Multiplatform and with taking an app all the way from an idea to Google Play. The first one is an exam prep app for the German citizenship test. The second one is a grid-based puzzle game that challenges your focus and memory.

Writing the code was the part I expected to be hard. The part that surprised me was closed testing. Before Google Play lets you publish a new app, you need real people to test it, and finding those people took more effort than I planned. When I searched for advice, I mostly found short posts with the rules and not much about how to get testers. So this is the article I wanted at the time. I’ll share the two approaches I used, what worked, and how I kept testers around for the full 14 days. You’ll also get the Reddit post I used to offer “test for test”, ready to copy for your own closed test, plus the reminder emails I sent to my testers.

The 12 Testers Rule in Short

If you have a personal Google Play developer account created after November 13, 2023, you can’t publish a new app straight to production. First, you need to run a closed test (a test release that only invited people can install) with at least 12 testers who stay opted in for 14 days in a row. After that, you can apply for production access.

My account was created in 2025, so the rule applied to both apps.

A tester is a Google account, not a device. If you have two Android phones with two different Google accounts, both can count.

My First App: Asking Friends and Family

For my first app, I asked people I knew. I messaged friends and family on social media, explained what the app does, and asked if they had a few minutes to help. When someone agreed, I asked for the email address of their Google account and added it to the closed test’s email list in Play Console. Then I sent them the opt-in link, which is the page where a tester confirms they want to join the test.

I invited about 15 people, and 14 of them joined. I also used two Android devices of my own, each with its own Google account.

It worked, but it wasn’t easy:

• People are busy. Getting someone’s attention, then getting them to opt in and install the app, often took more than one message.
• Many of my friends use iPhones. Closed testing on Google Play needs an Android phone, so I had to leave out several close friends who would have been happy to help.

My Second App: Reddit Test for Test

For my second app, I tried something different. I relied mostly on Reddit.

There are a few subreddits where developers help each other with closed testing. The idea is test for test: you test someone’s app, and they test yours. I posted in these three:

• r/AndroidClosedTesting
• r/20AndroidTesters
• r/AndroidAppTesters

For this test, I created a Google Group and added it as the tester list in Play Console. With a group, I didn’t need to collect emails one by one. Anyone who joins the group can opt in.

My post explained what the app is, what testers need to do, in which order, and what I offer in return. The order matters. Testers need to join the Google Group first. If they open the opt-in link before joining, the Play Store shows an error.

My “test for test” post. You’ll find a reusable version of it at the end of this article.

Posting once wasn’t enough. I also went through other people’s “need testers” posts, joined their tests, installed their apps, and left a comment with a screenshot as proof. Then I asked if they could join my test too. Most people were happy to.

In total, I reached out to more than 20 people, and about 16 joined. The community was friendly and helpful, and it was much easier than asking friends again.

It Only Works Both Ways

This is the most important part of the Reddit approach: don’t expect people to test your app unless you test theirs.

Testing back isn’t a one-time thing. Other developers need their 14 days too, so I opened their apps regularly and kept them installed until their closed tests were finished. If you uninstall someone’s app after a few days, you might drop them below 12 testers, and they’d have to wait longer.

It takes time. During those two weeks, I spent part of almost every day on Reddit, testing apps and answering comments. But that’s also why people kept testing mine.

Keeping Testers for 14 Days

Getting 12 testers is the first half. Keeping them opted in for 14 days is the second.

I used a simple routine of four short emails:

1. Day 1: a group email when the test started, with the start and end dates, so everyone knew how long it would take.
2. Around day 5: a quick thank-you and reminder. For the Reddit testers, I also mentioned that I was still testing their apps, so they knew the deal was going both ways.
3. Around day 10: a reminder that we were almost there, asking everyone to keep the app installed until the end.
4. After day 14: a thank-you email. For the Reddit testers, I promised to keep their apps installed until their own tests finished.

Feedback From the Testers

Testing is a requirement, but it also gave me real feedback. The testers didn’t find any bugs, but I got some valuable feedback on the UI and user experience, and a few feature ideas. I added a couple of them before the production release.

Friends and Family vs Reddit

Two ways to find 12 testers, side by side

If you have enough friends with Android phones who are happy to help, the first approach is quick to set up. If not, Reddit works well, as long as you’re ready to spend time testing other apps.

Reddit Post Template

**[Test for Test] Need testers for [App Name] ([short description]); I'll test your app back right away!**

Hi everyone! 👋

I'm looking for testers for my new Android app, **[App Name]**, [one sentence about the app].

I need 12 testers to opt in and keep the app installed for the required 14 days. **I'll gladly test your app in return. Just drop your links and a screenshot in the comments!**

**How to test [App Name] (please follow in order):**

1. **Join the Google Group (required first step).** You must join the group first, or the Play Store links below will show an error. Group link: [Google Group link]
2. **Opt in as a tester on the web.** Web opt-in link: [opt-in link]
3. **Download the app on Android.** Play Store link: [Play Store link]
4. **A quick favor for the 14-day run:**
    - Please keep the app installed for the full **14 days**.
    - If you have a spare moment, open it now and then and [play a round / try a feature].
    - Any feedback on [the UI, features, bugs] is hugely appreciated!

Once you've joined and installed it, **leave a comment with your app's testing links and a screenshot**, and I'll download and test yours right away. Thank you so much for the support! 🚀

Tips

• Aim for a few more than 12 testers. If someone drops out, you still have enough.
• Put the steps in order. Group first, then the opt-in link, then the Play Store link.
• Be active every day during the test, both on your own post and on other people’s.
• Send reminders on a schedule. A short email on day 1, 5 and 10 kept everyone on board.
• Test back, and keep testing. Keep other people’s apps installed until their tests are done.

Wrapping Up

Closed testing felt like a wall at first, but with a plan, it’s manageable. Friends and family can get you there quickly if enough of them use Android. Reddit’s test for test communities can get you there too, as long as you give back as much as you ask for.

After closed testing comes the application for production access and the Play review. That had its own surprises, and I’ll cover it in a separate article.

If you’d like to see the two apps that went through this:

• Leben in DE: exam prep for the German citizenship test.
• FocusCells: a grid-based puzzle game for focus and memory.