Google AI Studio App Builder: Android Apps and Play Rules

Google AI Studio turns a written description into a real, native Android app: Kotlin and Jetpack Compose code, generated in your browser, previewable in an in-browser emulator, installable on your own phone over USB. It costs nothing to start, and it is the fastest route yet from "I have an idea" to "there is an app on my phone." What it does not do is put that app in the public Play catalog on its own. AI Studio's own publish button stops at Google Play's internal testing track, and Google's documentation says so explicitly: "Publishing is limited to the internal testing track only. Production releases must be managed directly in the Google Play Console."

So the honest answer to "can I publish my AI Studio app to Google Play?" is: yes, and the path depends on what you want. Three routes exist today, with different requirements and different walls. This article maps all three, then covers the checks an AI-built app passes automatically, the ones it still fails, and what changes when you decide to go public.

What Google AI Studio's app builder actually generates

AI Studio's Build mode writes a native Android project, not a web page in a shell. Google's own documentation describes the output: "the Antigravity Agent generates a complete Kotlin and Jetpack Compose project." From the browser you can preview the app in a browser-based Android emulator, install it on a physical device over USB through the integrated Android Debug Bridge, and hand the whole project off to Android Studio as a ZIP download or a GitHub export when you outgrow the browser.

Three properties of that output matter for everything below:

• It is native code. Kotlin, Jetpack Compose, Material 3, Jetpack libraries. No WebView, no React Native bridge, no Capacitor wrapper. That distinction disappears for most Play requirements, but it decides a couple of the automatic passes in the technical checks section.
• It is client-side only. Google's documentation states the limitation plainly: "Android apps in AI Studio are client-side only. Features that require a server-side runtime, such as Google Workspace APIs, secrets management, and multiplayer, are available for web apps only." Backend work goes through Firebase (Firestore, Firebase Authentication, Gemini via Firebase AI Logic), which the agent can wire up for you, or through your own external API.
• It is a starting point, not a finished product. The generated project compiles and follows Google's recommended patterns. Whether it survives contact with your first real testers is a different question, and it is the question the closed test exists to answer.

AI Studio is free to start with; usage sits under Google's AI Studio quota and billing terms, which change more often than this article does, so check the current terms before you plan a large build around it.

Three ways to get your AI Studio app onto an Android phone

Only the third route involves the 12-tester requirement, and that is the single most useful fact on this page. The two earlier routes install software on devices; they do not distribute an app on Google Play.

Route 1: install it on your own phone over USB

The shortest loop in mobile development right now. Build in the browser, connect the phone, install through the integrated Debug Bridge, use the app, go back to the prompt, change it, reinstall. No developer account, no store, no review. This is the route to use while the app is still an argument with yourself about whether it is worth publishing at all.

Route 2: launch it as a private personal app through Google Play

On 13 October 2026 Google opened a new channel that most developers still have not heard of. From the announcement: "Using Google AI Studio, you can vibe code a custom Android app. Since many of these apps start out as personal projects, through Google Play you can now launch these personal apps on your own device. This means your creations stay private, secure, and separate from the public store catalog. You only need your standard Google account to do so, no developer account required."

Read the conditions carefully. The rollout "starts rolling out today to select markets, including the U.S., for users 18 and over." The app never appears in Play's public catalog or search. Google says that "in the coming months, you'll be able to share your personal apps with a close circle of friends and family," and that when you are ready for real distribution, Play "helps you graduate to a professional developer account," at which point "your app will go through the same Trust & Safety reviews and quality standards as every professional developer."

The private channel is genuinely useful, and it is not a way around the publishing requirements. It is a different product: software that lives on your device. The moment you want strangers to be able to find and install your app, you are in the normal pipeline, developer account and closed test included. One practical consequence we see in our own campaign records: a private personal app cannot collect public ratings or reviews, so it contributes nothing to the store presence you will need later, and it has no bearing on a production access decision. (Our own observation from 1,500+ closed-testing campaigns, not a Google statement.)

Route 3: publish to the internal testing track, then work toward production

