How many testers should I recruit?

The requirement is 12, but some people will drop out along the way, so it's safer to recruit at least two or three more. With exactly 12, one person uninstalling the app breaks the requirement.

Where should I post my recruiting message?

Common places are channels with friends and coworkers, Android developer communities, and groups where developers swap testers (on Discord, Telegram, Reddit, and the like). Even with the same message, posting where people who'd actually use your app hang out gets you more people who try it and give feedback.

Can iPhone users take part?

No. Google Play closed testing works by installing from the Play Store on an Android device, so iPhones can't take part. Saying so up front in your post saves everyone time.

Do I need to reward testers?

It's not required. But when it's clear what you're asking and until when, and you promise a thank-you or a small reward at the end, more people stay to the finish. In the questionnaire, describe truthfully how you recruited testers.

← Blog

How-to

How to write a call for app testers: example posts you can adapt

The clearer your call for testers is about what you're asking and for how long, the more people stay until the end. We list seven things every post needs, example texts you can adapt — the recruiting post, opt-in confirmation, mid-test reminder, and thank-you message — and tips for reducing dropouts over the 14 days.

Last checked Oct 14, 2026.

1. Your recruiting post decides the outcome

The hard part of closed testing isn't getting 12 people — it's keeping them for 14 days. And whether they stay to the end depends a lot on the recruiting post you start with. People who join from a post that only says “Need testers, please click the link” tend to install the app and then uninstall it a few days later.

Google also advises you to let testers know they need to stay opted in for 14 days. If you spell out from the start what you're asking, until when, and why, fewer people drop out and you get more feedback.

2. Seven things to include

One line on what the app is. People need to know what it is before they want to try it.
Why you need their email. Explain that you have to add the Google account they use for the Play Store as a tester.
How to join. Three steps: send their email → become a tester via the opt-in link → install.
The end date. “Until ○○/○○” is easier to stick to than “14 days.”
Why they shouldn't uninstall. One line saying the test starts over if they uninstall midway prevents more dropouts than anything else.
Where to leave feedback. A Discord or Telegram group, or an email address. Google also recommends gathering testers in a messaging group to share feedback.
What they need. An Android phone and a Google account. Say up front that iPhones can't take part.

3. Templates you can adapt

Just replace the ○ parts. The headcount adds a buffer on top of the 12 required.

Recruiting post

[Looking for 15 Android app testers] ○○ — one-line app description

I'm looking for people to join a closed test before my app launches on Google Play.

■ What you'll do
1. Reply below or message me with the Google account email you use for the Play Store.
2. Once I add you as a tester, I'll send you an opt-in link. Tap [Become a tester] on that page and install the app.
3. Please keep the app installed until ○○/○○ (a little over 14 days from install) and open it about once a day.
4. If anything bugs you while using it, just leave a one-line note. (Discord / Telegram group / email)

■ What you need
- An Android phone (iPhones can't take part)
- A Google account

■ Test period
○○/○○ – ○○/○○ (if you uninstall the app midway, the test starts over from scratch)

■ A thank-you (optional)
A ○○ coupon after launch / I'll test your app in return, etc.

Confirmation · when sending the link

Thanks so much for joining!
Opt-in link: (link)
1. Open the link above, tap [Become a tester], then install the app from the Play Store.
2. If you're signed in with a different Google account, you won't see the app. Open it with the account you gave me.
3. Please keep the app installed until ○○/○○. Opening it about once a day helps a lot.

Mid-test update (on the day you ship an update)

We're on day ○ of testing. Thanks for sticking with it!
I shipped a new version (1.0.2) today — the first screen loads faster now.
Could you quickly check that the app is still installed? If anything bugs you while using it, just leave a one-line note.
End date: ○○/○○

Closing thank-you

The 14-day test is over. Thank you so much for staying until the end!
I'll let you know once the production launch result is in. Until then, it would be great if you kept the app installed.
(Once it launches, I'll send you the link and a thank-you coupon.)

The mid-test update feels natural if you send it on the day you ship an update. When testers try the new version and give feedback, that becomes your “feedback received and changes made” in the production access questionnaire.

4. Tips for reducing dropouts

Gather everyone first, then send the opt-in link on the same day. Everyone ends on the same date, which makes it easier to communicate, and your 14 days are as short as possible.
Keep at least two or three testers above the required 12. Anyone who joins later starts their own 14-day count from that day.
Reach out at least once mid-test. Share your update news and ask them to check that the app is still installed.
Ask them to keep the app installed after the end date too, until the production result is in. You may be asked to test more.

For adding testers in Play Console, see How to add testers; for how many to recruit, see 12 or 20 testers?. If you're swapping tests with other developers, also read Closed testing tester swaps.

5. If recruiting is hard

If you don't know many Android users, or you don't have time to look after testers for 14 days, you can choose another approach instead of recruiting. We compare the cost and dropout risk of each in Ways to find testers compared. With DUIRE, real Android devices join as testers, run your app every day for 14 days, and keep records.

Frequently asked questions

How many testers should I recruit?: The requirement is 12, but some people will drop out along the way, so it's safer to recruit at least two or three more. With exactly 12, one person uninstalling the app breaks the requirement.
Where should I post my recruiting message?: Common places are channels with friends and coworkers, Android developer communities, and groups where developers swap testers (on Discord, Telegram, Reddit, and the like). Even with the same message, posting where people who'd actually use your app hang out gets you more people who try it and give feedback.
Can iPhone users take part?: No. Google Play closed testing works by installing from the Play Store on an Android device, so iPhones can't take part. Saying so up front in your post saves everyone time.
Do I need to reward testers?: It's not required. But when it's clear what you're asking and until when, and you promise a thank-you or a small reward at the end, more people stay to the finish. In the questionnaire, describe truthfully how you recruited testers.

Meet the requirement without recruiting testers

DUIRE joins your closed test with real Android devices and opens your app every day for 14 days. Registering your app and checking installability are free.

Check installability See how it works