Build Android and iOS Apps from Flutter Source Code

What you need before building

Before creating Android or iOS builds, make sure your development environment is ready and that you understand the difference between Android and iOS requirements.

Wrapply Flutter source code
Extract the ZIP file generated by Wrapply. This is the full project you will open, modify and rebuild.

Flutter SDK
Required for both Android and iOS builds. You should be able to run flutter doctor.

VS Code or Android Studio
Use Visual Studio Code with Flutter and Dart extensions, or Android Studio if you prefer.

Android SDK
Required to build APK and AAB files for Android.

macOS and Xcode for iOS
Required for iOS builds. IPA files cannot be built directly from Windows without a remote Mac or managed build service.

Apple Developer account
Required for TestFlight, App Store distribution and production iOS signing.

Android builds can be created on Windows, macOS or Linux. iOS builds require macOS and Xcode because Apple signing and IPA generation are handled through Apple tools.

Complete build flow from source code

This is the recommended order when you receive the full Flutter source code from Wrapply.

Extract the source code ZIP

Download the ZIP provided by Wrapply and extract it into a clean folder. Avoid editing files directly inside the ZIP archive.

Open the project in VS Code

Open the root folder of the Flutter project. You should see files like pubspec.yaml, lib, android and ios.

Install Flutter dependencies

Run flutter pub get from the project root. This downloads all packages required by the generated app.

Check your environment

Run flutter doctor. Fix Android SDK, licenses, Xcode or CocoaPods issues before creating production builds.

Run the app locally

Start an Android emulator, connect a device or use an iOS simulator on Mac, then run flutter run.

Customize app settings

Update app name, icon, splash screen, website URL, navigation labels, package name and iOS bundle identifier before publishing.

Build Android files

Generate an APK for direct installation/testing and an AAB for Google Play publishing.

Build iOS files

On macOS, configure signing in Xcode and generate an iOS build or IPA for Apple distribution workflows.

First commands to run:
flutter pub get
flutter doctor
flutter run
flutter clean
flutter pub get

Project structure: where to find the important files

A Wrapply source code package is a standard Flutter project. These are the folders and files you will usually edit first.

lib/
Main Flutter code. This is where app UI, WebView behavior, navigation and app logic usually live.

pubspec.yaml
Project configuration, dependencies, assets and app version.

assets/
Images, icons, splash resources or other static files used by the app.

android/
Android native configuration, manifest, Gradle files, permissions and signing setup.

ios/
iOS native configuration, Xcode Runner project, Info.plist, signing and iOS assets.

build/
Generated output folder created after build commands. You normally do not edit this manually.

Before publishing: essential customization checklist

Before creating production builds, review these app identity and branding settings.

App display name
The name shown under the app icon on the device and in app metadata.

Android package name
Unique Android identifier such as com.company.appname. Required before Google Play publishing.

iOS bundle identifier
Unique iOS identifier such as com.company.appname. Required for Apple signing and App Store Connect.

App icon
Replace default assets with your final brand icon before building store versions.

Splash screen
Check the launch screen and app loading experience.

Version and build number
Update version values before uploading new releases.

Permissions
Review Android manifest permissions and iOS Info.plist usage descriptions.

Website URL and navigation
Confirm the main website URL, AppBar, BottomNavigationBar and external link behavior.

Build Android APK and AAB

Android builds are the easiest production files to generate from Flutter source code. APK is useful for testing and direct installation. AAB is used for Google Play publishing.

Prepare Android environment

Install Android Studio or Android SDK tools, accept Android licenses and confirm that flutter doctor shows no blocking Android errors.

Check package name

Make sure your Android package name is unique before building a production version or uploading to Google Play.

Build APK

Use APK when you want to install the app directly on Android devices for testing, demos or internal distribution.

Build AAB

Use AAB when you want to upload the app to Google Play Console.

Android commands:
flutter doctor --android-licenses
flutter clean
flutter pub get
flutter build apk --release
flutter build appbundle --release

Output examples: APK files are usually generated under build/app/outputs/flutter-apk/. AAB files are usually generated under build/app/outputs/bundle/release/.

Build iOS app and IPA

iOS builds require macOS, Xcode and Apple signing. If you want to distribute through TestFlight or App Store, you also need an Apple Developer account.

Open the iOS project

Open ios/Runner.xcworkspace in Xcode. Do not open only the .xcodeproj file.

Set Bundle Identifier

In Xcode, set a unique bundle identifier such as com.company.appname.

Configure signing

Select your Apple Developer Team in Xcode and enable automatic signing when possible.

Install CocoaPods dependencies

If needed, run pod install inside the ios folder.

Build iOS release

Build from Flutter or archive from Xcode depending on your distribution workflow.

iOS commands:
flutter doctor
cd ios
pod install
cd ..
flutter build ios --release
flutter build ipa --release

IPA generation depends on Apple signing, provisioning profiles and App Store Connect configuration. Wrapply can assist with iOS builds and managed publishing when you prefer not to handle this manually.

APK vs AAB vs IPA: what each file is for

Each build file has a different use. Choosing the correct one depends on how you want to distribute the app.

APK

Android install file

Best for direct installation, testing, internal sharing and demos.

AAB

Google Play file

Best for publishing Android apps through Google Play Console.

IPA

iOS app archive

Used in Apple distribution workflows with certificates and provisioning profiles.

SRC

Flutter source

Best for ownership, customization, integrations and long-term control.

Common problems and quick fixes

Most build problems come from missing dependencies, SDK setup, signing configuration or incorrect identifiers.

Flutter packages missing
Run flutter pub get from the project root.

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

Android SDK not found
Install Android Studio or configure your Android SDK path correctly.

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

iOS signing error
Check Apple Developer Team, Bundle Identifier and provisioning profiles in Xcode.

CocoaPods error
Run cd ios, then pod install, then build again.

Useful reset commands:
flutter clean
flutter pub get
flutter doctor
cd ios && pod install && cd ..

When to use Wrapply managed publishing

You can build from source code independently, but store publishing can become complex when signing, policies, certificates, App Store Connect or Google Play Console setup are involved.

Use self-build
Best when you are comfortable with Flutter, Xcode, Android SDK and store dashboards.

Use managed publishing
Best when you want Wrapply to help prepare builds, review configuration and support the publishing workflow.

Generate your app View managed publishing

FAQ

Can I build Android and iOS from the same source code?

Yes. Flutter uses one shared codebase for Android and iOS, with platform-specific configuration inside the android and ios folders.

Can I build Android on Windows?

Yes. Android APK and AAB files can be built on Windows, macOS or Linux if Flutter and Android SDK are configured.

Can I build iOS on Windows?

No. iOS builds require macOS and Xcode. You need a Mac, a remote Mac build workflow or managed iOS support.

Do I need to change package name and bundle identifier?

For production publishing, yes. Your Android package name and iOS bundle identifier should be unique and connected to your brand or company.

Can Wrapply build the files for me?

Yes. Wrapply can generate signed Android builds, prepare iOS builds on request and offer managed publishing support.

How to create Android and iOS apps from your Wrapply Flutter source code