Skip to content
Floyant

Pages and forms

Compose screens from a layout system — lists, detail views, forms, and navigation connected directly to your data and automations.

What it gives you

  • Screens are defined as data, so they are consistent and generatable
  • Components connect to your data, queries, and automation actions
  • Forms carry validation, state, and submission wiring in the definition
  • The same screen definitions render in preview and live apps

A worked concept

A request list screen shows the request data, a detail panel shows the selected record, and an approval form triggers an automation — all described in a screen definition the platform renders.

How it works

Screens as definitions

Pages are structured documents: elements, data connections, and actions. The platform turns them into accessible, responsive UI.

Computed values

Built-in expressions handle computed fields, filtering, and conditional display without custom code.

Action wiring

Buttons and form submissions trigger automations and queries through the same definition the platform enforces everywhere.

Worth knowing

  • Screens are composed from a curated component catalog — consistent and dependable
  • For highly bespoke interfaces, Floyant can power your own front end through its APIs