Flows and boilerplates
Multi-step flows ship a controller so you wire one component. Boilerplates arrive by CLI instead.
Three content types
| Type | What it is | How it arrives |
|---|---|---|
| Screen | One self-contained screen, one file plus the odd helper. | Copy prompt |
| Flow | An ordered set of screens with a controller, such as a 4-step onboarding. | Copy prompt |
| Boilerplate | A complete, runnable Expo app. Not published yet. | One CLI command |
Flows ship their own controller
A flow is not four loose screens for you to sequence. It ships an index.tsx that owns the step index, the answers and the transition between steps, so you wire one component into navigation rather than four.
- initialStep opens the flow part-way through, for deep links and resumed sessions.
- onComplete fires after the last step, with whatever the flow collected.
import AuroraOnboarding from './components/aurora-onboarding'
<AuroraOnboarding
onComplete={answers => {
saveOnboarding(answers)
router.replace('/home')
}}
/>Boilerplates arrive by CLI
A full app is forty files or more, plus native config. That does not fit in a paste and should not try to. Boilerplates are cloned with one command, then customized by your agent with the whole tree already on disk to read.
npx degit <repo>/registry/boilerplates/<slug> my-app
cd my-app && npm install && npx expo startThen hand it to your agent
The boilerplate page gives you a short prompt for this part. It asks for what it needs rather than guessing.
No boilerplates are published yet
Screens and flows are live today. Boilerplates are the next thing being built, and this page describes how they will arrive so you know what to expect. Nothing on the pricing page promises them until they exist.