Build and Publish Your Android App

Google Flutter 12 min min read Updated: Nov 16, 2026 Intermediate
Build and Publish Your Android App
Intermediate Topic 4 of 5

Overview

  1. Prepare the app (name, icon, package id, permissions)
  2. Create a signing key
  3. Configure signing in Gradle
  4. Build a release app bundle
  5. Test the release build
  6. Upload to Google Play Console and complete the store listing
Do not skip: Keep your keystore file and its passwords safe and backed up. If you lose them, you cannot update your published app with the same key setup.

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.

yaml version: 1.0.0+1 # versionName 1.0.0, versionCode 1

Increase the number after the + for every upload to Google Play.

Step 2: Create an Upload Keystore

bash keytool -genkey -v -keystore ~/upload-keystore.jks -storetype JKS \ -keyalg RSA -keysize 2048 -validity 10000 -alias upload

Step 3: Configure Signing

Create android/key.properties (and add it to .gitignore, never commit it):

text storePassword=your-store-password keyPassword=your-key-password keyAlias=upload storeFile=/Users/you/upload-keystore.jks

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

bash # Recommended for Google Play flutter build appbundle --release # APK file for direct sharing or testing flutter build apk --release flutter build apk --split-per-abi

The bundle is created at build/app/outputs/bundle/release/app-release.aab.

Step 5: Test the Release Build

bash flutter run --release

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 .aab to a testing track first (internal or closed testing)
  • Submit to production after testing
Current rules: Google Play requirements, such as testing requirements for new personal accounts and target API levels, change regularly. Read the current Play Console help pages before you publish.

Pre-Launch Checklist

ItemCheck
Debug banner and test data removedYes
Production API URL usedYes
Firestore and API security rules lockedYes
App icon, name and version setYes
Privacy policy page readyYes
Crash reporting set up (for example Firebase Crashlytics)Yes
Obfuscation: To make reverse engineering harder and reduce size, you can build with --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.

Quick Summary: Create a keystore, configure signing, run flutter build appbundle and upload the AAB to Google Play Console.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators