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

3. Understanding the Workspace Editor

When a prompt is processed, the Buzzy Workspace is populated with structured views of your app. The sidebar navigation is organised into the following sections:


Dashboard

A central overview of your app, showing key information such as app name, creator, creation date, and last modified date. The Dashboard also provides quick links to documentation and getting started guides, as well as a summary of your app's development progress and suggested next steps.


BUILD

🔹 Brief

A high-level summary of what your app does, based on your prompt. You can revise this at any time to re-guide the AI.

🔹 Blueprint

An auto-generated list of screens and key components. This gives a birds-eye view of your app's structure and user flow. Note: Blueprint is hidden for Figma-created apps.

🔹 Design

Where you view and edit the actual screens. This includes layout, components, bindings, actions, and screen-level logic.

Inside the Design workspace you will usually work across four areas:

  • the left panel for screen structure and assets

  • the centre preview for interacting with the current screen

  • the right-hand tabs for Properties, Code, and Debug

  • the AI chat panel for prompting, diagnosis, and autofix suggestions

The Debug tab is contextual to the current screen or selected node. It shows issue counts, data-binding details, runtime context, and entry points for AI diagnosis. The AI chat panel also includes a dedicated diagnose flow, so you can start debugging from either side of the editor.

For Figma-created apps, screens are previewed here but are not directly editable. A button is provided to open the linked Figma file for editing.

🔹 Data

A list of data collections (e.g. tasks, users, products) and their fields. These power your app's dynamic content.


CONFIGURE

🔹 Constants Beta

Secure storage for API keys, passwords, database URLs, and other configuration values used by your app and its Functions. Constants can be regular (plain text) or secret (AES-encrypted). Use the BUZZYCONSTANTS() syntax to reference them in your Functions' environment variables.

🔹 MCP Beta

Configure Model Context Protocol (MCP) for your app. MCP enables AI assistants like ChatGPT and Claude to interact with your app through natural language — querying data, creating records, and performing actions. Buzzy automatically generates the MCP server and tools from your app's data model.

🔹 Functions Beta

Build and manage serverless Buzzy Functions — AWS Lambda functions that extend your app with custom code for external API integrations, AI processing, webhooks, and complex business logic. Functions can be written manually or generated with AI from a natural language prompt.

🔹 People

Where you can manage access and permissions for your app.

🔹 Settings

Control your app's settings and core information here, including privacy and publish status, custom header code and more.


RELEASE

🔹 Publish

Shows your app's publish information (live URL, QR code to preview on a device) and more. It also includes deployment controls and information — you'll need to sign up to a deployment plan to get your app into one of the app stores.

🔹 Tests

Create and run reusable Release Tests for important app workflows before you publish. The Tests section includes saved test definitions, manual authoring, viewport targets, and run history.

🔹 Versions

Buzzy includes version control so you can roll back to previous versions if needed.

Last updated