Connect your Play developer account in AI Studio, click Publish, choose Publish to Play Store. Google's AI Studio documentation describes what happens next: "AI Studio signs the APK, creates the app listing (or uploads a new version), and publishes to the internal testing track. You receive a link to share with your testers." The internal track holds up to 100 invited testers and never appears publicly.

Two things follow that most first-time publishers get wrong. First, the internal track is not the closed test. Internal testing has no access requirement in Google's testing table, and days spent there buy feedback, not calendar time toward production. Second, going from internal testing to a public listing is not a button; it is an application, reviewed by Google, with its own requirements. That is the subject of the next two sections.

Does the 12-tester requirement apply to an AI-built app?

Yes, if you want a public listing and your Play Console account is a personal account created after 13 November 2023. Google's Play Console Help states the rule in one sentence: "Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days. When you meet these criteria, you can apply for production access on the Dashboard in Play Console to distribute your app on Google Play."

The rule reads the same for a Kotlin project written by hand, a Lovable or Replit web app wrapped for Android, and an app that fell out of a prompt in AI Studio. It was written about accounts, not about code. We have run more than 1,500 closed-testing campaigns, and the toolchain has never once been a variable the Play Console asks about; what decides whether a fortnight goes smoothly is the same for every build: the right testing track, a current target API level, testers who stay opted in, and an app worth opening twice. (That last set of observations is ours, drawn from our own campaign records.)

The details that trip up AI-built apps specifically are covered in Do I Still Need 12 Testers If My App Was Built With AI?, and the mechanics of the window itself in Google Play 14-Day Closed Testing: What Resets.

Technical checks an AI Studio build passes, and ones it still fails

AI-built apps do not get rejected for being AI-built. They get rejected for the same checklist as everything else, and several rows of that checklist are already handled by what the generator produces, while others nobody has touched for you.

Already handled by the generated project

• Target API level. Since 31 August 2026, Google requires that "new apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play," with an extension available to 1 November 2026. A project generated today targets the current API level. If you hand off to Android Studio and freeze it there for a year, you own that problem later; our target API 36 guide covers the dates and the extension form.
• 16 KB memory page sizes. Google's technical quality requirements say apps "that contain native code must support devices with 16 KB memory page sizes," and add the sentence that matters here: "Java/Kotlin only apps are compatible by default." An AI Studio project with no bundled native libraries clears this requirement by default. The details of when it does not are in App Must Support 16 KB Memory Page Sizes.
• App Bundle format. Play requires new apps to be published as an Android App Bundle; AI Studio packages the bundle for you. If the terminology is new, What Is an AAB File? explains it in one read.

Still your job before you apply for production

• App setup completeness. Store listing, content rating questionnaire, Data Safety declaration, privacy policy, account and app access declarations. Google requires all of it before a production access application, and the agent does not file it for you. The Data Safety form walkthrough is the one developers underestimate most.
• Policy compliance of the actual content. Google's guidance is blunt: "It is your responsibility to ensure your app is fully compliant with all Google Play Developer Content Policies before submitting it for production access," and "review is not a troubleshooting step." Generated apps fail on ordinary grounds: broken sign-in after a password reset, permission requests for features that do not exist, a privacy policy URL that 404s.
• A reason for testers to open the app twice. "Insufficient tester engagement" is one of the two documented reasons Google gives for sending an application back for more testing. A scaffold app that does one demo trick will not survive a fortnight of real testers, however clean its Compose code is.

What to do before you start the 14-day clock

1. Decide your route. Private personal app while you iterate; developer account and internal track when you want testers beyond your own pocket; closed test when you are ready to talk about production.
2. Create the developer account early if public distribution is the goal. Identity verification is the slow variable, and it blocks everything after it. How to create the account and what the $25 covers are separate, short reads.
3. Finish app setup completely before the first tester arrives. Listing, ratings, Data Safety, privacy policy. The clock only helps you if the application can actually be filed when it expires.
4. Upload to the closed testing track, not internal. The 14-day window runs on the closed test. See Does Internal Testing Count for Production Access? for why the distinction is expensive.
5. Get 12 testers who will actually open the app. Opted in continuously for 14 days, on real devices. If your personal network cannot carry that, How to Get 12 Testers lists the realistic options and their failure modes.
6. Answer the production access form in writing. The application asks how testers used your app and what changed as a result. Our production access questions guide maps every field to Google's own instructions.

Expect review of that application to take, in Google's words, "seven days or less, but can occasionally take longer." Beyond that, our closed testing overview ties the whole sequence together.

Frequently asked questions

Is Google AI Studio's app builder free?

Free to start. You can build, preview in the browser emulator, and install on your own device without paying for AI Studio itself; usage is governed by Google's AI Studio quota and billing terms, which you should check for anything beyond small projects. The other costs in this pipeline are fixed and external: $25 once for a Play developer account, and whatever you spend on testers.

Can I publish an AI Studio app to Google Play without a developer account?

Not as a public app. Since 13 October 2026 you can launch it as a private personal app through Google Play with only a standard Google account, 18 and over in supported markets including the US, but that app stays out of the public catalog and search. Anything public requires a developer account.

What does AI Studio's Publish button do?

It signs the build, creates the app listing, and uploads it to your Play Console internal testing track, with a shareable link for invited testers. Google's documentation is explicit that "publishing is limited to the internal testing track only. Production releases must be managed directly in the Google Play Console."

Does an AI-built app skip the 12 testers and 14 days?

No. The requirement attaches to your developer account, not to how the app was written. A personal Play Console account created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access, and Google's wording never mentions AI, prompt engineering, or any builder tool.

Do AI Studio apps need to support 16 KB page sizes?

They are compatible by default. Google's technical quality requirements state that apps containing native code must support 16 KB page sizes, and that "Java/Kotlin only apps are compatible by default." An AI Studio project with no bundled native libraries falls in that default case.

Can testers see an AI Studio app on Google Play?

Only invited testers on the internal testing track can see and install it before launch; it does not appear in public Play search or listings. Testers who cannot find the app after being invited is a common closed-testing problem with its own fix list, in Testers See "App Not Available".

Will my private personal app show up in Ask Play or Play search?

No. Google says personal apps stay "private, secure, and separate from the public store catalog," which is also why they cannot build you store presence, ratings, or recommendations while they stay private. When you graduate to a professional developer account, the app goes through the same reviews and quality standards as any other developer's.

Sources

• Build Android apps in Google AI Studio, Google AI for Developers, page last updated 20 October 2026. Kotlin and Jetpack Compose output, client-side only limitation, internal testing track publish flow, APK signing.
• App testing requirements for new personal developer accounts, Play Console Help. The 12-tester, 14-day requirement; policy compliance responsibility; production access review timing.
• New on Google Play: more ways to create, discover, and play, blog.google, 13 October 2026. The personal app channel: private, standard Google account, 18+, select markets including the US, graduation to a professional developer account.
• Build native Android apps in Google AI Studio, Android Developers Blog, May 2026. App record creation, bundle packaging, internal testing track upload, Android Studio handoff.
• Target API level requirements for Google Play apps, Play Console Help. API 36 required from 31 August 2026 for new apps and updates; extension to 1 November 2026.
• Play Console technical quality requirements, Play Console Help. 16 KB memory page size support for apps with native code; Java/Kotlin-only apps compatible by default.
• Publish your app, Play Console Help. Review times of up to seven days or longer in exceptional cases; standard and managed publishing.
• Set up an open, closed, or internal test, Play Console Help. The three testing tracks, what each is for, and how testers opt in to a closed test.
• Prepare your app for review, Play Console Help. The policy-compliance expectations Google places on the developer before production access, quoted in this article.

Every Google and developer.android.com link above was opened and the quoted wording checked on 24 October 2026. The AI Studio documentation page carried a last-updated stamp of 20 October 2026 at the time of writing. The personal app channel described in this article was announced on 13 October 2026 and is rolling out over time, so availability in any given market should be confirmed against the announcement before you rely on it.