Find people who can actually test your app
Recruit for the work you need done: eligible people with supported Android devices, enough time to participate and a way to give useful feedback. Tell them what the app does, which journeys to try and how long the commitment lasts before asking them to join.
If your Play Console requires the 12-tester, 14-day closed test, count actual Play opt-ins rather than replies to your invitation. Check which accounts the requirement applies to and keep Play Console as your reference.
Which recruitment method fits your test?
| Method | Useful when | What you need to manage |
|---|---|---|
| Existing or intended users | Your app solves a specific problem and you can reach people who have it. | Recruitment, access, instructions and regular feedback follow-up. |
| Friends and professional contacts | You need an initial group you can contact directly. | Device eligibility, honest feedback and continued participation. |
| Relevant online communities | You can contribute to a community whose members fit the app. | Community rules, individual invitations and a reliable testing record. |
| Developer exchange such as AppFledge | You can test other apps in return and want one place to coordinate. | Your own testing contribution, Play access and acting on feedback. |
You can combine methods. Developer peers can spot confusing flows while intended users help you evaluate whether the app solves their problem. Keep one clear set of tasks and avoid counting the same person twice across recruitment lists.
Is AppFledge a good fit?
AppFledge is a give-and-get closed-testing community for Android builders. It fits developers with an app ready to test who can use other developers' apps and share useful updates in return.
- Your first app is free during beta. Free refers to the platform charge; participation takes your time.
- You need a supported Android device for your own testing contribution.
- You manage your Play Console release and grant testers access.
- Testers come from the available community. A fixed arrival date, completed tester count or production approval is not guaranteed.
- If you need a guaranteed start date, paid QA specialists or no reciprocal testing, this beta does not offer those services.
How to find testers through AppFledge
- 1
Add an app people can understand
Provide the purpose, device requirements, screenshots and practical tasks. Explain any test login or setup before a tester joins. Complete the readiness checklist and publish your app to the community.
- 2
Contribute to another developer's test
Choose an eligible app, follow its access instructions, install through Google Play and confirm your opt-in in the workspace. Your first such confirmation activates Starter Boost when it is needed; an empty pool can activate it without that step.
- 3
Open access for your incoming testers
With an email list, add the consenting testers' Play emails to your track. With a developer-owned Google Group, configure that Group on the track and share the self-join URL. Testers still need to opt in through Google Play.
- 4
Check progress and answer feedback
Follow reported opt-ins, activity and updates. Compare the community record with your Console count. Fix blockers quickly so an access problem does not look like an unresponsive tester.
- 5
Keep your contribution going
Use the apps you joined and submit qualifying testing updates. Credits support further tester joins to your own app. Read each test's exact requirements and deadlines before committing.
Read the current Starter Boost, credit and testing commitments →
What should you include in a tester invitation?
Make the invitation specific enough for someone to decide whether they can help. This is an illustrative example for a fictional reminder app:
I'm testing a reminder app for people who plan recurring household tasks. I need Android users who can try creating, editing and completing a reminder over the testing period. I'll provide the Google Play access steps and a short task list. Please report confusing behaviour and steps to reproduce bugs. If we agree to exchange tests, send me your app's requirements so I can check that I can take part too.
Add your actual device requirements, dates, access instructions and feedback channel. Share Google emails privately and only with consent. Do not ask for positive public ratings as a condition of participating.
Recruitment is only the start
Before inviting a large group, confirm that someone can reach the app, install it and complete the first task. During the test, ask focused questions and acknowledge the feedback you receive. At the end, record the problems found and the changes you made.
See how participation and feedback can become a testing report, or use the closed-testing troubleshooting checklist if testers cannot access the build.
For the policy behind the test, refer to Google's official testing requirements. AppFledge coordinates community testing; Google makes its own production-access decisions.
Have an Android app ready for closed testing?
AppFledge connects builders who test each other's apps. Your first app is free during beta; you contribute testing time in return. Tester availability and Google Play approval are not guaranteed.