How to Publish an Android App — Testing to Google Play
Use the actual Android project and developer-account requirements to plan the release. Brainbaby can help develop the app, but a preview does not establish that its signed build is ready for Google Play. Keep the selected bundle, testing feedback, store setup and production decision together so each next step has evidence.
Step by step
Define and check the app’s first task
Start with the main screens and one complete user workflow. Inspect navigation, input, loading and error states. Keep the task small enough to reproduce. Check what the project actually produces before planning Android distribution.
Review the Android project and account
Confirm the package name, version code and release configuration in the intended project. Check the developer-account dashboard for verification and setup tasks. Keep unresolved account or signing requirements visible instead of assuming the builder completed them.
Build and upload the intended bundle
Create a correctly signed Android App Bundle through the path appropriate to the project. EAS Submit can upload a valid AAB into a selected Play Console track. Inspect the actual bundle and track status before distributing it. Upload success is not production approval.
Test the installed Android build
Use the intended build on a real Android device. Reproduce the main task, system back behavior, keyboard interaction and any paid workflow. Collect genuine feedback and fix problems. A browser preview or a different bundle does not establish this build’s behavior.
Check whether closed testing is required
For personal developer accounts created after November 13, 2023, Google currently requires at least 12 testers continuously opted in for 14 days before applying for production access. Completing that test is not automatic approval; check the dashboard and application outcome. Other account requirements must also be completed.
Complete the store setup and review rollout
Review the listing, required declarations, reviewer access and actual release status in Play Console. Keep the submitted information consistent with the app. Confirm production access and the intended rollout before publishing. A testing-track release and a publicly available production app are different results.
A small example to adapt
These are original fictional planning examples. They are not a generated benchmark, a completed release or a customer result.
Example brief: test a small Android app
Prepare an Android test plan for a fictional shopping-list app. Check blank input, one valid item, repeated taps, deleting an item, system back navigation and keyboard dismissal. Identify the package, version code and installed build before reporting results. Keep untested behavior marked as untested. Do not claim Play Console production access, review approval or public release.
Testing and production record
Project revision: Package name and version code: Bundle selected for upload: Testing track and installed version: Feedback received and issues fixed: Account-specific closed-test requirement: Production-access application status: Store-review status: Rollout and public availability:
Review before the next action
Match the bundle to the evidence
Record which version testers installed and which bundle is selected for production. Verify that a reported fix is included in that bundle.
Use actual testing feedback
Collect useful observations and resolve issues. Do not treat a tester count as evidence that every workflow was exercised.
Check the final track and status
Review the target track, production-access decision and release controls before publishing. Keep processing, testing and public availability distinct.
Frequently asked questions
Do all developer accounts follow the same closed-test requirement?
No. The cited requirement applies to personal accounts created after November 13, 2023. Check the current requirements shown for your actual account.
Does meeting the tester requirement guarantee production access?
No. Eligible developers apply for production access and Google reviews the application. Keep the outcome separate from the testing milestone.
Does an uploaded AAB mean the app is live?
No. Check the selected track, review and release status. An internal testing build is not a public production release.
Can I skip checking the installed build because the preview works?
A preview does not verify the signed Android build. Test the intended version’s actual behavior before distribution.