Yes, but “publish” covers three different jobs. Eligible users of Google AI Studio can launch a private personal Android app through Google Play without a developer account. That does not create a public Play Store listing. Testing with other people and releasing publicly use the developer-account route. Google’s October announcement introduces the personal option; it does not abolish app-store publishing requirements.
Start with who needs the app. A weekend calculator for yourself and a product for customers should not send you through the same checklist.
Personal app, internal test, or public release?
| Your goal | Developer account? | Who can install? | Where it appears |
|---|---|---|---|
| Run a personal app | No, where supported | You | Private, outside the public catalog |
| Share an internal test | Yes | Up to 100 selected testers | A Google Play testing track, accessed through the test link |
| Launch publicly | Yes | Eligible Play users in your chosen markets | Public Play Store listing after release requirements and review |
The testing and production distinctions follow Play Console’s release guidance. Open testing is another developer option, but it sits outside AI Studio’s documented internal-test shortcut. New personal developer accounts only unlock it after gaining production access.
For a tool you only need yourself, check the personal route first. For feedback from other people now, use testing. For a public product, plan the release work before promising a launch date.
What changed between May and October?
On May 19, 2026, Google introduced native Android creation in AI Studio: Kotlin generation, a browser emulator, installation over USB, and developer-account publishing to an internal test track. The I/O announcement described those capabilities months before personal apps arrived.
October 13 added the private Play route. Friends-and-family sharing was announced for the coming months, without a firm date.
That explains the main apparent contradiction. Instructions requiring a developer account can still be correct for internal testing. They are incomplete advice for someone whose only goal is personal use.
There are also genuine documentation differences, covered below. Treating every older instruction as obsolete would create another set of wrong answers.
Is the personal-app feature available to you?
Google says the rollout starts in selected markets, including the United States, for people aged 18 and over using a standard Google account. The announcement does not say whether Google Workspace, school, or other managed accounts qualify.
The reviewed Google documentation does not provide a complete personal-app country list or an account-by-account rollout schedule. That supports neither “worldwide” nor “U.S. only.”
AI Studio’s general availability list includes Australia, the UK, Canada, and many other countries. It also describes age verification. Access to the builder does not establish access to this new Play feature.
If the option is missing, check availability before paying for a developer account just to solve a personal-install problem.
How to get your app onto your Android phone
First, make sure you are building an Android project. AI Studio also builds web applications; publishing a web URL does not produce an Android store release.
Google’s Build documentation distinguishes native Kotlin and Jetpack Compose output from its web stack. Choose the Android option before generating the project.
A sensible first brief is small: one user, one recurring task, and a clear description of what should be saved. For example, a packing checklist that remembers checked items after the app closes. Add accounts, payments, and shared data only when the job actually needs them.
Google’s Android codelab documents building, previewing, and iterating in the browser. Test whether your app does its job before worrying about distribution.
For the new personal Play route, Google’s announcement establishes the capability but does not supply a complete click-by-click installation guide. We cannot give you a verified button sequence for it yet.
There is an established alternative: USB installation. Google documents using Chrome or Edge, connecting an Android phone with a data cable, enabling USB debugging, and using AI Studio’s install control. The codelab calls this Install, then Install via USB. The Android reference uses Install on Device.
Follow the flow your interface exposes. This puts a build on the connected device; it does not create a public listing. It also gives you a practical fallback while the personal Play rollout is incomplete.
How to share with testers today
Use the developer testing route when another person needs to install a build now.
Google’s Android reference documents Settings > Publish > Publish to Play Store, authentication with a Play developer account, and automatic signing through a managed keystore.
The codelab describes a shorter Publish flow and confirms that its destination is internal testing. Neither is a documented personal-app installation sequence.
Google’s codelab shows AI Studio collecting tester email addresses, then displaying a shareable link and QR code once published. If your interface does not offer that, manage testers in Play Console: open Test and release > Testing > Internal testing, select Testers, create an email list if needed, and select it. Provide a feedback contact, copy the shareable link, and save your changes. The opt-in link appears only when the app status is Published, and each tester must open it and opt in. Testers need a Google or Workspace account. Google’s testing guide explains the access controls.
Do not confuse this with the future friends-and-family feature. A relative can be an approved tester under the existing developer workflow without that new sharing feature having launched.
What public publishing still requires
A public release starts with a Play Console developer account. Registration currently costs US$25 once, with identity verification and, for new personal developer accounts, Android-device verification. Google’s registration guide lists Personal and Organization as the account types.
That terminology matters. A standard Google account, a private personal app, and a Personal developer account are different things. The announcement’s phrase “professional developer account” does not establish a new third account type or require every individual to register an organization.
For personal developer accounts created after November 13, 2023, Google requires a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Internal testing does not satisfy that specific closed-test requirement. Meeting the minimum lets you apply; it does not guarantee approval. Read the production-access requirements.
Then complete the store listing, app-content and review requirements, release artifact, signing, and production submission in Play Console. Google’s release guide specifies Android App Bundles for new apps; its APK exception concerns apps created before August 2021.
Budget for review and fixes. A generated app that opens successfully is still a long way from a product that strangers can rely on.
What you can export, and where the docs differ
AI Studio generates a Gradle-based Android project. ZIP export to continue in Android Studio is documented.
Direct GitHub export is less clear: Google’s May Android announcement includes it, while the Android reference, last updated August 18, says Android export is ZIP-only. Use ZIP as the documented common route; verify GitHub availability in your project.
The same sources use different packaging terms: the reference describes signing an APK, while the launch announcement describes uploading a bundle. Those terms are not interchangeable. Inspect the actual release artifact rather than assuming a locally installed APK is ready for a new public submission.
Google says Play will help you move a personal app to a developer account. The announcement does not explain update delivery or how signing identity and app data carry over. Plan for those questions before promising customers a seamless conversion.
Is it free, and does it need Google AI Pro?
Google’s billing documentation says AI Studio usage is free unless you link a paid API key for paid features. The personal-app announcement does not mention a Google AI Pro or Ultra requirement. Free use has limits: Google’s AI plans page describes a modest free-plan quota, with higher daily allowances for Pro and Ultra subscribers across Playground and Build.
That is not a promise of unlimited free development or operation. Gemini API usage has its own project and model limits, and services your app uses can incur separate charges. The reviewed documentation does not specify a build quota or app-count limit for personal apps.
The offer to deploy two apps without a billing account is the Google Cloud Starter Tier, covering Cloud Run-hosted full-stack web apps. Firebase’s AI Studio guide explicitly excludes Android apps from Starter Tier. This offer provides neither a two-app Android allowance nor a waiver of the Play developer fee.
One security detail older guides miss
The August Android reference says Firebase integration is unavailable. Firebase’s integration documentation, updated October 13, now describes Android support for Cloud Firestore, Authentication, Firebase AI Logic, and App Check. It also says Android integration is rolling out over several days. Check that AI Studio offers the integration in your account before planning around it.
Firebase warns against embedding a Gemini API secret in the distributed app and requires review and testing of generated Security Rules. Automatic setup does not remove that responsibility.
A private install controls distribution. It does not prove that the app keeps every piece of data on the phone or that its generated code is secure.
Choosely’s take
This change makes small personal utilities more practical. It also makes the question “Can I publish it?” less useful than “Who needs to use it?”
Choose the release path first. Keep the first app small enough to inspect. Move into public distribution when you are ready to maintain software for other people.
If you are still choosing a development platform, our AI app builder comparison covers that earlier decision.
FAQ
Can this publish the same native app to Apple’s App Store?
No. Firebase’s current integration guide explicitly says AI Studio does not support creating iOS apps. A web app working in an iPhone browser is a different output.
Do I need to install Android Studio first?
No. The browser workflow includes an emulator. Android Studio becomes useful when you need deeper local development and debugging.
Should a beginner start with a public app?
Start with a contained job you can test yourself. Learn what breaks when you close the app, lose connectivity, or enter unexpected data. Treat other people’s accounts and information as a reason to get competent review.
Building a broader AI workflow? Explore Stack Intelligence to organize the tools you use.
The Change Brief
Get the week’s AI changes in one clear read
Pricing moves, tool launches, free-tier changes and practical stack updates, filtered for people who actually use these tools.
Stay ahead of AI without following it all day. We’ll send you what matters each week.
Continue reading
Related reads
AI Tool Recommendations
Best AI App Builder in 2026: Lovable vs Bolt vs Bubble vs Replit
The best AI app builder in 2026 depends on what you are actually building. Here’s the right pick for MVPs, internal tools, complex no-code apps, and mobile-first products.
AI Tool Recommendations
Best Vibe Coding Tool in 2026: Cursor vs Lovable vs Bolt vs v0
A practical comparison of Cursor, Lovable, Bolt, and v0 to help founders and teams choose the right vibe coding tool for code control, full-stack delivery, rapid validation, or interface-first work.
