Introduction
Real apps built with Axiom, and the ones we're building next.
Nothing shipped yet
Axiom is in phase 1. None of these apps exist as code today. They are the proof we owe the system: each one is chosen to stress a different part of it, and this page fills up as they ship.
A component library proves itself in a real app, not in a catalog. Every app below is a whole product, built only with Axiom components and the same tokens any consumer gets. If a screen needs something the system doesn’t have, that gap becomes a component, a behavior or a pattern rather than a one-off file inside the app.
The apps
The reference app: one screen per component, light and dark side by side, every styling variant running from the same props.
A habit tracker. Long lists you check off, reorder by dragging and clean up in bulk.
Shared expenses. Numeric entry, split rules, and actions that stay cancellable for a few seconds.
A city guide. A map under a sheet that snaps, plus the full search flow from field to results.
A reader with notes. Where type scale, reading themes and text selection get tested for real.
A neighbourhood shop. Browse, product page, cart and checkout, built on the commerce blocks.
What each app has to prove
| App | The question it answers |
|---|---|
| Axiom Demo | Do all the components exist, in every state, in every styling variant? |
| Tempo | Do gestures survive a list that scrolls, reorders and selects at once? |
| Tally | Does a form hold up against the keyboard, the numeric pad and a mistake? |
| Atlas | Can a sheet, a map and a search field share one screen without fighting? |
| Chapter | Do the typography and color tokens hold a whole reading surface? |
| Corner | Can a real purchase flow be assembled from blocks alone? |
Building your own
Nothing here is a template to fork. Axiom is copied into your project file by file with the CLI, so the apps below are read as evidence, not as a starting repo. Ship one and open an issue: this page is meant to hold your app too.