For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Buzzy gives you several ways to create and keep improving an application. You can start from a prompt, a Figma design, a Builder MCP workflow, or the no-code Workspace. All paths create or edit the same underlying Buzzy app definition: brief, flows, data model, blueprint, theme, screens, functions, widgets, people, settings, tests, and security configuration.

The important idea is that Buzzy does not leave you with a one-off pile of generated code. Buzzy stores a structured app definition that the Buzzy runtime can render, test, secure, publish, and keep maintaining.

Ways to Create an App

Starting point
Best when
How to start
How to keep iterating

You have an app idea and want a working first version quickly.

Describe the app, audience, core data, roles, and workflows.

Use the Workspace to refine brief, flows, data, screens, theme, tests, security, functions, widgets, and settings.

You have a designed UI, a design team, or want direct design control.

Mark up a Figma file with the Buzzy plugin and publish it as a working app.

Keep editing in Figma, publish updates, and use Buzzy Workspace for data, access, testing, security, and extensions.

You want an AI coding agent such as Codex or Claude Code to build, adapt, inspect, or modify a Buzzy app in stages.

Connect the agent to Builder MCP and follow the staged workflow.

Let the agent inspect current artifacts, make bounded changes, validate, test, and open reviewable updates.

No-code Workspace editing

You want to build or maintain directly in Buzzy without using Figma or an external agent.

Open the Workspace and edit Data, Design, Theme, People, Settings, Functions, MCP, Tests, and Security.

Use the left navigation as the app control surface for ongoing changes.

The Common Iteration Loop

Most Buzzy work follows the same loop, even if the starting point is different:

  1. Clarify the product goal, users, roles, and core workflows.

  2. Shape the data model around the records the app needs to store and secure.

  3. Define or refine the screen map and navigation.

  4. Build or edit screens that bind to the right datatables and fields.

  5. Apply a coherent theme.

  6. Add functions, constants, widgets, APIs, or MCP when the app needs extension points.

  7. Configure People, Teams, Organizations, and Settings.

  8. Create Tests for important workflows.

  9. Run Security Review before exposing sensitive data or wider access.

  10. Publish, monitor, and continue iterating.

Where to Go Next

Last updated