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

# App Builder tour

The App Builder is where you build one App: its logic, its pages, its look and its data. You open it from the App Manager, and it works on that App until you leave.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-493b7b00a5d4b5c5cfdd89f9554fca7ed986b5de%2Fbuilder-tour.png?alt=media" alt="The App Builder: the top bar with its editors and Test and Deploy, the Explorer with the Functions tab, the Flowboard with its executors and mini map, the Page editor at the right, and the Console open on the assistant"><figcaption></figcaption></figure>

## The areas

The Builder is one workbench, and the App editor is its main view: the [Flowboard](https://docs.heisenware.com/app-builder/app-builder/flowboard.md) in the middle, the [Page editor](https://docs.heisenware.com/app-builder/app-builder/page-editor.md) on the right, the Explorer on the left and the Console at the bottom.

* **The top bar** holds four editors: the **App editor**, the [Database editor](https://docs.heisenware.com/app-builder/app-builder/database-editor.md), the [Theme editor](https://docs.heisenware.com/app-builder/app-builder/theme-editor.md) and the [Template editor](https://docs.heisenware.com/app-builder/app-builder/template-editor.md). Next to them, three toggles show and hide the Explorer, the Console and the Page editor. Then the settings and the help menu. On the right: the deployed version, **Test** and **Deploy**, see [Test and deploy](https://docs.heisenware.com/app-builder/app-builder/test-and-deploy.md).
* **The Explorer** is the panel on the left, with five tabs on its icon rail: [Functions](https://docs.heisenware.com/app-builder/app-builder/functions.md), [Pages and actions](https://docs.heisenware.com/app-builder/app-builder/pages.md), [Files](https://docs.heisenware.com/app-builder/app-builder/files.md), [Variables](https://docs.heisenware.com/app-builder/app-builder/variables.md) and [Endpoints](https://docs.heisenware.com/app-builder/app-builder/endpoints.md). A click on the active icon closes the panel, a click on another opens that tab.
* **The Flowboard** carries the logic of the whole App. You drag functions onto it, where each becomes an executor, and wire the executors together.
* **The Page editor** is where you design each page, for every screen the App serves.
* **The Console** at the bottom holds the [assistant](https://docs.heisenware.com/app-builder/app-builder/assistant.md), which builds with you. An installation without an assistant has no Console and no toggle for it.

The footer along the bottom edge names who is signed in, the App, the workspace, the App's language, which is set in the [App Manager](https://docs.heisenware.com/app-manager/app-manager.md), and the base theme its look is compiled from.

While a test run is on, the four editors are locked. Stop the test to go on building.

## How the pieces fit

Logic and pages are built separately and joined by **links**. A button's click fires an executor's trigger, an input field writes an executor's input, an executor's output feeds a gauge, a chart or a widget's color. There is no glue code: a value that arrives moves on by itself.

* [Executors and instances](https://docs.heisenware.com/concepts/executors-and-instances.md): what a node on the Flowboard is made of.
* [Triggers and wires](https://docs.heisenware.com/concepts/triggers-and-wires.md): what makes an executor run.
* [Widgets and links](https://docs.heisenware.com/concepts/widgets-and-links.md): the three kinds of link and where each one leads.
* [Scopes](https://docs.heisenware.com/concepts/scopes.md): which users see which value.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-1d8d1eac7097bf4cd68827cd186f63f9851d551f%2Fwidget-link.png?alt=media" alt="A modifier on the Flowboard whose item reads set value, with the value box it feeds standing in the Page editor beside it"><figcaption><p>A link: the modifier's item on the left, the widget it feeds on the right</p></figcaption></figure>

## Settings

The gear in the top bar opens **App Builder Settings**. They belong to you and to this browser, not to the App.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-1718990583ee54e123412e51598753f292a525f3%2Fbuilder-settings.png?alt=media" alt="The App Builder settings: the Flowboard settings over the developer settings" width="420"><figcaption></figcaption></figure>

Under **Flowboard Settings**:

* **Viewport Controls**: how the board pans and zooms. `design-tool-like` behaves like Figma or Miro, `google-maps-like` like a map.
* **Grid Size**: the grid nodes snap to. `0` switches snapping off.
* **Invert WASD Controls**: by default W is up and S is down. Inverted, they swap.
* **WASD Pan Speed** and **WASD Zoom Speed**: how far the WASD keys move the board, and the Q and E keys zoom it.
* **Default Modifier Type**: which language a new [modifier](https://docs.heisenware.com/app-builder/app-builder/flowboard/modifier.md) starts in, JSONata or JavaScript.
* **Show Mini Map**: the overview in the bottom right corner of the board.

Under **Developer Settings**:

* **Debug Backend**: shows the platform's own agents and control classes in the Functions explorer. They run the platform, they are not building blocks.
* **Show Database Visualizer**: whether the Database editor's icon sits in the top bar.
* **Auto expand sections during spotlight effect**: experimental.

{% hint style="danger" %}
Leave **Debug Backend** off unless Heisenware support asks you to switch it on.
{% endhint %}

## Where to go next

* [Flowboard](https://docs.heisenware.com/app-builder/app-builder/flowboard.md), and the extensions on an output: [modifier](https://docs.heisenware.com/app-builder/app-builder/flowboard/modifier.md), [filter](https://docs.heisenware.com/app-builder/app-builder/flowboard/filter.md), [recorder](https://docs.heisenware.com/app-builder/app-builder/flowboard/recorder.md), [error handler](https://docs.heisenware.com/app-builder/app-builder/flowboard/error-handler.md).
* The Explorer: [Functions](https://docs.heisenware.com/app-builder/app-builder/functions.md), [Pages and actions](https://docs.heisenware.com/app-builder/app-builder/pages.md), [Files](https://docs.heisenware.com/app-builder/app-builder/files.md), [Variables](https://docs.heisenware.com/app-builder/app-builder/variables.md), [Endpoints](https://docs.heisenware.com/app-builder/app-builder/endpoints.md).
* [Page editor](https://docs.heisenware.com/app-builder/app-builder/page-editor.md), [Theme editor](https://docs.heisenware.com/app-builder/app-builder/theme-editor.md), [Template editor](https://docs.heisenware.com/app-builder/app-builder/template-editor.md), [Database editor](https://docs.heisenware.com/app-builder/app-builder/database-editor.md).
* [The assistant in the Builder](https://docs.heisenware.com/app-builder/app-builder/assistant.md).
* [Test and deploy](https://docs.heisenware.com/app-builder/app-builder/test-and-deploy.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.heisenware.com/app-builder/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.
