🤖 Android from Flutter source code

How to build Android APK and AAB files from your Wrapply Flutter source code

If you purchased the complete Flutter source code, you can rebuild your Android app anytime using Flutter. This guide explains how to open the project, install dependencies, update the package name, generate APK files for testing and AAB files for Google Play publishing.

Start Android build Back to tutorials

Before you start

Android builds can be created on Windows, macOS or Linux. You need Flutter, Android Studio or Android command-line tools, and a correctly configured Android SDK.

Flutter SDK
Required to run, test and build the generated Flutter app.

Android SDK
Installed through Android Studio or standalone Android command-line tools.

VS Code or Android Studio
Use Visual Studio Code with Flutter extensions, or Android Studio if you prefer native Android tools.

Wrapply source code ZIP
Extract the generated Flutter source code before running commands.

APK files are useful for testing and direct installation. AAB files are the recommended format for Google Play publishing. For production publishing, package name, version, icons and signing configuration should be checked carefully.

Step-by-step Android build flow

Use this workflow after extracting the ZIP file containing your Wrapply Flutter source code.

Open the project in Visual Studio Code

Extract the source code ZIP and open the project root folder in VS Code. Install the Flutter and Dart extensions if they are not installed yet.

Install project dependencies

Run flutter pub get from the project root to download all required Flutter packages.

Check your Flutter setup

Run flutter doctor and fix Android SDK, licenses or device warnings before building.

Update the Android package name

Before publishing, use a unique package name such as com.yourcompany.yourapp. This identifies your app on Android and Google Play.

Test the app

Connect an Android device or start an emulator, then run flutter run to test the generated app.

Build the APK

Generate a release APK when you want an installable Android file for testing, internal distribution or direct sharing.

Build the AAB

Generate a release Android App Bundle when you want to upload the app to Google Play Console.

Basic commands:
flutter pub get
flutter doctor
flutter run
flutter build apk --release
flutter build appbundle --release

Where to change Android app settings

Most Android-specific settings are inside the android folder. The exact files may vary depending on your Flutter version and Gradle setup.

Package name
Usually configured in Android Gradle files and Android manifest references. It should be unique before publishing.

App display name
Usually configured in Android resources or manifest metadata, depending on the project structure.

App icon
Android launcher icons are stored inside the Android resources folders, usually under android/app/src/main/res.

Permissions
Add or review Android permissions inside android/app/src/main/AndroidManifest.xml.

Version code and version name
Controlled by Flutter build version values and Android Gradle configuration.

Signing configuration
Production builds require a signing key. Wrapply can generate signed builds, but custom publishing workflows may require your own key.

APK vs AAB: which one should you use?

APK and AAB files serve different purposes. Wrapply can generate both depending on your package and publishing goal.

Use APK for testing
APK files can be installed directly on Android devices and are useful for demos, validation and quick sharing.

Use AAB for Google Play
AAB files are used by Google Play Console for production distribution and optimized app delivery.

Signed APK
Required when distributing an APK outside your development environment.

Signed AAB
Required when preparing a production-ready upload for Google Play.

Common Android build issues

Most Android build problems are related to missing SDK setup, Gradle configuration, package name conflicts or signing configuration.

Android SDK not found
Install Android Studio or configure the Android SDK path correctly, then run flutter doctor.

Android licenses missing
Run flutter doctor --android-licenses and accept the required licenses.

Package name already used
Choose a unique package name before uploading to Google Play Console.

Signing error
Check your keystore, key alias, passwords and Gradle signing configuration.

Useful diagnostic commands:
flutter doctor
flutter doctor --android-licenses
flutter clean
flutter pub get
flutter build appbundle --release

Managed Android build and publishing

If you do not want to manage Flutter commands, package name configuration, signing and Play Console upload manually, Wrapply can generate signed APK and AAB files and assist with managed Google Play publishing.

Generate Android app View managed publishing

FAQ

Can I build Android apps on Windows?

Yes. Android Flutter builds can be created on Windows, macOS or Linux if Flutter and Android SDK are correctly installed.

Do I need an AAB for Google Play?

Yes, Google Play commonly requires Android App Bundle files for app publishing. APK files are better for testing and direct installation.

Are Wrapply Android builds signed?

Wrapply can generate signed APK and AAB files. If you rebuild the project independently, you may need to configure your own signing key.

Can I modify the Android app after generation?

Yes. If you have the Flutter source code, you can update UI, navigation, icons, package name, permissions and integrations before rebuilding.