Start Here
Choose the right Buzzy workflow before you start building.
Buzzy gives you several ways to create and improve an app. The best starting point depends on how much structure you already have, whether you want to work with an AI agent, and how much visual control you need.
For most serious app builds today, start with Buzzy Builder MCP. It gives an AI agent such as Codex or Claude Code a structured way to build with Buzzy in stages: brief, flows, data model, theme, blueprint, screens, sample data, and verification.
Recommended for new builders: use Buzzy Builder MCP, especially when you want to build from a template, work iteratively, inspect the app with screenshots, or test real workflows before shipping.
In our experience, Builder MCP has often been the most cost-effective path and produced the best-quality results for serious app creation and editing, while supporting staged review and control. Use it through an MCP-capable agentic AI development tool such as Codex, Claude Code, Cursor, or Antigravity. Direct Adapt work on a copied template or existing app does not require Buzzy AI generation credits; the connected tool's subscription or usage allowance applies. A from-scratch Create workflow that invokes Buzzy generation also needs separately purchased Buzzy AI credits or a supported bring-your-own OpenAI API key. Buzzy Deployment subscriptions do not include a recurring monthly AI credit allowance. See Builder MCP: Create vs Adapt.
AI cost and output quality depend on the app, instructions, selected model, and current model performance. AI can make mistakes; review and test generated results before publishing.
Choose Your Starting Path
Build a production-minded app with staged review
Adapt an existing template into a new app
Create a quick prompt-first app in the workspace
Design and publish directly from Figma
Change an app that already exists
For a fuller comparison, see What to use when.
The Recommended Builder Workflow
The most reliable Buzzy builds are planned and reviewed in stages:
define the app brief
map the key flows
model the data
choose the theme direction
review the blueprint and navigation
generate or adapt screens
add realistic sample data
verify the app in preview or runtime
This staged flow keeps changes easier to review and cheaper to correct. It is especially important for apps with roles, permissions, sensitive data, payments, external integrations, or several connected workflows.
Helpful Next Reads
Last updated