Overview
- Prepare the app (name, icon, package id, permissions)
- Create a signing key
- Configure signing in Gradle
- Build a release app bundle
- Test the release build
- Upload to Google Play Console and complete the store listing
Step 1: Application ID and Version
The application ID is the unique identity of your app, such as com.mycompany.myshop. It cannot be changed after publishing. Set it in android/app/build.gradle(.kts) under applicationId. The version lives in pubspec.yaml.
Increase the number after the + for every upload to Google Play.
Step 2: Create an Upload Keystore
Step 3: Configure Signing
Create android/key.properties (and add it to .gitignore, never commit it):
Then connect it in android/app/build.gradle(.kts) by reading the properties file and adding a signingConfigs block with a release config, and use it in buildTypes.release. The exact Gradle code depends on whether your project uses Groovy or Kotlin script, so copy it from the official guide “Build and release an Android app” on docs.flutter.dev.
Step 4: Build the Release
The bundle is created at build/app/outputs/bundle/release/app-release.aab.
Step 5: Test the Release Build
Release builds can behave differently from debug builds. Check internet access (the INTERNET permission), login, payments, deep links and anything that uses code shrinking.
Step 6: Google Play Console
- Create a developer account (one-time registration fee)
- Create the app and fill in the store listing: title, description, screenshots, icon, feature graphic
- Complete the privacy policy link and the Data safety form
- Set the content rating and target audience
- Upload the
.aabto a testing track first (internal or closed testing) - Submit to production after testing
Pre-Launch Checklist
| Item | Check |
|---|---|
| Debug banner and test data removed | Yes |
| Production API URL used | Yes |
| Firestore and API security rules locked | Yes |
| App icon, name and version set | Yes |
| Privacy policy page ready | Yes |
| Crash reporting set up (for example Firebase Crashlytics) | Yes |
--obfuscate --split-debug-info=build/symbols. Keep the symbols folder to read crash reports.
Conclusion
Publishing is mostly preparation: a unique id, a safely stored key, a signed app bundle and a complete store listing.

