Apps and core concepts
An App groups executable workflows with their interfaces, data, and access settings. Create one App for a project that should be configured and shared together, then add the Flows and entry points it needs.
Terms you will see
Section titled “Terms you will see”| Term | Meaning |
|---|---|
| App | The project boundary for Flows, Events, Pages, storage, data, Widgets, Templates, and access settings. |
| Project | The UI also uses this word for an App, including Project Name and Create Project. |
| Flow | Executable logic built from nodes and connections, edited visually or as FlowScript. |
| Board | The stored graph representation of a Flow. APIs use board_id, and older interfaces can still use the word Board. |
| Event node | A start node inside a Flow, such as Simple Event or Chat Event. You can run it from Studio. |
| Event | A configured App entry point that selects a Flow, node, version, execution location, and interface or trigger settings. A Page-target Event opens a Page. |
| Page | A full A2UI interface owned by a Flow. An Event and route make it available to App users. |
| Route | A path such as /support mapped to an Event within an App. |
An Event node and a configured Event are separate objects. Several Events can invoke the same node with different defaults or versions. A Flow version captures its graph and owned Pages. App data, files, and independently versioned Widgets need separate release checks; see Versioning.
Four meanings of widget
Section titled “Four meanings of widget”| Kind | Where it belongs | Guide |
|---|---|---|
| Home widget | A block in a Profile’s Home layout, such as an App collection or image | Customize Home |
| A2UI Widget | A reusable declarative component tree owned by an App and placed in interfaces | Create Widgets |
| Package micro widget | An HTML/JavaScript interface supplied by a package and hosted in an isolated frame | Package widgets |
| Native widget | A Flow-Like widget on the iOS Home Screen or macOS desktop, using cached content | Native widgets |
Choose your next task
Section titled “Choose your next task”| Goal | Start here |
|---|---|
| Build and verify a first workflow | First Flow |
| Decide where data and execution live | Offline vs. Online |
| Organize and inspect workflows | Flows and Studio |
| Add a page, chat, or trigger | Interfaces and Events |
| Store files or structured data | Storage and Data Studio |
| Configure device-specific values | Runtime variables |
| Share and release an App | Sharing and Event releases |
Use Docs for current procedures, configuration, and API reference. For a chapter-by-chapter explanation of the language and application model, start with FlowBook’s introduction, then return to the relevant Docs task when configuring a feature.