Publish a Google AI Studio App to Google Play: 12 Testers

Short answer: AI Studio gets you to an internal test, not to production

Google AI Studio can publish an Android app you built from a prompt, but only to Google Play's internal testing track. Google's announcement of the feature says AI Studio "will automatically create your app record, package the bundle, and upload it to an internal testing track in Google Play Developer Console." Everything after that is ordinary Play Console work: complete your app setup, run a closed test with 12 testers opted in continuously for 14 days if your Play account is a personal one created after November 13, 2023, then apply for production access.

Below: what AI Studio's Publish button really does, why its tester list cannot become your 12, what Play Console still asks for, and the sequence from prompt to the 14-day clock. Every policy quote here was checked against Google's Play Console testing requirements, the testing track setup guide and Android Developers documentation on October 19, 2026. If you built with Lovable or Bolt.new instead, the starting point differs but this article's second half is exactly your path too.

What does Google AI Studio's Publish button actually do?

AI Studio's Build mode writes a native Kotlin and Jetpack Compose project, previews it in an in-browser emulator, installs it on a phone over USB through an integrated debug bridge, and — once a Play developer account is connected — publishes it. Google's codelab for the feature lists the steps: click Publish, choose Publish to Play Store, sign in with the Google Account that owns your Play Console account, then "Google AI Studio will automatically sign your app and publish it to the Internal Testing track." The panel then shows a shareable link and a QR code, and lets you type in the email addresses of the people you want to test.

Both official descriptions of this feature stop at the same wall. The Android Developers blog describes uploading "to an internal testing track in Google Play Developer Console" and lists managing Play test tracks from AI Studio as a future addition; Google's codelab (last revised August 21, 2026) still describes the internal testing track as the destination. There is no documented closed-testing or production publish inside AI Studio — production is an application you file in Play Console.

• A Play Console developer account. Google charges "a US$25 one-time registration fee."
• The same Google Account on both sides: the codelab's first instruction is "Make sure you are logged into Google AI Studio with the same Google Account you use for your Google Play Developer Account."
• Somewhere to send the link. Internal testing holds up to 100 testers, and they install through the Play Store like any other release.

Why the testers AI Studio invites cannot become your 12

The moment AI Studio publishes, it asks who should receive the link. That question deserves a pause, because Google has a hard rule about track membership: "A user who opts into your app's internal test is no longer eligible to receive an open or closed test. To access an open or closed test, the user must first opt out of the internal test and then opt in to the open or closed test."

Everyone you hand the AI Studio link to therefore locks themselves out of your closed test until they opt out of the internal one. Their internal-track days contribute nothing to the 14: the requirement is measured on the closed test, per tester. Google's FAQ is explicit that "Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement," and that a tester who leaves and returns only counts once the run is consecutive. Both points are Google's, stated in App testing requirements for new personal developer accounts.

This trap is specific to the AI Studio route because publishing and inviting happen on the same screen: the app lands on internal testing and the tester field is right below it. Any path that starts in Play Console makes you choose a track deliberately instead. (If your count already fell below 12 after launch, see what happens when you reach 0 testers before you restart anything.)

What Play Console still asks for after AI Studio publishes

AI Studio creates the app record and uploads a build. It does not complete your app setup, and closed testing needs that done: the testing requirements article gives closed testing the prerequisite "Complete app setup" and says "You can start a closed test after completing your app setup." Google's app dashboard documentation puts the same point in one line — "You must complete the mandatory tasks before you can launch your app on Google Play."

• App content and store listing details: category, contact details, screenshots and the rest of the information Google says "helps us to ensure that your app is safe for its intended users, is compliant with Google Play policies, and satisfies legal requirements."
• A release on a closed testing track, which the dashboard lists as "Preparing and rolling out a release to the test track."
• Testers invited "via email or Google Groups": closed testing accepts up to 200 lists, each holding up to 2,000 users, with up to 50 lists per track.
• Device verification, for new personal accounts: developers "will be required to verify that they have access to an Android device using the Play Console mobile app before they can make their app available on Google Play." We cover that step in device verification for closed testing.

One gap remains between the two systems: an internal-testing release does not hand you a bundle for the closed track. Google's documented exit from AI Studio is the ZIP export — projects "can be exported as a ZIP file and opened seamlessly in Android Studio" — and from that project Android Studio builds the signed app bundle you upload under Test and release > Testing > Closed testing > Manage track. Build it yourself or hand it to someone who does; either way it must be the same app, with the same package name and the same signing key.

How to start the 14-day clock from an AI Studio build

A sequence that keeps every AI Studio shortcut while satisfying Google's requirement. The first three steps are browser work; the rest live in Play Console.

