Article
Firebase Studio App Prototyping Agent: Sunset and Scope
Firebase Studio's App Prototyping agent generated Next.js apps from prompts. New workspaces are disabled, and Firebase Studio is scheduled to shut down in 2027.
In this article
Firebase Studio App Prototyping Agent
Firebase Studio's App Prototyping agent was a hosted, prompt-driven environment for generating Next.js applications, previews, and optional Firebase-backed services. It is now a historical product for new buyers. Google disabled new Firebase Studio workspace creation and new user signup on June 22, 2026 and plans to shut down Firebase Studio on March 22, 2027.
The tested E098 interface should not be called Genkit. Genkit is a separate open-source application framework.
Product at a glance
| Surface | Documented role | Current boundary |
|---|---|---|
| Prototyping agent | Generate a blueprint, code, and web preview from prompts | New workspaces and new user signup are disabled |
| Application stack | Next.js with optional Firebase and Gemini services | Existing projects require migration before shutdown |
| AI features | Gemini API with Genkit flows when used | Genkit is a framework dependency, not the builder itself |
| Publishing | Firebase App Hosting with a billing account | Core Firebase services continue beyond Studio |
| Migration | Google AI Studio, Antigravity, or other environments | Chat history and managed configuration need special handling |
flowchart LR
A["Prompt and optional image"] --> B["Blueprint"]
B --> C["Generated Next.js app"]
C --> D["Firebase services and Gemini when selected"]
C --> E["Preview and iteration"]
E --> F["Migration before March 22, 2027"]
F --> G["Google AI Studio, Antigravity, or another platform"]
What the product did
Google's App Prototyping agent guide describes a no-code flow that generated an application blueprint, code, and web preview from natural language and optional images. It could provision a Gemini API key and Firebase project, add Firestore and Authentication during iteration, expose code view, and publish through Firebase App Hosting.
The same guide warns that generated output can appear plausible while being factually wrong, says untested generated code should not be used in production, and cautions against entering personally identifiable information or user data into the chat. Those boundaries are directly relevant to any generated application.
Firebase App Hosting documentation describes the deployment service that could continue to run an exported or migrated application. Firebase Studio's retirement does not retire core services such as Firestore, Authentication, or App Hosting.
Sunset and migration
Google's sunset and migration guide says new workspace creation and new user signup were disabled on June 22, 2026. Existing workspaces can continue until March 22, 2027. On that date, Firebase Studio is scheduled to shut down and remaining Studio data is scheduled for deletion.
Google recommends Google AI Studio for browser-based prototyping and Antigravity for code-first agentic development. The migration guide also describes ZIP, GitHub, Firebase CLI, and external-hosting routes.
The guide warns that chat history is not included in the normal exported ZIP and explains a separate recovery route. It also notes that shared workspaces can retain backend pointers to the original owner's resources. Migration therefore needs more than code download.
E098 lab context
In Venture Step's January 5, 2026 E098 run, the App Prototyping agent generated several insurance dashboards. The recording shows Firebase Studio, a generated interface, a Gemini API-key prompt, and a visible security-check recommendation.
Dalton found the result unstable, difficult to navigate, and unable to meet his intended one-shot behavior. That is a dated first-hand observation, not a current comparison candidate.
How to use this profile
For a new procurement decision, do not include Firebase Studio as an available builder. Review Google AI Studio or Antigravity on their current terms instead.
For an existing Firebase Studio project, identify the workspace owner, recover source and chat history, map Firebase projects and keys, select a migration route, test the migrated application, preserve the domain where necessary, and finish before the shutdown date. Verify the sunset schedule again before taking action because migration guidance can change.
Sources
Follow the evidence.
- docs.base44.com: githubdocs.base44.com
- web.dev: vitalsweb.dev
- docs.replit.com: replit appsdocs.replit.com
- docs.replit.com: build with agentdocs.replit.com
- csrc.nist.gov: finalcsrc.nist.gov
- help.emergent.sh: 272715 features and toolshelp.emergent.sh
- firebase.google.com: migrating projectfirebase.google.com
- owasp.org: www project application security verification standardowasp.org
- docs.base44.com: Quick start guidedocs.base44.com
- w3.org: WCAG22w3.org
- firebase.google.com: get started aifirebase.google.com
- help.emergent.sh: plans and creditshelp.emergent.sh
- docs.lovable.dev: githubdocs.lovable.dev
- docs.lovable.dev: getting starteddocs.lovable.dev
- firebase.google.com: overviewfirebase.google.com