How to Build and Download Your App

Once your app configuration is saved, building it takes a few clicks. This article walks through the build process from start to download.

Selecting a Build Tier

From your app's dashboard page, click Build App. You'll be presented with the three build tier options:

• Debug (10 credits): Unsigned APK for device testing
• Starter (50 credits): Signed AAB with branding, ready for Google Play
• Professional (100 credits): Starter + push notifications, AdMob, file upload/download

Your current credit balance is displayed alongside each option. If you don't have enough credits for the selected tier, you'll be prompted to purchase a credit pack before the build can proceed.

Build Confirmation

Before the build starts, a confirmation screen shows:

• The build tier and credit cost
• Your remaining credits after the build
• The app configuration that will be used (version, settings summary)

Confirm to place the build in the queue. Credits are deducted immediately when the build is confirmed.

Build Queue and Status

Your build enters a queue. Build time depends on queue depth and tier:

• Debug: typically 2–5 minutes
• Starter: typically 3–7 minutes
• Professional: typically 5–10 minutes

Build status is displayed on your app's Build History page:

• Queued: Waiting for a build server to pick up your job
• Building: The build server is actively processing your configuration
• Completed: Build succeeded: download link available
• Failed: Build encountered an error: see the error log

You'll receive an email notification when the build completes or fails. You don't need to keep the dashboard open while waiting.

Downloading Your Build

When the build completes, click Download on the build history row. The download is a direct file download:

• Debug: [app-name]-debug.apk
• Starter / Professional: [app-name]-release.aab

Download links are available for:

• 7 days on free accounts
• 30 days on paid accounts
• Indefinitely on subscribed accounts

After the retention window expires, the build artifact is deleted from storage. If you need the file after expiration, you'll need to run a new build. This is why it's important to keep your AAB file stored safely locally or in cloud storage.

Installing a Debug APK

To install a debug APK on your Android device:

1. Transfer the .apk file to your device (email it, use Google Drive, or transfer via USB)
2. On the device, open the Files app and navigate to the APK
3. Tap the APK file to install it
4. If prompted about "Install unknown apps," grant permission for the source you used to transfer the file
5. Complete the installation and open the app

Debug APKs are for testing only. They're not suitable for distributing to users due to the debug signing key and missing optimizations. For production distribution, always use the signed AAB through Google Play Console.

Build Failures

If a build fails, the error log is available by clicking View Log on the failed build row. Common failure reasons:

• Invalid google-services.json: The Firebase configuration file is malformed or doesn't match the package name
• Icon file format error: The uploaded icon is not a valid PNG or is too small
• Keystore password incorrect: If uploading your own keystore, verify the key alias and passwords
• Package name conflict: A configuration issue with the package name format

If the error log doesn't clarify the issue, contact support with the build ID shown in the log.