> For the complete documentation index, see [llms.txt](https://docs.buzzy.buzz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buzzy.buzz/getting-started-with-buzzy/new-buzzy-ai-v3/2.-previewing-your-app.md).

# 2. Previewing Your App

<figure><img src="/files/wNuQd9Vy8Ib67rsFoHpO" alt=""><figcaption><p>Preview your app in the Workspace Editor view</p></figcaption></figure>

After submitting a prompt, Buzzy generates an app structure, including screens, data, and UI components.

The Buzzy Workspace will switch to the Workspace Editor view, which has a navigation panel on the left that lets you access your entire app's structure, including brief, data model, design, settings and more. See below for more.

The App Editor will default to the Design view, were you'll see a preview of your app when it's ready. Not every screen will be generated at first - the editor will prompt you to create the missing ones when needed.

You can also **preview a live version of the generated app** by clicking the **Live view** button in the top toolbar. This opens a live version of the app using real data and navigation.

**Preview features:**

* Test real interactions (e.g. forms, navigation)
* View responsive layouts
* Interact with mock or connected data


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.buzzy.buzz/getting-started-with-buzzy/new-buzzy-ai-v3/2.-previewing-your-app.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.