Build and ship a Fission application.

Follow the same path you will use in a real project: get an app running, understand its state and rendering model, add product work, test the actual targets, and produce release artifacts.

Put an app on screen first

The Quickstart creates a desktop app, shows you which file owns the shared product model, and explains every command before asking you to add another target.

•

Open the Quickstart

•

Understand the application model

A route through the documentation

Each stage ends with something you can run, inspect, or verify.

Stage	What you will accomplish	Evidence
Start	Create the project and run it	Working window
Learn	Understand where behaviour belongs	Explainable flow
Build	Add a real product workflow	Useful behaviour
Verify	Test shared logic and target boundaries	Reproducible evidence
Ship	Build the artifact customers receive	Qualified artifact

Find guidance by the work in front of you

You do not need to read the documentation front to back.

Build an interface

Use the layout and widgets guide for retained composition, then add responsive behaviour and a typed design system.

Manage application state

Read state, handles, and providers to choose the correct owner, then use resources and async for work outside pure component conversion.

Add platform behaviour

Start with the capability matrix and use the target shell as the explicit boundary for host-specific lifecycle, input, accessibility, and delivery work.

Diagnose and ship

Follow testing and diagnostics during development, then use build and package and the release checklist for the shipped form.