148 words. That's all it took to ship a working Android app to a physical phone - no IDE setup, no Gradle configuration, no Android SDK installed. Just a browser tab and Google's AI Studio.
A Verge writer who had never built an Android app before documented the experience, building three apps in a single afternoon. For one, they typed a 148-word description and walked away. Ten minutes later, a real app appeared on their actual Android phone.
This is vibe coding - the practice of describing what you want software to do in plain English and letting an AI model write all the actual code. Google has been building toward this with Gemini inside AI Studio, and the Android-specific workflow has an advantage most competitors lack: Google owns the full stack. The AI model, the development environment, and the operating system are all theirs.
How the Workflow Runs
You type what you want. Gemini writes the code. AI Studio packages it into an installable app file. You either scan a QR code or connect via ADB (Android Debug Bridge - a tool that lets a computer talk directly to a phone for installing test apps) and the app installs. The full cycle ran about 10 minutes per app in this session.
The only real prerequisite: enabling developer options on your Android phone before starting. That's a settings menu most users have never touched - hidden behind tapping the build number seven times in the About Phone menu. Once that's on, the rest is surprisingly smooth.
The 148-word prompt is the detail worth sitting with. That's shorter than most Slack threads asking a developer to clarify requirements. The model isn't just generating code - it's choosing layouts, picking colors, handling all the packaging and configuration that typically absorbs hours of a developer's setup time.
The Actual Ceiling Here
These aren't production apps with real backends, user authentication, or anything you'd put in the Play Store. They're personal utilities and prototypes. A custom tracker, a calculator with niche logic, a simple form - that's the realistic output range.
But for people who had a specific tool in mind and no path to build it, that ceiling is high enough to be genuinely useful. Tools like Cursor and Claudee Code](/tools/claude-code/) have been doing similar things for web apps for over a year. Native mobile has lagged behind because the setup complexity scared most non-developers off before they ever wrote a line. Google just removed most of that friction for Android.