Visual application specification

Design the application.
Specify the implementation.

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.

Artifact
Typed project specification
Canvas
Real Forma HTML + CSS
Application authority
F# + Ordo
Browser boundary
Limen
Why this exists

Stop handing implementation teams a picture of an application.

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.

01

Real components

The preview uses the same Forma patterns and CSS the implementation consumes. Studio does not maintain a second visual copy.

02

Linked pages

Pages have stable identities and routes. Links form an explicit navigation graph that can be previewed and validated before application code exists.

03

Machine-readable handoff

The saved artifact describes pages, components, properties, tokens, links, scenarios, obligations, and validation findings without requiring screenshot interpretation.

Workflow

From composition to specification

  1. 01

    Create pages

    Give each page a stable ID and, when appropriate, an application route.

  2. 02

    Compose with Forma

    Add canonical components, configure legal properties, bind tokens, and use named slots instead of arbitrary canvas pixels.

  3. 03

    Connect the flow

    Link component actions to target pages or external destinations. Studio validates broken and unreachable paths.

  4. 04

    Stress the design

    Preview at 320px through desktop widths, switch themes, and apply loading, empty, error, and long-content scenarios.

  5. 05

    Hand off structure, not pixels

    Export the typed project for developers, agents, CI, and future tooling.

A different canvas

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
Architecture

Each layer owns one kind of truth.

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.

What it is not

Not Illustrator

No goal of becoming a freehand vector or photo editor.

Not a second Forma

Canonical component internals stay in Forma rather than being forked inside Studio.

Not hidden business logic

A convincing prototype never licenses Studio to invent application rules.

Not screenshot handoff

Images may communicate a design, but the typed specification remains authoritative.

Current status

The contract is being built first.

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 ↗