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 takes four concrete steps: export the project, compile it into a signed AAB, pass Play's closed-testing requirement if your developer account is new (12 testers, 14 days), and promote to production. This guide walks the whole road. If you just want an APK on your own phone, our shorter APK guide covers that; this one is about a real store listing.

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 email list, instant availability, no review. It is also a dead end for distribution: internal testing never becomes a public listing, no matter how long you wait.

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 walk it up the track ladder: closed testing → production. The thing you cannot reuse is the build itself, because production requires an Android App Bundle signed with an upload key you control and keep.

Step 1: export the project

In your AI Studio project, export the code — as a ZIP download, to a GitHub repository, or into Android Studio. For the native Android mode you get a complete Gradle project: Kotlin source, Jetpack Compose UI, build.gradle files, 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 and it compiles on machines with the SDK, JDK and Gradle already matched — and repairs the toolchain problems we see most in fresh exports before they kill the build: a missing Gradle wrapper is regenerated, Android Gradle Plugin and Kotlin versions below the toolchain floor are raised, plugin modules that demand compileSdk 36 get it, desugaring is enabled when a library requires it. Each of those is a named, classified repair in the pipeline, not a hopeful retry. You get back a signed AAB for the Play Console plus a signed APK for direct installs, under a per-project upload key that stays stable across every rebuild — which is exactly the key continuity Play's update model assumes. Failed builds refund their credit automatically.

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. Accept it — it is mandatory for new apps and it is also what saves you if an upload key is ever lost.

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 is required before production review.

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.) Organization accounts skip this entirely.

Practical notes from watching people get stuck: the 14 days count only while testers remain opted in, so a tester who drops out resets your math — recruit a few more than 12. Testers must actually install and keep the app. When the period completes, you apply for production access in the console and answer questions about your testing; Google reviews the answers, and a rejected application means more testing, not an appeal. If rounding up a dozen strangers is your blocker, we run a $249 closed-testing add-on with real testers for exactly this wall — and since you will likely want to push fixes during the window, per-build pricing means an update build is a credit, not a renegotiation.

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. First submissions typically clear in a few days. 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 — a rebuild under a different key would be rejected as a different app.

The short version

AI Studio takes you from prompt to running app; Play takes a signed AAB, a $25 account, a store listing, and — for new personal accounts — 12 testers for 14 days. The gap between those two is one export and one real build. Do it locally with Android Studio if you want the toolchain on your machine, or upload the export and let the pipeline compile, repair and sign it — first build free, and the AAB it hands back is the file the Play Console is asking for.