Google Play Store Vibe-Coded Apps: What AI Studio Actually Builds

Google AI Studio can now turn a plain-language prompt into a native Android project and push that build directly into Google Play testing.

That is the confirmed story behind the recent chatter about Google Play Store vibe-coded apps. It does not mean Google has created a public Play Store category for AI-generated apps, nor does it let a prompted build skip the normal process required for a production release.

Google's current AI Studio Android documentation spells out the workflow in more detail than its original I/O announcement. The Antigravity Agent generates a standard Kotlin and Jetpack Compose project, previews it in a browser-based Android emulator, lets the builder install it on a physical device, and can publish it directly to Google Play's Internal testing track.

What AI Studio's Android builder actually creates

Inside AI Studio's Build mode, select Android from the platform picker and describe the app you want.

The Antigravity Agent then generates a complete Gradle-based Android project rather than a web mockup.

Google says the generated project uses:

• Kotlin

• Jetpack Compose

• Material 3

• A single-activity architecture

• ViewModels and data classes

• Standard Android resources and manifest files

The code remains visible and editable inside AI Studio.

You can also download the project as a ZIP file and continue development elsewhere.

That makes the Android workflow different from simply prompting Gemini to sketch an interface. It produces actual Android source code and a build that can run on Android hardware.

There are limits, though.

AI Studio's current native Android projects are client-side only. Google says server-side features such as Firebase integration, Google Workspace APIs, secrets management, and multiplayer are available for web apps, not native Android projects built through this workflow.

The Android builder also currently supports only single-activity, single-module projects using Jetpack Compose. Java, XML layouts, NDK code, Wear OS, and Android TV projects are not supported.

You can install the app without publishing it

AI Studio includes a browser-based Android emulator for testing the generated app before it reaches Play.

Builders can also install the APK on a physical Android phone or tablet through WebUSB.

That requires:

• Chrome or Edge

• An Android device with Developer Options enabled

• USB debugging

• A USB cable between the device and computer

AI Studio handles the transfer through the browser, so a separate local ADB installation is not required.

This is useful for testing a prompted app privately before creating any Play release at all.

What "publish to Play Store" actually means

The one-click publishing option does not send a vibe-coded app straight into public Google Play search results.

Google calls the feature Direct-to-Play Store testing.

A builder connects a Google Play Developer account inside AI Studio, then opens Settings > Publish and selects Publish to Play Store.

Google says AI Studio then:

• Authenticates the developer account

• Signs the Android build using a managed keystore

• Creates an app listing or uploads a new version

• Publishes it to the Internal testing track

• Returns a link for testers

A Google Play Developer account currently carries a one-time $25 registration fee, and the developer profile must be completed before publishing through the integration.

The important limit is explicit in Google's documentation: AI Studio publishing stops at Internal testing. Production releases must be managed in Play Console.

Internal testing is not a public Play Store listing

Google Play treats Internal testing as a private release track.

Google's current Play Console documentation says apps in Internal testing are available to testers through a URL and are not discoverable on Google Play.

Internal testing supports up to 100 testers.

That means somebody can genuinely publish an AI Studio-generated Android app "to Google Play" while the app remains invisible to ordinary Play Store users.

Moving beyond that requires the normal Play Console release process.

Production apps still need the required store setup, policy compliance, review information, content rating, data-safety information where applicable, and a production release managed through Play Console.

New personal developer accounts have another hurdle

Some builders also face mandatory testing before Google will give them production access.

For personal developer accounts created after Nov. 13, 2023, Google currently requires a closed test before an app can go public.

Google's testing requirements require at least 12 testers to remain opted into that closed test continuously for 14 days before the developer can apply for production access.

Internal testing does not satisfy that requirement by itself.

So the path for a new personal developer can look like this:

1. Generate the Android project in AI Studio.

2. Test it in the browser emulator or on a physical device.

3. Publish it from AI Studio to Internal testing.

4. Complete Play Console setup.

5. Run the required closed test.

6. Apply for production access.

7. Publish to production through Play Console.

The AI shortcut removes development and upload friction. It does not remove Google's release requirements.

There is no vibe-coded app category on Google Play

Google has announced several new Play discovery features in 2026, but none is a dedicated section for AI-generated or vibe-coded apps.

Its I/O Play announcements included Play Shorts, conversational discovery through Ask Play, and app discovery through Gemini.

Google has not announced an AI-generated badge, a vibe-coded category, or a separate storefront where apps made through AI Studio are grouped together.

Once an AI-generated app eventually reaches production, it goes through the ordinary Play publishing system rather than being placed into a special AI Studio destination.

How the code was originally generated is therefore separate from how the finished app is distributed.

A prompt gets you an app project, not a finished product

Google's tools remove a large amount of setup work, but that doesn't make every prompted build production-ready.

The current Android builder has clear architectural restrictions, and an automatically generated project still needs testing for crashes, broken flows, accessibility, permissions, privacy behavior, security, and compatibility.

The Internal testing limit reinforces that distinction.

AI Studio can get a builder from a description to a working native app and private Play distribution quickly. Public launch still involves Play Console and the same production responsibilities other Android developers face.

That is especially important for apps handling accounts, personal information, payments, health data, location, or other sensitive information.

Generated code still needs review.

What happened to the idea of creating personal apps directly on a phone?

A separate concept circulated around I/O: a phone-level system that could generate small personal apps, widgets, or utilities without distributing them through Play.

That is not the Android publishing feature Google documented.

Google's I/O AI Studio announcement did announce a mobile AI Studio app for pre-registration. Google described it as bringing Build mode to a phone so developers could start an idea, iterate on code, preview builds, remix projects, and share deployments while mobile.

That is different from Android itself generating private home-screen apps or widgets on demand without a normal application project.

The system-level personal-app concept described in third-party reporting therefore should not be treated as another name for AI Studio's Android builder.

Google's documented product creates Android projects. Its Play integration publishes those projects to an Internal testing track.

Google Cloud deployment is a separate part of AI Studio

Google also announced that new AI Studio builders could deploy their first two apps to Google Cloud at no cost without supplying a credit card.

That announcement applies to AI Studio's broader app-building platform and should not be confused with publishing the native Android app to Google Play.

The current native Android documentation says those projects are client-side only.

AI Studio's web-app builder is the part of the platform that supports a full-stack environment and server-side runtime.

So a free Cloud deployment is not an extra step that automatically turns an Android test build into a public Play app.

What builders should check before using the workflow

Before treating AI Studio as a shortcut to an Android launch, check the current limits.

Make sure:

• A client-side, single-activity Jetpack Compose app is sufficient for the project.

• The app does not depend on unsupported server-side features.

• You have a completed Google Play Developer account if you want one-click testing.

• Internal testing is enough for the current stage of development.

• You understand any closed-testing requirements tied to your developer account.

• The generated code has been reviewed and tested before wider distribution.

If the project outgrows AI Studio's current Android restrictions, download the source and continue development in a full Android development environment.

What Android users should expect

Ordinary Play Store users do not currently have a "vibe-coded apps" section to browse.

An AI Studio app sent to Internal testing is available only to its testers and is not discoverable through normal Google Play search.

If that app later reaches production, it appears through the standard Google Play publishing system.

That leaves a much narrower reality than the phrase "Google Play Store vibe-coded apps" suggests.

Google has made it dramatically easier to generate a native Android project, test it on real hardware, and send it into Play's private testing infrastructure. It has not created a separate public marketplace for AI-generated apps, and it has not removed the testing, policy, and production-release steps that sit between a prompted prototype and something anyone can download.