Closed testing an App Inventor, Flutter or Unity app
Start with the Android build your testers will install from Google Play. A successful editor preview is a useful first check. Your closed-test plan should also cover installation, real tasks and returning to saved work.
Prepare the build you intend to ship
Google Play uses an Android App Bundle to generate device-specific APKs. Package names are permanent. Google's app setup guide.
For a new app, prepare an app bundle and follow Play Console's signing and release steps. APK uploads are a legacy option for apps created before August 2021. Google's release guide.
Use your builder's current Android export instructions. Record the package, build version and export date. Check that your uploaded file is the intended build before inviting testers. The Play Console checklist covers the next steps.
Choose useful tasks for your app
These are suggested tests, not extra Google requirements. Use only the tasks that match your features.
- App Inventor: ask someone to move through the main screens, save an item, close the app and find it again. If it uses the camera, location or files, try both accepting and declining the permission.
- Flutter: try onboarding and sign-in, the keyboard on a small screen, larger text, backgrounding and returning. Check a failed network request and the recovery path.
- Unity: start a fresh game, pause and resume, finish a level, save and reload. Try audio interruptions and a longer session. Note device heat, battery use and visible stutter.
For every report, ask for the installed version, device, steps, expected result and actual result. A screen recording can help when words are unclear. Ask testers to leave private information out of recordings.
Check what the automated report actually reached
Google's pre-launch crawler explores installed builds on test devices. Automatic credential entry needs standard Android widgets; it does not support OpenGL custom controls or WebView sign-in. For OpenGL apps and games, Google recommends a game loop to guide the test. Google's pre-launch report setup.
Inspect the report before treating it as coverage of your whole app. If it stopped at login or a menu, arrange a human test of the screens beyond that point. Keep those results with your feedback log for the production-access application.