1. Check your account, not your builder. The rule is account-based: personal accounts created after November 13, 2023 must run the closed test. Organization accounts and older personal accounts are not covered.
2. Publish from AI Studio to internal testing and install it on your own phone. Fix what breaks, invite a few trusted people if you like — just not your 12.
3. Complete app setup in Play Console until the dashboard shows the mandatory tasks finished.
4. Export the project as a ZIP, build a signed app bundle, and create a release on the closed testing track. Add a feedback email or URL; Google displays it on the opt-in page.
5. Send the closed-test opt-in link to more people than you need. Google warns that "After publishing an open, closed, or internal test for the first time, the test link can take several hours to become available to testers." Based on our analysis of 1,500+ closed-testing campaigns, recruiting 15 or 16 instead of exactly 12 is what keeps one day-nine dropout from pushing your date out — and the opt-in has to come from the tester, not from an address you typed into a list.
6. Write down the date on which the 12th tester is continuously opted in. That is day 1 of 14. Every tester runs their own clock and must stay opted in for all of it.
7. Ship at least one update during the test and keep the testers' notes. The application requires it: you must "summarize your testing feedback when applying for production access" and say "whether testers used all available app features." The exact wording the form asks for is in production access form questions.
8. Apply from the Dashboard. The form has three sections — About your closed test, About your app/game, About your production readiness. If the button never appears, Apply for production button not showing walks through why.

Which decisions in this flow can you never change?

Four of them, all locked before your first closed-test day. AI-built projects hit these faster because a prompt-driven build never had a store listing in mind.

• Package name. Google's Play Console documentation: "Package names for app files are unique and permanent, so please name them carefully. Package names can't be deleted or re-used in the future." AI Studio's first upload fixes it.
• Signing key. Google's codelab says AI Studio signs the app for you. Every later bundle must arrive signed with the key registered to that app: "You use this key to sign your app bundle before uploading it to the Play Console. Google uses it to verify your identity." If you intend to build releases in Android Studio after exporting, settle the key question before the first upload rather than after — Play Console can reset an upload key, but not without friction.
• Account type and creation date. These decide whether the 12-tester requirement applies to you at all, and nothing you do inside AI Studio changes them.
• Target API level. Google's target API level requirements: "Starting August 31, 2026: New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play." If the bundle AI Studio generates targets an older level, Play Console refuses the upload, so check the exported project before you plan a calendar around it.

How long does an AI Studio app take to reach production?

Minutes to an internal test, then the calendar takes over. For an account the 12-tester rule applies to, a realistic sequence is:

1. Build and internal publish: minutes — Google says the app "is available for you to install within minutes."
2. App setup plus the closed-track release: one to three days, mostly store listing and content rating work.
3. Recruiting 12 continuously opted-in testers: the variable, and the only part Google does not time for you. The clock starts with the twelfth opt-in, not the first install.
4. Closed test: 14 days, with no documented shortcut.
5. Production access review: "usually takes seven days or less, but can occasionally take longer."

Based on our analysis of 1,500+ closed-testing campaigns, the calendar is dominated by the required window rather than by how the binary was produced — an AI-built app and a hand-built app reach production on the same schedule once the closed test starts. Our estimate: about three weeks from the twelfth opt-in, and roughly a month from your first prompt if recruitment is starting cold.

Frequently asked questions

Does publishing from AI Studio count toward the 12 testers? No. The requirement is a closed test, and AI Studio publishes to internal testing. Google's own table gives internal testing the requirement "None" while closed testing requires completed app setup and, to reach production, "a closed test with at least 12 opted-in testers continuously for 14 days."

Can my internal testers become my 12? Only after they opt out of the internal test. Until then they are ineligible for the closed test, and the days they spent on the internal track count for nothing.

Can AI Studio publish straight to production? Not in anything Google has published. Both the Android Developers announcement and Google's August 2026 codelab describe publishing to the internal testing track. Production opens only after your production access application is approved.

Do I need Android Studio at all? For building the app, no — AI Studio does that in the browser. For the closed-track release, yes in practice: Google's documented export is a ZIP opened in Android Studio, and that project is what produces the signed app bundle Play Console expects.

Do I have to pay the $25 fee? Yes, before AI Studio can publish anything: "There is a US$25 one-time registration fee" for a Play Console developer account.

Will Google reject my app because AI wrote it? No. Authorship is not a review category. What gets judged is policy compliance, functionality and stability — the same three things applied to any other build — plus, for your application, evidence that real testers used the app.

Is this the same problem as a WebView-wrapped app? No, and that is a genuine advantage of this route. AI Studio outputs a native Kotlin and Jetpack Compose project, so the "website in an app shell" policy question that web builders raise never arises. Lovable and Bolt users have to answer it; you do not.

What to do today

1. Build the app in AI Studio and publish it to internal testing for your own device checks.
2. Start Play Console app setup in parallel — it is the prerequisite for the closed test, and it is the part nobody budgets for.
3. Write down whether your account is a personal one created after November 13, 2023; that single fact decides your whole timeline.
4. Line up 15 or 16 people for the closed test, not 12, and keep them off the internal track.

The one part of this sequence that reliably eats evenings is recruiting and holding 12 engaged testers for 14 continuous days. That is the service we run: how it works and plans and pricing.