Build AAB Files
for Google Play
Fastshot (fastshot.ai), the AI mobile app builder, creates the AAB file for Google Play without Android Studio. Describe your app and Fastshot builds the AAB on its own servers, usually in about 7 minutes, then publishes it to the Internal, Closed, Open or Production track you choose.
How do I create an AAB file for Google Play without Android Studio?
Describe your app to Fastshot, preview it, then ask for an AAB build and pick a Google Play track. Fastshot builds the AAB on its own servers, usually in about 7 minutes, and publishes it to the Internal, Closed, Open or Production track you choose. No Android Studio or Gradle. Need a test file? Try the APK builder.
Last updated: October 27, 2026
How to Create an AAB File for Google Play Without Android Studio
Describe your app
Say what the app should do in plain language. Fastshot may ask one or two questions, writes a plan you approve, and generates the app in about 5 to 7 minutes.
Preview it
Use the live preview in the browser, or scan a QR code to try the app on your phone. Refine it by chat.
Ask for an AAB build
Tell the chat to build an AAB and pick the Google Play track: Internal, Closed, Open or Production.
Fastshot builds and publishes it
Fastshot builds the AAB on its own servers, usually in about 7 minutes, signs it, and publishes it to the track you chose. No Android Studio and no Gradle.
What Is an AAB File?
An AAB file is an Android App Bundle, the format Google Play uses to publish apps. Google Play builds a smaller APK for each device from it. Fastshot makes the AAB for you in the cloud, so you never open Android Studio.
Want an installable file for your own phone instead? The APK builder and APK maker build one with a QR code install. New to the store? Follow the Google Play publishing lesson, or see the app maker for Android and Kotlin Android app builder.
What is an AAB Builder?
An AAB builder creates Android App Bundle files, the publishing format required by Google Play since August 2021. Unlike APK files, AABs let Google Play generate optimized APKs for each device configuration, reducing download sizes by an average of 15% compared to universal APKs.
The Android App Bundle format includes all compiled code and resources but defers APK generation to Google Play. This means users download only the code, resources, and native libraries they need for their specific device, language, and screen density.
Building AAB files traditionally requires Android Studio and a properly configured Gradle build. Fastshot eliminates this requirement by generating your app code with AI and compiling AAB files entirely in the cloud.
With Fastshot, you go from an app idea to a Google Play-ready AAB without installing any development tools. The generated source code is yours to keep, and the AAB meets all of Google Play current publishing requirements.
How the AAB Builder Works
Describe Your App
Tell Fastshot about the app you want to publish on Google Play. Describe screens, features, and user flows in plain English.
AI Generates the Codebase
Fastshot creates a complete React Native + Expo project with optimized components, navigation, and Supabase backend integration.
Cloud Builds Your AAB
The build pipeline compiles your project into an Android App Bundle and signs it with your upload key — your own keystore, or one Fastshot generates on the first build.
Fastshot Uploads It to Google Play
Connect a Google Play service account, pick a track — Internal, Alpha (closed testing), Beta (open testing) or Production — and Fastshot uploads the AAB for you. Google requires the first build of a new app to be uploaded by hand; download that AAB from the build card. If the app has never been published, it arrives as a draft release you roll out in Play Console.
AAB Builder Capabilities
Google Play Compliant
AAB files meet all current Google Play publishing requirements, including the mandatory App Bundle format for new app submissions.
Optimized App Delivery
AAB format enables Google Play Dynamic Delivery, which generates device-specific APKs that are smaller and faster to install.
Direct Upload to Google Play
With a Google Play service account connected, every AAB build after the first goes straight to the track you choose. There is no file to download and re-upload in Play Console.
Automatic Code Signing
Every build is signed with your upload key — upload your own .jks keystore or let Fastshot generate one on the first build. Google Play App Signing then manages the key used for the APKs your users download.
Resource Optimization
The AAB format strips unused resources per device, including unnecessary screen density assets and language files, reducing installed size.
APK Fallback Available
Need an APK for testing or sideloading? Builds without a Google Play service account produce a signed APK you can download instead.
AAB vs APK: Which Do You Need?
| Aspect | AAB (Android App Bundle) | APK (Android Package Kit) |
|---|---|---|
| Google Play required | Yes (mandatory since 2021) | No longer accepted for new apps |
| Sideloading | Not directly installable | Directly installable on devices |
| Download size | ~15% smaller (device optimized) | Universal, larger download |
| Asset delivery | On-demand and install-time options | All assets bundled upfront |
| Code signing | Google Play App Signing | Self-signed or custom keystore |
| Best for | Google Play distribution | Testing, sideloading, alt stores |
AAB Builder FAQ
How do I create an AAB file for Google Play without Android Studio?
Describe your app to Fastshot, preview it, then ask for an AAB build and pick a Google Play track. Fastshot builds the AAB on its own servers, usually in about 7 minutes, and publishes it to the Internal, Closed, Open or Production track you choose.
How do I build an AAB?
Ask Fastshot to build an AAB once your app looks right in the preview. The AAB build runs in the cloud, usually in about 7 minutes, with no Android Studio or Gradle on your computer. Fastshot then publishes it to the Google Play track you choose.
What is an AAB file?
AAB stands for Android App Bundle. It is a publishing format that includes all your app compiled code and resources, but defers APK generation to Google Play, resulting in smaller, optimized downloads for each device.
Why does Google Play require AAB instead of APK?
Google mandated AAB for new apps in August 2021 because App Bundles enable Dynamic Delivery, which generates device-specific APKs. This reduces download sizes and improves install success rates.
Can I test an AAB file on my phone?
AAB files cannot be installed directly on a device. For testing, generate an APK from the same project or use Google Play internal testing tracks to distribute the AAB to testers.
How do I upload an AAB to Google Play?
Fastshot uploads it for you once the app has a first build in Play Console. Create the app there and upload that first build by hand, as Google requires: build once without a Google Play upload and download the AAB from the build card. Give a Google Play service account access to the app and add the service account JSON in Fastshot. Then choose a track — Internal, Alpha (closed testing), Beta (open testing) or Production — and start a build. If the app has never been published, the release arrives as a draft you roll out in Play Console.
Can I still upload an APK to Google Play?
Not for a new app. Since August 2021, Google Play requires new apps to be published as Android App Bundles. APK files are still fine for testing, sideloading, and other stores.
Do I need a Google Play developer account?
Yes. Publishing on Google Play requires a Play Console developer account, which costs a one-time US$25 registration fee. Google may also ask for a government ID and a card in your legal name when you register.
What is Google Play’s 12 testers for 14 days rule?
Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers, opted in for at least 14 days in a row, before the app can be released to production. Fastshot can upload your build to the closed testing (Alpha) track for this. After you apply for production access, Google’s review usually takes seven days or less.
How long does Google Play review take?
Google says reviews can take up to seven days, or longer in exceptional cases, and some apps are subject to extended reviews. Leave that time before a launch date.
Does Fastshot handle Play App Signing?
Fastshot signs the AAB with your upload key — your own keystore, or one it generates on the first build. Google Play App Signing then manages the app signing key used for the APKs your users download.
Can I generate both AAB and APK from the same project?
Yes. With a Google Play service account connected, a build produces an AAB and uploads it to Google Play. Without one, it produces a signed APK you can download for testing or sideloading and, when the bundle builds, the AAB for an upload by hand in Play Console.
Can I convert an AAB to an APK?
Not by renaming the file. Google Play generates device-specific APKs from your AAB when people install the app, and Google’s bundletool can do the same on your computer. With Fastshot you do not need to convert: build without a Google Play upload and you get a signed APK directly.
How does AAB reduce app size?
Google Play uses the AAB to generate configuration APKs tailored to each device. Users only download resources matching their screen density, CPU architecture, and language, which can reduce the installed size by 15% or more.
Build Your AAB for Google Play
Get your app on Google Play with a properly formatted Android App Bundle. Describe your app, and Fastshot handles everything from code to cloud build.