> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/app-builder.md).

# App builder

The App builder is where you build user-facing applications — dashboards, forms, portals, and tools that your team or customers open and use.

The App builder is the interface you work in when you are building an app. An app is something people open and use — a dashboard, a form, a portal, a reporting tool. The Riff agent builds it with you.

## Layout

Three zones:

* **Topbar** — project name, tab row, [History](/reference/shared/version-history.md), Deploy button
* **Content area** — changes per active tab
* **Console / Logs panel** — slides up from the bottom on demand

## Default tabs

These tabs are open when you first enter the App builder:

| Tab                                            | What it is                                                                  |
| ---------------------------------------------- | --------------------------------------------------------------------------- |
| [Preview](/reference/app-builder/preview.md)   | Your app running as you build it — interact with it exactly as a user would |
| [Tasks](/reference/app-builder/tasks.md)       | Shared task board between you and the Riff agent                            |
| [Database](/reference/app-builder/database.md) | Browse your app's database and ask the Riff agent to work with your data    |
| [Secrets](/reference/shared/secrets.md)        | Store API keys and credentials                                              |
| [Storage](/reference/shared/storage.md)        | Upload and manage files                                                     |

## Additional tabs

Open any of these via the **+** button in the topbar:

| Tab                                                          | What it is                                             |
| ------------------------------------------------------------ | ------------------------------------------------------ |
| [Automations](/reference/shared/triggers-and-automations.md) | Schedule your app's backend endpoints to run on a cron |
| [Integrations](/reference/shared/integrations.md)            | Connect your app to external services                  |
| [Access](/reference/app-builder/access.md)                   | Manage access to your app                              |
| [Code Editor](/reference/app-builder/code-editor.md)         | Edit source code directly                              |
| [Packages](/reference/app-builder/packages.md)               | Manage frontend and backend dependencies               |

## Deploying your app

When your app is ready for real users, click **Deploy** in the topbar. See [Deploy](/reference/app-builder/deploy.md) for the full flow and pre-deployment checks.

## The Riff agent in the App builder

The Riff agent chat panel runs on the right side of the App builder. It builds your app in response to your messages. See [Riff agent chat](/reference/app-builder/riff-agent-chat.md) for what the panel contains and how to use it effectively.

## App Settings

Your app's details, workspace controls, access, agent rules, design, hosting and notifications are in App Settings: click the app name at the top left, then **Settings**. See [App Settings](/reference/app-builder/app-settings.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.riff.ai/reference/app-builder.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.