Publishing to Play Store
Prepare your app for release. Configure build.gradle for production, sign with a keystore, build an AAB, set up Play Console, and use staged rollouts.
Publishing to Play Store is a free Android Academy lesson on CoddyKit. This is lesson 6 of 6. Any 3 lessons of this learning path are free to read in full — after that, CoddyKit PRO unlocks every lesson, plus hands-on practice with a built-in code editor and a 24/7 AI tutor. It is part of the Android Academy learning path, and your progress syncs across the web and the CoddyKit app. The Android Academy course includes 6 lessons in total.
Before You Publish
Before releasing to the Play Store, make sure you've:
- Set a proper app name, icon, and description
- Updated
versionCodeandversionNamein build.gradle - Tested on multiple screen sizes and Android versions
- Set
minSdkappropriate for your audience - Removed debug logs and test credentials
versionCode and versionName
Two version fields in app/build.gradle:
versionCode— integer, must increment with every release (1, 2, 3…). Used by the Play Store to detect updates.versionName— human-readable string shown to users ("1.0.0", "2.3.1"). Use semantic versioning: major.minor.patch.
Build Config
Before building a release APK/AAB, configure your build type in build.gradle:
android {
defaultConfig {
applicationId "com.yourcompany.yourapp"
minSdk 26
targetSdk 34
versionCode 1
versionName "1.0.0"
}
buildTypes {
release {
minifyEnabled true // removes unused code (ProGuard)
shrinkResources true // removes unused resources
proguardFiles(
getDefaultProguardFile("proguard-android-optimize.txt"),
"proguard-rules.pro"
)
}
}
}Signing the App
Every Android app must be digitally signed before release. You need a keystore — a file containing your private key.
Create it once: Build → Generate Signed Bundle/APK → Create new keystore in Android Studio.
Warning: If you lose your keystore, you can never update your app. Back it up securely!
AAB vs APK
Google Play requires AAB (Android App Bundle) format for new apps (not APK):
- AAB — Google Play generates optimized APKs per device from it. Smaller download for users.
- APK — older format, still used for sideloading and testing
Build → Generate Signed Bundle/APK → Android App Bundle
Play Console Setup
Steps to publish on the Google Play Console:
- Create a developer account at play.google.com/console (one-time $25 fee)
- Create a new app — choose country and language
- Fill in the store listing: title, description, screenshots, feature graphic
- Set the content rating using the questionnaire
- Upload your signed AAB to the Internal Testing or Production track
Release Tracks
Google Play has multiple release tracks — use them in order:
- Internal Testing — up to 100 testers, approved instantly
- Closed Testing (Alpha) — invite-only group of testers
- Open Testing (Beta) — public opt-in beta
- Production — available to all users. Can do a staged rollout (e.g. 10% → 50% → 100%)
Store Listing Assets
Required assets for the Play Store:
- App icon — 512×512 PNG
- Feature graphic — 1024×500 PNG (shown in Play Store header)
- Screenshots — at least 2 phone screenshots
- Short description — up to 80 characters
- Full description — up to 4000 characters
Post-Release: Updates
Updating your app:
- Increment
versionCodeandversionName - Build a new signed AAB
- Upload to Play Console → same app → new release
- Write release notes (What's new) to inform users of changes
- Use staged rollouts for risky changes — watch crash rates before expanding
Quick Check
What happens if you forget to increment versionCode when uploading a new release?
Congratulations!
You've completed the full Android Development course! Here's what you've learned:
- Kotlin fundamentals — variables, functions, null safety, classes
- Android basics — Activities, layouts, user input, Intents
- Lists & data — RecyclerView, Collections, SharedPreferences
- Architecture — ViewModel, LiveData, Room, Coroutines, Repository
- Networking — Retrofit, Coil, error handling, and publishing
You're ready to build and ship real Android apps. Keep building!
Learn Kotlin with an AI tutor — free
Write and run real code in your browser, get instant help from a 24/7 AI tutor, and pick up where you left off on the web or in the app.
- Courses
- 36
- Lessons
- 152
Frequently Asked Questions
Is the “Publishing to Play Store” lesson free?
Yes — any 3 lessons of the Android Academy learning path, including “Publishing to Play Store”, are free to read in full here on the web. After that, CoddyKit PRO unlocks every lesson, plus interactive practice with a built-in code editor and a 24/7 AI tutor. The Android Academy course includes 6 lessons in total.
What will I learn in “Publishing to Play Store”?
Prepare your app for release. Configure build.gradle for production, sign with a keystore, build an AAB, set up Play Console, and use staged rollouts. You practise Android Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Android Academy?
No prior experience is required. Android Academy on CoddyKit is structured for beginners through advanced learners, so you can start here or from the beginning and move at your own pace. This is lesson 6 of 6.
How long does the “Publishing to Play Store” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Android Academy lesson?
Yes. Every Android Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Retrofit & REST APIs
- Loading Images with Coil
- Error Handling & UX
- Push Notifications
- WorkManager & Background Tasks
- Publishing to Play Store