Publishing for Android Developers
Publishing is the process of getting an Android app to users through the Google Play Console. It involves signing releases, building an Android App Bundle, filling in the store listing, moving through testing tracks, and setting up CI/CD and crash reporting so you can ship updates and watch for problems after launch.
Stage: Release and Beyond · Part of the Android Developer roadmap · Last reviewed 19 November 2026
What to learn in Publishing
- Generate an upload key and understand Play App Signing
- Build a release Android App Bundle with Gradle
- Roll out through internal, closed and production tracks
- Automate builds and tests in a CI pipeline
- Read crash reports and prioritise fixes after a release
Publishing interview questions
What is an Android App Bundle and why does Play prefer it?
An App Bundle is a publishing format that contains all compiled code and resources. Google Play uses it to generate optimised APKs for each device configuration, such as screen density and CPU architecture, so users download less. It replaced uploading a single universal APK for new apps.
What is the upload key in Play App Signing?
With Play App Signing, Google holds the app signing key and you sign uploads with a separate upload key. If the upload key is lost or compromised, you can ask Google to reset it, which would be impossible if you alone held the only signing key.
Where Publishing fits in the Android Developer roadmap
Publishing belongs to the Release and Beyond stage (intermediate level), which takes about 6 hours. Ship and grow.
Other units in this stage
Back to the full Android Developer roadmap