Vibe coded apps are about to flood the Play Store; Google's preparing for chaos

Since Google I/O in May 2026, you can type a description into Google AI Studio and get a native Android app. I've done it several times.

Watching a half-formed idea turn into installable software in minutes still feels unreal. The Play Store seems to know what's coming.

Code strings found in a teardown of the Play Store APK point to a new "Your creations" section for apps made with AI Studio, along with hints that you'll be able to share them.

When anyone can make an app, the store has to figure out where all those apps go. Google wants more people building software, and it also has to keep its store from drowning in it.

Related

6 reasons Google slacking on AI safety reports is a big problem

The implications could be catastrophic

Posts By  Jon Gilbert

From a text box to your phone in one browser tab

Kotlin code written by an agent

AI Studio uses its Antigravity Agent to write what Google calls production-ready Kotlin, built with Jetpack Compose, the same declarative UI toolkit Google recommends to professional engineers.

The workflow happens in a browser tab. You don't need to download Android Studio (it's massive) or configure a local SDK.

A cloud-based Android emulator streams into your browser tab, so you get a live, interactive preview. You describe the app, the agent writes the files, and then you poke at the result.

Want the buttons somewhere else? Ask the chat panel to move them.

When you're ready to try it on your hardware, turn on USB debugging, plug in your phone, and AI Studio installs the app from Chrome or Edge.

Large-scale code generation is now open to everyone

The usual curation methods won't keep up

The number of app submissions is about to spike. Going from a rough idea in the AI Studio playground to a shippable app package is now scary fast.

I went from an empty prompt box to a working utility app in a single afternoon. However, I probably have more programming knowledge than the average person trying this.

Still, I believe anyone curious and patient enough can try this, and if anyone can get working software by describing it in English, the usual curation methods won't keep up.

Google already works at this kind of scale internally. In April 2026, CEO Sundar Pichai said AI generates 75% of all new code at Google.

Now that kind of generative volume is open to everyone. Expect the submission queues to fill up with habit trackers and hyper-niche productivity tools.

A separate shelf could save the top charts from AI slop

Some legitimacy for prompt-built apps

Google is reworking the storefront. The Play Store already summarizes reviews with AI, and at I/O 2026 Google introduced Ask Play, a Gemini-powered overlay that recommends apps through conversation.

I think a separate shelf for vibe-coded apps is a smart move. It has two benefits per se.

First, it keeps prompt-generated spam out of the main top charts. Polished, human-built apps take years of investment.

Forcing them to fight for visibility against thousands of instantly generated clones, many of which would be AI slop, would wreck the app economy.

Second, it gives prompt-built apps a home of their own. Users get a sandbox for weird or highly personal tools, and nobody walks in expecting enterprise-grade stability.

A designated space also gives AI-made software some legitimacy, which it doesn't really have yet when it's mixed in with everything else.

A working app isn't necessarily a safe one

Security has to start with Google

Shipping software written entirely by a large language model is risky. Models hallucinate.

They can misconfigure manifest permissions, mishandle local storage, and trust user input without checking it.

I recently read about a developer who took apart 20 AI-built Play Store apps. He confirmed security problems in seven of them.

Four shipped secrets inside the app, including a Google Cloud private key and .env files packed with AI provider keys that "accidentally" made their way into the release packages.

The other three had weak encryption, insecure network settings, or components that other apps could reach.

Google is in an unusual position here because it makes both the tool that writes these apps and the store that distributes them. It can't leave security to people who, by design, don't know what to look for.

If AI Studio is going to hand anyone an app, it should check that app for exposed keys and leftover development files before it reaches the Play Console, and the Play Store should scan for the same things on upload.

Google has made building an app easy. Now it needs to make shipping an unsafe one hard.

Human developers still own the hardest parts of the job

Professional Android developers still have plenty to do, but the work looks different. AI Studio handles boilerplate well.

It'll build the interface and set up navigation without complaint, and it writes basic logic just fine. Still, I think the browser setup hits a hard ceiling as soon as an app needs a backend.

AI Studio's Android apps are client-side only, so there's no server, no Firebase, and no built-in way to keep secrets off the device.

The cloud emulator also can't test the camera, NFC, Bluetooth, or Google Play Services like Maps and sign-in, so anything that touches hardware has to be checked on a real phone.

If your app needs to sync data between users or talk to a wireless accessory, vibe coding gets more complicated. That means human developers still have plenty to do.