Google AI Studio App to the Play Store: From Exported ZIP to Production AAB

Google AI Studio can build you a real Android app, but its one-click publish stops at Google Play's internal testing track — up to 100 invited testers, no public listing, no store search. Getting from there to an app strangers can install means a production release you create in Play Console, after a closed test if your developer account is new (12 testers, 14 days). You can send the bundle AI Studio uploaded through those tracks, or export the project and compile your own signed AAB; this guide covers both, including the upload-key step AI Studio's managed signing adds. If you just want the app on your own phone, AI Studio's Install on Device button does that over USB from Chrome or Edge; our shorter APK guide covers getting an APK file you can share.

What the one-click publish actually created

When you hit publish inside AI Studio, it automates something genuinely useful: it creates an app record in the Play Console under your developer account and uploads a build to the internal testing track. That track is built for QA: a hand-picked list of up to 100 testers, builds available within seconds, and possibly no standard policy review. Internal testing itself never becomes a public listing, no matter how long you wait, but the bundle AI Studio uploaded is not stuck there: Play Console can add it to a closed testing or production release.

The good news is that the app record it created is a perfectly normal Play Console app. You do not start over — you upload a production-grade build to that same record and follow the testing and production requirements shown there. Before rebuilding, check whether the bundle AI Studio uploaded can go forward as it is: Play Console can add it to a closed testing or production release with Add from library, if it meets current requirements such as target API 36. A bundle you build yourself must keep the package name, use a higher version code and be signed with the app's upload key; because AI Studio holds that key, request an upload key reset first.

Step 1: export the project

In your AI Studio project, download the code as a ZIP. For Android projects that is the only export today (GitHub export is not yet available for them), and it is also how you move the project into Android Studio. You get a standard Gradle project: Kotlin source, a Jetpack Compose UI with Material 3, build.gradle.kts files (Kotlin DSL) and an AndroidManifest.xml. Keep that export somewhere safe — it is your app's source of truth from here on.

One fork in the road first: if your AI Studio project is a web app (the preview runs as a website and deploys to a URL) rather than native Kotlin, the compile-from-source path below does not apply — you wrap the deployed URL instead. The APK guide's Route A covers wrapping; everything in this article from Step 3 onward still applies to the wrapped AAB identically.

Step 2: compile a signed AAB from the export

Play requires the App Bundle format for new apps — not an APK — and it must be release-signed. You have two honest options:

Locally with Android Studio (free). Install Android Studio, open the export, wait out the Gradle sync, create a keystore, and run Build → Generate Signed App Bundle. This works, and costs nothing but time and a few gigabytes of SDK. Two warnings from the trenches: guard the keystore file with your life (lose it and update continuity depends entirely on Play App Signing), and expect version friction — fresh exports regularly assume a newer or older toolchain than whatever your local machine has installed.

Cloud build (what we do). Upload the exported ZIP to the source pipeline on Builder or Pro. Source compiles spend bundled credits; Builder allows 20 Android source builds per calendar month. The managed toolchain runs your project, but does not guarantee to repair invalid source or incompatible dependencies. Read the resulting logs and artifact signing details. If you do not upload a keystore, Code2Native creates a signing key for the project and keeps it for every build; after the project's first successful Android build, changing it takes a reviewed migration. Upload a keystore you hold if you want to keep the key yourself. For an existing Play app, the build must be signed with that app's upload key. If AI Studio published the app, that is AI Studio's managed key, which you cannot supply here: create a keystore, request a Play upload key reset for its certificate, and upload that keystore to the project before you build. Platform/network failures refund credits actually charged; customer compile errors do not. Current allowances are on the pricing page. Whichever route you take, check targetSdk in app/build.gradle.kts first: since August 31, 2026, Google Play requires new apps and app updates to target API level 36 or higher, with extensions available only to November 1, 2026.

Step 3: set up the Play Console record

If AI Studio already created the app record, open it in the Play Console and work with it — do not create a duplicate. If not, create the app record yourself (the developer account is a one-time $25 if you don't have one). Either way, when you upload your first AAB Google will enroll the app in Play App Signing: Google holds the app signing key, your AAB is signed with an upload key, and Play re-signs installs. There is nothing to opt into: new apps are enrolled automatically with Google-generated keys, and if an upload key is ever lost, Google can reset it.

Fill the store listing while you are here: title, short and full description, screenshots, a 512×512 icon, a feature graphic, a privacy policy URL, content rating questionnaire, data safety form. None of it is hard; all of it must be complete before Play lets you start the closed test in Step 4.

Step 4: the closed-testing wall (12 testers, 14 days)

Here is the step that surprises almost everyone shipping their first app: if your Play developer account is a personal account created after November 13, 2023, Google will not let you near the production track until the app has run a closed test with at least 12 testers opted in continuously for the last 14 days. (It was 20 testers until December 2024, when Google cut it to 12 — plenty of older guides still say 20.) This specific gate does not cover organization accounts; other review requirements still apply.

Practical notes from watching people get stuck: each tester counts only after 14 unbroken days opted in, and one who opts out and back in starts again, so recruit a few more than 12. Google's formal requirement is opt-in, but it lists insufficient tester engagement as a reason to require more testing, so ask testers to install the app and use it. When the period completes, apply for production access from the Dashboard and describe the feedback you collected and the changes it informed. Google says review usually takes seven days or less, and it may require further testing. Recruit people from your intended audience and keep a usable feedback channel; tester counts alone do not establish that the app is ready. Code2Native does not sell a closed-testing or guaranteed-approval service in the current public offer.

Step 5: promote to production

With production access granted, upload (or promote) your AAB on the production track, finish any remaining listing checks, and submit for review. Review often takes a few days; Google says some developer accounts get a more thorough review that can take up to seven days, or longer in exceptional cases. Two things that trip up AI-built apps in review: a listing that promises more than the app does (write the description about what actually works), and apps that are effectively a single thin screen — if that is you, ship one more real feature before submitting. Wrapped web apps have their own review dynamics; our Play approval guide for WebView apps covers them.

After approval, updates are the same loop minus the walls: bump the version, rebuild the signed AAB with the same upload key, upload, roll out. This is where key continuity pays off — Play Console refuses a bundle signed with a different upload key, and fixing that takes an upload key reset.

The short version

AI Studio takes you from prompt to running app; Play takes a signed AAB that targets API 36, a $25 account, a store listing, and — for new personal accounts — 12 testers for 14 days. The gap between those two is either AI Studio's own bundle sent through Play Console's tracks, or one export and one real build. Do the build locally with Android Studio if you want the toolchain on your machine, or upload the export using the paid Builder or Pro source lane. A successfully compiled and correctly signed AAB is one input to submission, not proof of store acceptance. The free Preview offer applies to URL wrapping only.