What you get
You describe your product as a set of contracts — your brand, your components, how they behave, how they move, how screens are composed — and The Wyrding Way generates the real code for both web and Flutter. You write a thing once; both platforms get a faithful copy.
The whole system runs on one idea: contracts plus conformance. You author a contract, the tooling generates from it, and a build fails the moment your two platforms disagree. You find drift at build time, not in production.
How it fits together
Your brand sets the colors, type, spacing and motion. Your components consume those tokens and present your UI. Behavior and motion give a component state and movement that feel identical on either platform. Layout composes components into screens. Each layer is a contract the next layer builds on.
You don't wire any of the cross-platform machinery by hand. You author at the top — a brand file, a component, a behavior — and the generators carry it down to web and Flutter for you.
Your journey
1. Quickstart
Available nowGet a product building on The Wyrding Way and render your first component on web and Flutter.
2. Define your brand
Available nowDeclare your colors, type, spacing and motion once, in a file you and your agents can write.
3. Build with components
Available nowUse the component set, or add your own that stays correct across web and Flutter.
4. Bring it to life
In previewGive a component state and motion that behaves the same on both platforms, from one source.
5. Compose screens
ComingLay out components into screens that render on web and Flutter — and, soon, author it all in Studio.
Where these facts come from
The component list, command reference and availability tags on this site are generated from the published foundation — not hand-typed — so they can't fall out of date. Reflects the foundation at 67111ac.