Find 12 testers for your Android app

Who needs 12 testers on Google Play?

The requirement applies to the new personal developer accounts described above. It does not apply to every developer or account type. First check which steps Google shows for your app.

What matters is staying continuously opted in to the closed test, also called Closed Testing . Leaving and later rejoining resets the continuous participation period. Signing up on a community website does not replace opting in on Google Play.

Plan for real usage and feedback. Google may require more testing if engagement is insufficient. Do not tell testers that Google requires a fixed number of minutes per day.

How do I find suitable testers for my Android app?

Entwickler Test Network brings your app and testing request together in one place. Other members can view your project and request to join. This helps you find each other for closed Android testing and exchange feedback directly on the project. Community membership is free.

1. Create your account: Sign up for free and verify your email address. Briefly describe what you are working on in your profile.
2. Introduce your Android app: Create a project in your dashboard. Explain who your app is for, which devices it supports and what you want tested. A clear description helps members decide whether they are a good fit.
3. Approve test requests: When members want to participate, you decide whether to approve them. Approved testers gain access to the saved testing information. Opting in on Google Play is a separate step, explained below.
4. Test other apps yourself: In the Project overview you will find apps from our community. Choose a suitable project and request to participate. Mutual support depends on everyone contributing time and honest feedback.

You do not have to be a developer to participate. People who enjoy trying new apps can become testers too. For your own project, describe precisely which experience and devices would be helpful.

If possible, plan for slightly more than twelve testers. This is a practical buffer, not an additional Google requirement. People may drop out or devices may be unsuitable. Our community is still growing; how quickly you find enough testers depends on available members and their interest in your app.

What to include in your project description

Briefly describe your app’s benefits, required Android version, planned timeframe and two or three specific tasks. Mention whether an account is required or costs apply. A screenshot helps people picture your idea.

I am looking for testers for my Android app for planning shared shopping trips. I am particularly interested in whether creating and sharing a list is easy to understand. If you have time for the closed test, I would love your feedback. You can find the timeframe, device requirements and test access in the project description.

Prepare your closed Google Play test

Try the main flows yourself before inviting others: does the app start? Does sign-in work? Can the main feature be used without your explanation? A short internal test can help catch obvious problems first.

Then set up your closed test in Play Console and publish a test release. You can use an email list or Google Group for access. Google explains setup in its guide to internal, closed and open testing.

Use your project’s feedback section on Entwickler Test Network to keep responses together. Ask testers to include their device, app version and the steps that led to the problem. Track what you have fixed and what needs retesting.

Google Group, test opt-in and installation: what is the difference?

These steps are easily confused. Being approved as a tester and actually opting in to the test are separate things.

Use the same Google account for approval, opting in and the Play Store. Share required email addresses privately; never ask anyone to post them in a public comment. Nobody needs your Google account password for this.

Send brief instructions with links in the correct order. Then ask testers to confirm whether joining, installation and the first launch worked. This helps you catch access problems before testing begins.

Collect feedback that really helps you improve

“It works” is nice but not very informative. Give small tasks instead: create a list, edit an entry or find a setting again. Afterwards, ask where the tester had to stop and think.

The following details help make bug reports reproducible:

• Which device, Android version and app version were used?
• Which steps led to the problem?
• What was expected and what actually happened?
• Does it happen again? Is there a screenshot without personal information?

On my Pixel running Android 15, the shopping list in app version 0.3 stays empty after I save an item. It appears after restarting the app. I expected to see it immediately.

Thank people even for difficult feedback. When you fix a bug, let them know and ask them to try again. Record what you learned and improved through testing. This also helps you describe the testing process honestly when applying for production access.

Testers cannot join or install the app?

Go through access together step by step: is the correct address approved, or is the person in the configured Google Group? Is the same account selected in the browser and Play Store? Has the separate opt-in step been completed?

Also check whether the device and Google Play country are supported by your test. According to Google, a newly published test link may take a few hours to become available. An “App not available” message therefore does not automatically mean the tester has done something wrong.

Find testing partners – free and together

Entwickler Test Network grew out of my own search for Android testers. The idea is simple: introduce your app, let other members request to join and exchange clear feedback. At the same time, you can test other apps and support small developers.

Joining our community is free. You do not have to code: anyone who enjoys trying new apps and contributing ideas is welcome. Whether a particular test app costs money depends on the project; free community access does not automatically mean every app is free.

We are still getting started, so we cannot promise twelve testers or Google approval. Our platform helps you find and organize testers; you still set up the closed test yourself in Play Console.

Checklist: ready for your closed Android test?

• You have checked your account’s requirements in Play Console.
• Your test version launches and the main features are usable.
• Testers know what to try and how long they should participate.
• Approval, the opt-in link and installation have been checked with a test account.
• There is a clear feedback channel and you are tracking improvements.
• You check the test status in Play Console before applying for production access.

Your app does not have to be perfect to start testing. What matters is that testers know what to focus on, you are available for questions and you act on their feedback.