Shared app definition
Screens, data, automations, and API connections are structured documents. The visual editor works on those same documents — one source of truth.
Visual editing and text files
One app definition, three ways to edit it: the visual editor, readable text files, or AI. Changes stay in sync because every tool edits the same definition.
What it gives you
- Visual editors for screens, automations, and data models
- Text files are human-readable and reviewable in version control
- Free to move between editing styles at any time
- One shared definition means fewer surprises between design and runtime
A worked concept
A builder lays out a review screen in the visual editor, a teammate adjusts the underlying layout file in a pull request, and the AI drafter proposes an extra validation step — all against the same document.
How it works
Reviewable changes
Because app definitions are structured text, changes can be reviewed like code — part of the planned review and release workflow.
Already running underneath
The platform already runs defined screens and automations today; the visual editor and file tooling are the planned authoring layer on top.
Worth knowing
- The visual editor and the review/release workflow are still being built
- App definitions are purpose-built for the Floyant platform
- Custom code lives in your own connected services — always under your control