Native builds overview
Build a signed APK, App Bundle or IPA from one revision, with no Xcode, Android Studio or Mac; you pay only when it succeeds.
Updated Oct 11, 2026
Pick an output
| Output | Platform | For | When it finishes |
|---|---|---|---|
| Installable APK | Android | Your phones and direct testers | QR code, Download |
| Play Store AAB | Android | Google Play | Open in Publish, download |
| IPA | iOS | TestFlight and the App Store | Open in Publish, download |
Every output is a signed release build that uses the project's one .env. The Build panel sends nothing to a store: uploads happen in Publish.
Steps
- Click Build in the project bar.
- Pick Android or iOS, then the output. Each option shows its price.
- Fix anything red in the checks above the build button.
- Start the build. You can close the panel: the project bar shows Building and a notification says when it ends.
- On Your app is ready, scan the QR code or Download an APK, or click Open in Publish for an App Bundle or IPA.
Checked before you build
The checks cover the build machine, the bundle ID or package name, signing, the version and build number, store files, secrets in the source, credits and build slots, a repeat of the same revision, and must-fix Release and Security findings. A red check keeps the button off and links to its fix. A refused build costs nothing and uses no build number.
Good to know
- The price is held while the build runs and charged only if it succeeds. Failed and canceled builds cost 0 credits.
- A build uses the revision current when it started. Later edits need a new build; building the exact same version again charges again.
- Builds take a few minutes, an iOS one often 10 to 15. The plan limits how many can be queued or running at once.
- Building needs the Build app permission. Owners, admins and developers have it.
Related
Did this page help?