Google AI Studio can turn a prompt into a native Android app, and its Publish button sends that app to Google Play in a few clicks. But the button only reaches Play's internal testing track. Getting a public store listing on a new personal developer account takes a closed test with at least 12 testers for 14 days and an application for production access, and those steps live on separate Play Console help pages. This guide puts the whole path in one place: what changed in 2026, which of the four paths fits your app, a checklist before you publish, the closed test, how to find testers who stay, what to write in the production application and what it costs in money and days. It is useful without a Soloop account.
The short answer
If the app is only for you, install it from Google Play as a private personal app with your normal Google account; it is free and needs no developer account. To let other people install it, register a Google Play developer account for a one-time US$25, sign in to AI Studio with the same Google account and use Settings → Publish → Publish to Play Store, which uploads the app to the internal testing track for up to 100 testers.
For a public listing on a personal developer account created after November 13, 2023, add the same app bundle to a closed test in Play Console, keep at least 12 testers opted in for 14 days in a row, then apply for production access. Google says it usually reviews that application within seven days.
What changed in 2026
On May 19, 2026, Google added an Android option to AI Studio's Build mode. It generates a Kotlin and Jetpack Compose project from a prompt, runs it in an emulator in the browser, installs it on a phone over USB and publishes it to Google Play's internal testing track. On October 13, 2026, Google Play added a second route: a standard Google account can now install an AI Studio app privately from Play, without a developer account, in select markets including the U.S. for people 18 and over.
The personal route is private. Google says sharing personal apps with a close circle of friends and family is coming "in the coming months", and that moving to a professional account brings the same Trust & Safety reviews as any developer. Some coverage has described the October change as free publishing to the Play Store; it is not a public listing.
Generates a native Kotlin app from a prompt, previews it in a browser emulator, installs it over USB and publishes to an internal testing track with a Google Play developer account; managing test tracks and inviting testers from AI Studio were listed as coming soon.
Android Developers Blog, May 19, 2026AI Studio apps can be installed from Google Play with a standard Google account and no developer account; they stay private and separate from the public catalog; rolling out to select markets including the U.S. for users 18 and over; sharing with friends and family is planned.
Google Play: October 2026 updatesChoose your path
The four routes differ in who can install the app, what you pay and how long it takes. Most people start with the second and move down the table as the app proves useful.
| Dimension | Who can install it | What you need, review and time |
|---|---|---|
| Personal app | Only you. | A standard Google account, age 18+, in a supported market. Free, not reviewed by Google Play. |
| Internal testing (AI Studio Publish) | Up to 100 testers you add by email. | A Play developer account (US$25 once) with a completed profile, signed in to AI Studio with the same account. Testers get it within minutes. |
| Closed testing | Testers on your email lists or Google Groups who opt in with a link. | A closed testing release created in Play Console. On a new personal account it must run 14 days with 12 opted-in testers. |
| Production | Anyone on Google Play. | Production access, which new personal accounts apply for after the closed test; Google usually reviews the application within 7 days, then the app follows Play's normal review. |
Before you publish
Most delays come from the account, not the app. Google's codelab says account setup can take from 10 minutes to a few days because of identity checks, so start it before the app is finished.
- Register a Google Play developer account with the same Google account you use in AI Studio, and choose personal or organization deliberately: personal accounts need the closed test and device verification.
- Have a government ID and a credit or debit card in your legal name; prepaid cards are not accepted.
- Verify your phone number and email, and verify access to an Android device with the Play Console mobile app.
- Complete the developer profile in Play Console; AI Studio cannot publish until it is done.
- Test the app on a real phone over USB: the browser emulator has no camera, NFC, Bluetooth, real GPS or Play services such as Google Sign-In and Maps.
- If the app calls Gemini, use the Firebase AI Logic setup AI Studio provides, so no raw API key ships inside the app, and remember that every user's calls count toward your usage limits.
- Write down the one job the app does and who it is for; you will need it for the tester invitation and the production application.
One-time US$25 registration fee; personal accounts must complete app testing and verify device access with the Play Console app; a government ID and a card in your legal name may be required; you must be 18 or older.
Play Console Help: Get startedSign in to AI Studio with the same Google account as your Play developer account; identity verification with a government-issued document and phone and email verification; account setup takes 10 minutes to a few days.
Google codelab: Build and publish your first Android appFirebase AI Logic lets the app call Gemini without embedding raw API keys; App Check verifies requests; API calls count toward your usage limits and paid models may cost.
Google AI Studio docs: Android and Build modePublish from AI Studio to internal testing
AI Studio handles the packaging. It signs the app with a keystore it manages, creates the Play listing on the first publish and uploads a new version on later ones.
- In AI Studio, open the app and go to Settings → Publish, then choose Publish to Play Store.
- Authenticate with your Google Play developer account and follow the onscreen steps.
- Add your testers' email addresses. AI Studio gives you a link and a QR code to share.
- Install from the link yourself first and check the core action works on a real phone.
- When you change the app, publish again; testers receive the update through Google Play.
Settings → Publish → Publish to Play Store; authenticate with the Play developer account; AI Studio creates the listing or uploads a new version, signs with a managed keystore and publishes to the internal testing track only, for up to 100 testers.
Google AI Studio docs: Build Android appsRun the closed test
Internal testing does not count toward production access on a new personal account. Google requires a closed test with at least 12 testers who stay opted in continuously for at least 14 days. A tester who joins, tests for fewer than 14 days and leaves does not count, and someone who leaves and rejoins starts their 14 days again.
AI Studio does not create closed tests yet, so this part happens in Play Console, reusing the bundle AI Studio already uploaded.
- In Play Console, select the app and finish any setup tasks the Dashboard still lists; until then, release creation stays disabled.
- Go to Test and release → Testing → Closed testing and create a track.
- Create a new release and choose Add from library to reuse the app bundle AI Studio uploaded, then add release notes and save.
- Add testers as an email list or a Google Group, and set a feedback email or URL.
- Send the release for review if Play Console asks, and share the opt-in link once the release shows as published; each tester must open it and opt in.
- Count opted-in testers every few days and keep the test running until 12 or more have stayed for 14 consecutive days.
Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for at least 14 days before applying for production; testers who opt out before 14 days do not count.
Play Console Help: Testing requirements for new personal accountsClosed tests use email lists of up to 2,000 users or Google Groups; testers opt in with a link shown once the app is published; you can provide a feedback URL or email; testers cannot leave public reviews.
Play Console Help: Set up an open, closed, or internal testCreate a closed track and a new release under Test and release → Testing → Closed testing; Add from library reuses a previously uploaded bundle; outstanding Dashboard tasks disable release creation.
Play Console Help: Prepare and roll out a releaseFind 12 testers who will actually stay
The production application asks how easy testers were to recruit, whether they used the app's features and what feedback you collected, and Google may ask you to keep testing if engagement was low. So the useful goal is not 12 email addresses but 12 people who have the problem the app solves and will open it more than once.
Start with people who already asked for something like it: a community where you described the problem, friends in the target audience and people from your waitlist. Invite more than 12. Illustrative example: if a third of invited testers never opt in or drop out, 18 invitations leave 12 (18 × 2/3 = 12). Ask for honest feedback, not ratings; testers cannot leave public reviews on a test version anyway.
Search results for this requirement include paid tester services and tester exchanges. Their testers rarely match your audience, and the application asks about real usage and feedback, so testers who only keep an app installed give you little to report.
Draft the production application
Once the requirement is met, open Apply for production on the Play Console Dashboard. The form has three parts: your closed test, your app and your production readiness. Answer from what testers actually did, with numbers you observed, and name what you changed because of them.
If Google needs more, it may ask you to continue the closed test, for example when fewer than 12 testers stayed or engagement was insufficient. After approval, a production release still goes through Play's normal app review.
Questions cover the closed test (recruitment, feature use, expected production behaviour, feedback summary), the app (audience, value, expected first-year installs) and production readiness (changes made, how readiness was decided); reviews usually take 7 days or less, and you may need to continue testing.
Play Console Help: Testing requirements for new personal accountsWhat it costs, in money and days
The money is small: US$25 once for the developer account, plus any paid Gemini usage the app's users generate on your account. The time is longer. Illustrative example, not a benchmark: two days for identity checks, one day to publish to internal testing and recruit testers, 14 days of closed testing and up to seven days for the production application add up to about 24 days (2 + 1 + 14 + 7) before the public listing.
Use those weeks. The closed test is the first real look at whether anyone opens the app twice, which matters more than the listing date.
What AI Studio Android apps cannot do yet
According to Google's documentation, AI Studio builds single-module Kotlin and Jetpack Compose apps for phones and tablets, with Firebase AI Logic, App Check, Cloud Firestore and Firebase Authentication. It does not support server-side features such as secrets management, multiplayer or Google Workspace APIs (those are web-app only), Java or XML layouts, C/C++ or NDK code, Wear OS or Android TV, or GitHub export for Android; you can download the project as a ZIP and continue in Android Studio.
If your app needs one of those, plan the move to Android Studio before the closed test, so testers try the version you will ship.
Where Soloop fits
Soloop does not build, sign or publish Android apps. It helps with the part this guide cannot do for you: finding the people who need the app. According to the Soloop manual, it can research with sources where your audience talks, post on X after you connect it with OAuth, prepare Reddit posts for you to publish yourself and send cold email through a connected Gmail account. Actions wait for your approval by default.
A bounded first request: I built [app] for [who] to [job]. Find, with sources, three communities where these people ask about this problem and their self-promotion rules, then draft a tester invitation for each that follows those rules. Do not post or send anything.
Sources, limitations and refresh
Google's Android Developers Blog post of May 19, 2026, Google Play's October 2026 updates, the AI Studio Android and Build mode documentation, the AI Studio codelab and Play Console Help pages on getting started, test tracks, releases and testing requirements for new personal accounts were read on November 4, 2026. The path table, checklist, templates, tester buffer and timeline are editorial guidance; the numbers in the examples are illustrative. Google does not publish the markets for personal apps or AI Studio's free quota, and approval is not guaranteed.
This guide will be reviewed by February 4, 2027, or sooner if Google ships friends-and-family sharing for personal apps, closed-test management in AI Studio, or changes the testing requirement.
The Soloop manual describes research with sources, X publishing with OAuth, Reddit preparation with manual publication and cold email through a connected Gmail account; approval comes first by default. It does not build or publish apps.
Soloop product manual