Real components
The preview uses the same Forma patterns and CSS the implementation consumes. Studio does not maintain a second visual copy.
Visual application specification
Forma Studio lets people compose real Forma components into pages, connect those pages into flows, preview the actual responsive browser result, and save the design as a machine-readable specification.
A visual mockup is useful to humans, but it leaves component identity, responsive behavior, tokens, navigation, accessibility intent, and implementation boundaries open to interpretation. Forma Studio makes those things explicit.
The preview uses the same Forma patterns and CSS the implementation consumes. Studio does not maintain a second visual copy.
Pages have stable identities and routes. Links form an explicit navigation graph that can be previewed and validated before application code exists.
The saved artifact describes pages, components, properties, tokens, links, scenarios, obligations, and validation findings without requiring screenshot interpretation.
Give each page a stable ID and, when appropriate, an application route.
Add canonical components, configure legal properties, bind tokens, and use named slots instead of arbitrary canvas pixels.
Link component actions to target pages or external destinations. Studio validates broken and unreachable paths.
Preview at 320px through desktop widths, switch themes, and apply loading, empty, error, and long-content scenarios.
Export the typed project for developers, agents, CI, and future tooling.
General design canvas
Rectangle
+ text
+ color
+ click prototype
↓
developer interprets intent
Forma Studio
Page: Detail
Forma / Record Header
Forma / Data Grid
navigation → /edit
↓
typed implementation contract
The browser renders and performs browser capabilities. It does not own the document. Presentation comes from Forma. Studio state and legal editing transitions live in F#. Limen is the threshold between them.
No goal of becoming a freehand vector or photo editor.
Canonical component internals stay in Forma rather than being forked inside Studio.
A convincing prototype never licenses Studio to invent application rules.
Images may communicate a design, but the typed specification remains authoritative.
Current status
Forma Studio is in greenfield development. The repository begins with explicit requirements, a versioned project schema, a linked-page fixture, and the Echelon engineering capability stack before editor implementation starts.
Follow development ↗