Flutter and Android.
Compiled from your source.
Bring a complete ZIP or Git project. Builder and Pro provide the paid source-build workflow; you get the build result, logs, and available Android artifacts. Your code still needs to be buildable.
Free is one marked Preview Android APK of a live website. An App license is for that website's release wrap, not a source-build subscription. Check current credits and plan limits before submitting.
What can I upload?
Flutter
The application root with pubspec.yaml, source, assets, and local dependencies. Keep android/ when it contains custom native work.
Native Android
A complete Gradle project: settings, build files, application module, and the full Gradle wrapper when provided.
Capacitor, React Native, Ionic, and Expo source builds are waitlist only. iOS/macOS source uploads are disabled; the current iOS workflow builds a server-generated website wrapper. Windows also wraps a URL; it does not compile an uploaded source project.
From project to a testable artifact.
Standard projects use detected defaults. Custom modules, flavors, and output paths may need explicit configuration. Read the source build guide first.
Prepare the input
Upload a project ZIP or provide an accessible Git clone URL. Include the files required to reproduce the app; exclude caches and private credentials.
Review and compile
Choose Android and the distribution target. Confirm the displayed cost, then watch the actual build logs. Duration depends on the queue and your project.
Inspect the artifacts
Check APK/AAB output, package identity, version, and signing metadata. Test installation and updates before distribution; a build is not store approval.
Choose the workflow you need.
Build locally
Keep your existing toolchain if it works. Android Studio is not strictly required for a command-line build, but the SDK and compatible tools are. Our Flutter CLI and cloud guide explains both routes.
Use a self-service build
Code2Native fits a supported Android project when you want a build attempt and inspectable artifacts without maintaining the build machine. You retain responsibility for application code, testing, and publishing.
Configure a broader CI pipeline
For automated tests, repository triggers, and coordinated releases, compare documented CI workflows. For example, Codemagic supports a Flutter workflow editor as well as YAML. Compare the same scope, not unsupported setup-time or price claims.
A failure should be diagnosable.
Inspect the command, toolchain, and first actionable error. Logged compatibility adjustments can help some projects; they do not replace missing source or guarantee a successful compile. Platform faults refund credits. Customer compile errors do not.
A download needs verification.
An APK can be installable without meeting your production signing requirements. Check the signer, application ID, and update compatibility, then follow the Android build guide. AAB output is not Google Play approval.