How to Get an APK from Google AI Studio and Publish It to Google Play

Google AI Studio does not hand you a production-ready APK. As of mid-2026 it can build a native Android app and publish it in one click to Google Play's internal testing track — which caps out at 100 testers and is never a public listing — or install it on your own phone over USB. To actually publish, you need a signed AAB uploaded to a production track under your own developer account: if AI Studio built you a web app, wrap the deployed URL into a signed APK/AAB; if it built you a native Kotlin project, export the code and compile it from source. This guide walks through both.

What Google AI Studio actually gives you (as of mid-2026)

At I/O in May 2026, Google announced that AI Studio can build native Android apps from a prompt — real Kotlin with Jetpack Compose, with access to hardware like GPS, Bluetooth, and NFC. You can preview the app in an emulator inside your browser, install it on a physical phone over USB with the integrated adb bridge, and export the whole project as a ZIP, to GitHub, or straight into Android Studio. It is a genuinely impressive pipeline, and it is free to use.

That native mode sits next to the thing AI Studio has done for longer: building web apps — React and TypeScript projects you deploy to a URL. Depending on what you asked for and when, your project is one or the other, and the two take completely different roads to an APK. We'll sort that out in a minute.

One more piece of context, because it's why a lot of people are landing here: Google is sunsetting Firebase Studio. New signups and new workspace creation were disabled on June 22, 2026, with a full shutdown scheduled for 2027, and AI Studio is the designated successor. If you're migrating a Firebase Studio project, the same two routes below apply — we wrote a dedicated guide for Firebase Studio apps covering the migration wrinkles.

The gap: internal testing is not publishing

AI Studio's one-click publish is real, but read the fine print on what it publishes to. Google Play's internal testing track distributes your app to a hand-picked email list of up to 100 testers. It's built for QA: no store search, no public listing page, no installs from strangers. For showing an app to your team or your client, it's honestly all you need — and AI Studio automating the app record and upload is a real convenience.

A production listing is a different animal. You need a Google Play developer account (one-time $25 fee), a signed AAB — the app bundle format Play requires for new apps, signed with an upload key you must keep using for every future update — plus store listing assets, and, if your developer account is a new personal one, a closed test with real testers before Google will let you go to production (as of mid-2026 that means 12 testers over 14 days; our production-path guide walks that whole wall). AI Studio does none of that last mile. That gap — from “app that exists” to “signed AAB you can actually ship” — is the part we close.

Step 1: figure out which kind of app AI Studio built you

Open your project and look at what it produces. If the preview runs as a website and the deploy step gives you an HTTPS URL, you have a web app — take Route A. If the preview runs in an Android emulator, the code is Kotlin, and the export contains build.gradle files, you have a native Android project — take Route B. Getting this wrong wastes your time in both directions: a web app has nothing for a Gradle pipeline to compile, and a native Compose app has no URL to wrap.

Route A: AI Studio built a web app — wrap the deployed URL

A deployed web app is exactly what our core pipeline wraps. The result is a real Android application — a native shell that renders your live app full-screen, with the pieces a browser tab can't give you. The steps:

1. Deploy from AI Studio and copy the HTTPS URL where your app is live. Any deploy target works — we only need the URL, never your Google account.
2. Paste the URL into Code2Native, pick an app name and a package ID like com.yourstudio.app (choose carefully — it's permanent once published).
3. Add your icon and splash. Upload one 512×512 PNG and every density variant is generated; no logo yet gets you a clean monogram icon. If you enable the Android OneSignal integration, configure the provider and permissions and test delivery on a device.
4. Build and inspect the result. The free offer produces one marked Preview APK for compatible Android devices. Paid releases provide Release APK/AAB delivery. For an existing app, verify its package ID, increasing version code and accepted signing identity before attempting an update. Queue and dependency work affect build time.

The best property of this route: the app loads your live site, so every edit you make in AI Studio follows your deployment and cache behavior. Native-shell changes need a rebuild, and store policies still apply. The app is your web app. If it's slow or awkward in a phone browser, a native shell won't fix that; fix it in AI Studio first. And to be clear about the thing wrapper vendors tend to blur: a PWA or a bare URL is not itself something you can submit to Google Play — a new Play app normally needs a signed AAB, available through the paid release route. More on that mechanic in our website-to-Android guide.

Have a deployed URL? Preview the website layout before creating a project. A browser preview is not a real-device compatibility test.

Route B: AI Studio built native Kotlin — compile the export from source

If AI Studio gave you a Kotlin/Compose project, you're holding actual native source code, and wrapping would throw that away. Instead: export the project as a ZIP (or push to GitHub and zip that), and upload it to our source build pipeline. We compile native Android Gradle projects — exactly what AI Studio exports — on machines with the SDK, JDK, and Gradle already installed, and sign the output with a per-project release keystore. The result follows your native project and selected APK/AAB distribution settings; it is not replaced with a URL wrapper.

This source lane requires Builder or Pro and spends bundled credits; Builder permits 20 Android source builds per calendar month. It runs supported projects with managed tools but does not guarantee to repair invalid source or dependencies. Existing published apps need their accepted signing key, not a new key substituted for a missing one. Read the logs and artifact details. Platform/network faults refund credits actually charged; customer compile errors do not. Check the source input and signing requirements before uploading your export.

Scope honesty: the source pipeline builds Flutter, native Android (Gradle), and Capacitor projects that include an android/ folder. React Native, Ionic, and Expo are waitlist only — not supported source inputs today. AI Studio's Android export is a plain Gradle project, so it lands squarely on the live path.

The do-it-yourself route, honestly

You can do Route B locally for free, and Google makes it easy to start: export from AI Studio straight into Android Studio. From there you install the toolchain (plan for roughly 10 GB with the SDK and a JDK), generate a signing key with keytool, wire it into android/app/build.gradle, and run ./gradlew bundleRelease for a release AAB. Back up the keystore. If an upload key is lost, use Google's applicable Play App Signing reset process; generating another key is not an automatic replacement. If you want to learn the Android toolchain, this is a fine weekend. If you just want the app shipped, it's an afternoon you don't need to spend.

Your options, side by side

*Producing a release bundle is not production access or store approval. Complete signing, testing and review requirements separately.

Who should do what

• Demoing to teammates or a client? AI Studio's internal testing publish is genuinely enough. Don't pay us or anyone else — 100 testers covers a demo with room to spare.
• Want a real Play listing, and your project is a web app? Wrap the deployed URL. You keep AI Studio as your editor, and every redeploy updates the installed app instantly.
• Want a real Play listing, and your project is Kotlin/Compose? Upload the export to the source pipeline. You get your actual native app, compiled and signed, without installing a toolchain.
• Want to learn Android development? Go DIY through Android Studio. The export hand-off lets you inspect and maintain the native project directly.
• Coming from another AI builder? The same decision tree applies to most of them — see our guides for Glide and Firebase Studio.

FAQ