Firebase Studio for Android: What It Actually Builds in 2026

Google building an AI-powered app studio is a genuinely big deal. Firebase Studio — the product that evolved from Project IDX and launched publicly in April 2025 — represents Google's most serious attempt yet to go from a text description to a deployed application. It integrates with AdMob, Google Play, Firebase Analytics, and Firestore natively. The AI is powered by Gemini 2.5. It runs entirely in the browser.

On paper, it sounds like exactly what Android developers have been waiting for. A prompt-to-app pipeline from the company that owns Android, backed by one of the most capable models available, with the entire Google developer ecosystem wired in. So: does it build native Android apps?

The answer is more nuanced than most articles will tell you — and there's a specific sentence in Google's documentation that changes everything.

What Firebase Studio actually is

Firebase Studio is a cloud IDE — specifically, a browser-based Code OSS editor (the open-source base of VS Code) running on Google's infrastructure. It is not a no-code tool. You still write, read, and debug code inside it. What makes it distinctive is the layer of AI and Google ecosystem integration built on top of that familiar IDE surface.

The centerpiece feature is the App Prototyping Agent. You describe an application in natural language, and the agent generates a blueprint, writes the initial code, and renders a live preview — all without you touching the editor. It's fast, and the blueprints are thoughtfully structured. Gemini 2.5 handles the code generation, which means the output quality is meaningfully better than what earlier AI code generators produced.

Beyond prototyping, Firebase Studio offers deep integration with the Google ecosystem by design:

• Firebase Authentication, Firestore, and Cloud Functions can be wired into new projects automatically
• Firebase Hosting handles deployment for web projects
• The integrated terminal and build tooling run on Google's cloud infrastructure, which Google has noted compiles faster than local Intel machines for some workloads
• No local setup is required — it works in a browser on any device, including low-powered machines

It also supports Flutter workspaces (two are free; Premium unlocks more), giving mobile developers a cloud-based environment for Flutter development without local Android Studio or Xcode installations.

Firebase Studio is currently free during preview. Firebase usage (Firestore reads/writes, hosting bandwidth, etc.) is billed separately at standard Firebase rates.

The Android question: what does it actually output?

Here is the sentence that matters. From Google's official Firebase Studio documentation on the App Prototyping Agent:

"The agent supports Next.js apps, with other platforms and frameworks planned in the future."

That's it. The App Prototyping Agent — the AI feature that takes your text prompt and generates a full application — only generates Next.js web apps. Not Flutter. Not React Native. Not Kotlin. Not Jetpack Compose. A Next.js web application that runs in a browser.

This isn't buried in fine print. It's in the main documentation for the feature. But it tends to get lost in coverage that leads with "Google's AI can build your app" without specifying what "app" means here.

What about Flutter?

Flutter workspaces do exist in Firebase Studio, and they're a genuinely useful feature for Flutter developers who want a cloud-based IDE. But the AI prototyping agent does not support Flutter workspaces yet. You can write Flutter code in Firebase Studio — Gemini will assist you as a coding assistant inside the editor — but you cannot describe an app in natural language and have Firebase Studio generate Flutter code from scratch the way it does for Next.js.

What about APK generation?

Firebase Studio does not generate APKs. Even for Flutter projects, it provides the IDE and the compilation environment — but producing a signed APK or IPA for distribution still requires external tools. As the research from newly.app documents: "No APK/IPA generation — you still need external tools like EAS Build, Xcode, or Android Studio to compile native binaries."

The gap between "runs in the cloud IDE preview" and "installable on an Android device" is non-trivial. It requires build configuration, signing key setup, and either Android Studio locally or a service like EAS Build in the cloud.

What about AdMob and Google Play?

Firebase Studio does have excellent Firebase and Google product integration — but the AdMob and Play Store compliance claims in marketing language refer to what's possible after you wire things up yourself. AdMob is not automatically configured in your generated app. Configuring AdMob in a web application (which is what the prototyping agent generates) is also a different, more limited use case than AdMob in a native Android app.

Where Firebase Studio genuinely shines

To be clear: Firebase Studio is impressive, and it's the right tool for a specific set of problems. The criticism above isn't that it fails to do what it claims — it's that what it claims and what many people assume it claims are different things.

For the right use case, it's the fastest path available:

• Next.js web app prototyping. Describe a product, get a working prototype with Firebase Auth and Firestore wired in. This is genuinely faster than any other method available today. For founders validating a web product, this is a significant time saver.
• No local setup. Works in a browser on any device. A Chromebook, a MacBook with a fresh OS install, a borrowed machine — all work equally well. This removes a real barrier for developers in low-resource environments.
• Google ecosystem depth. If you live in Firebase — Analytics, Auth, Firestore, Cloud Functions, Hosting — Firebase Studio integrates all of it more seamlessly than any external IDE. Authentication flows, database rules, and cloud functions can be added with conversational prompts to Gemini inside the editor.
• Cloud compilation speed. For compute-heavy builds, Google's cloud infrastructure is measurably faster than local Intel machines. This matters most for Flutter projects that have long build times locally.
• Gemini as a coding assistant. Even outside the prototyping agent, Gemini 2.5 integrated into Code OSS is a capable pair programmer for any language the editor supports.

Who Firebase Studio is not designed for

Firebase Studio is a developer tool. This sounds obvious stated plainly, but a lot of the confusion in coverage comes from positioning language that obscures it. Here's who should not expect Firebase Studio to solve their problem:

Non-developers

The App Prototyping Agent generates a starting point — but it doesn't maintain it. Making incremental changes, debugging errors, and extending functionality all require understanding code. One reviewer described the experience directly: "Making small changes can often lead to errors after errors. While Firebase Studio tries to fix these errors, letting the AI fix it leads to nowhere." That matches the experience many developers have had with AI code generation at the limits of its context: error loops that require human judgment to escape.

The same reviewer noted that "vibe coding in general is still mainly useful for developers to prototype rapidly" — which is an accurate characterization of where the technology sits in 2026. Firebase Studio is an acceleration tool for developers, not a replacement for development knowledge.

People who want a native Android APK from a prompt

This is the most important point to understand. Firebase Studio does not take a text description and output a native Android application. It outputs a Next.js web app. For Android specifically — native Kotlin, Jetpack Compose, Play Store ready — Firebase Studio is not the right tool today. The platform roadmap suggests this may change, but "planned for the future" is not a shipping date.

People who want AdMob and subscriptions wired automatically

AdMob integration in a native Android app requires Kotlin-level implementation: manifest declarations, SDK initialization, ad unit IDs, and placement logic inside Compose layouts. RevenueCat for subscription management requires its own SDK integration and entitlement configuration. Firebase Studio doesn't do any of this automatically, even for the Firebase-native features it does support. You get a good starting point for a web app, with manual work still required to monetize it.

The gap Firebase Studio doesn't fill

Firebase Studio is the most capable AI-assisted development environment Google has shipped. It's a real step forward. But it's worth being precise about what "the gap" is, because it's specific:

There is still no Google product — or any product — that takes a text prompt and outputs a production-ready, native Kotlin Android APK with AdMob and RevenueCat wired in, ready for the Play Store, without requiring a developer.

Firebase Studio gets closer than anything Google has shipped before. Gemini inside Android Studio gets close on the IDE-assistance side. But both are still developer tools. They accelerate the work of building — they don't eliminate the need for development knowledge.

The demand for that product is real. Hundreds of thousands of people have ideas for Android apps but no path to building them: no Android Studio experience, no Kotlin knowledge, no appetite to debug Gradle build files. For those people, the current landscape — including Firebase Studio — offers increasingly impressive tools for developers, and almost nothing for everyone else.

That's the exact gap Vixo is built to fill. Native Kotlin/Compose output — not Next.js. AdMob built in automatically, not manual. RevenueCat subscriptions wired without configuration. No IDE required. Play Store ready. The output is a real APK you can submit, built from a text prompt, in under 10 minutes. At $20 per project, with early access open now.

Comparison: Firebase Studio vs. the alternatives

Related articles