Google Play 12 testers for apps made with App Inventor, Kodular, Flutter, Unity and other builders
Updated October 2026
It doesn't matter which tool you used to build your app. If your Google Play developer account is a new personal account, you need a closed test with at least 12 testers for 14 days before you can publish to production. This guide covers the parts that trip up builder and game-engine users, and a free way to find the testers.
The rule is the same for every tool
Google checks your developer account, not your tool. Apps made with MIT App Inventor, Kodular, Niotron, Sketchware, Thunkable, FlutterFlow, Flutter, React Native, Expo, Unity or Godot all go through the same closed test.
If you created a personal developer account after 13 November 2023, you need at least 12 testers opted in for 14 days in a row before you can apply for production access. Organization accounts don't have this requirement.
Step 1: export a release build your builder can sign
- Export an Android App Bundle (.aab). Google Play needs an .aab for new apps. Most builders and engines can export one; if yours only offers an APK, check its documentation for the App Bundle option.
- Keep your signing key safe. Builders such as App Inventor and Kodular create a keystore for you. Download a backup of it. You need the same key for every update.
- Choose your package name carefully. It can never change once the app is on Google Play.
- Meet the target API level. Google Play only accepts builds that target a recent Android version. If the upload is rejected for its target API level, update your builder or engine and export again.
Step 2: set up the closed test
- In Play Console, open Test and release → Testing → Closed testing and create a track.
- Add testers with a Google Group rather than an email list: testers join the group themselves, and you never paste emails again.
- Upload your .aab to the closed track, add release notes and send it for review.
- Copy the opt-in link. Testers join the group, open the opt-in link, tap "Become a tester", then install from Google Play.
Step 3: find 12 testers who stay for 14 days
Twelve names on a list isn't enough. Google reviews whether testers really used your app, and the 14 days only count while at least 12 testers are opted in. Recruit 14 or 15 people, so one or two dropouts don't stop the clock.
- Friends and family with Android phones: free, but they often stop opening the app after a few days.
- Builder communities and forums: fellow builders understand the rule, and many swap tests.
- A test exchange: on Tester Exchange you test other developers' apps a few minutes a day and earn credits, or join a free swap circle of 13 developers who test each other's apps.
Step 4: keep testers active and ship an update
- Give testers one small task per day, so they have a reason to open the app.
- Upload a new build with fixes around day 7 and say what changed. Builders make this quick: export, upload to the same closed track, done.
- Ask for written feedback and fix what you can. It also gives you real answers for the production questions.
Step 5: apply for production
After 14 days, apply for production access in the Play Console dashboard. Google asks how you recruited testers, how they used the app and what you changed based on their feedback. Answer with real numbers from your test. Google usually replies within about a week.
Frequently asked questions
Do apps made with App Inventor or Kodular need 12 testers too?
Yes. The requirement depends on your developer account, not the tool. New personal accounts need 12 testers opted in for 14 days, whatever the app was built with.
Can my testers install an APK I send them instead?
No. Only installs from the closed test on Google Play count. Testers must opt in with the link from Play Console and install from the Play Store.
Do I need a new build to start the closed test?
You need at least one build uploaded to the closed track. Uploading a second build during the test with fixes from tester feedback is a good idea.
Is there a free way to get 12 testers?
Yes. Test swaps are free: you test other developers' apps and they test yours. Tester Exchange verifies daily use on each tester's phone, so the testing is real.