Full native control.
Every meaningful change waits for a build, review, and release.
Native mobile onboarding as code · controlled private alpha
Ship native onboarding changes without shipping another app build.
Your coding agent composes the SwiftUI and React Native components already in your app. Weir verifies the flow against installed builds, signs it, and safely releases compatible changes.
Public support is SwiftUI and React Native/Expo only. Compatible copy, ordering, branching, themes, and experiments can ship remotely; new native component types still ship with the app.
onboarding.yml
01 / release review
Requested change
Move assessment before camera
Keep the native control unchanged.
Agent request
Move the assessment before the camera step for variant B. Keep the control unchanged.
Journey change
Welcome → Camera → Assessment → RevealWelcome → Assessment → Camera → Reveal
$ weir conform --flowId onboarding
schema · registry · rollout pass
Installed-build compatibility
iOS 118Eligible
Android 84Eligible
Android 82Refused · missing Assessment.v2
- Eligible builds receive the flow
- Refused builds keep the app baseline
3 builds checked · 2 eligible · 1 baseline fallback
Ineligible builds keep their app-shipped baseline.
Explore this product surface with deterministic demo data, then run the local loop yourself. A release review shows the changed journey, eligible builds, and exact fallback — not just a publish button. Use the replay control to step through request → conform → release. Open the demo workspace.
Public support: SwiftUI and React Native / Expo on iOS and Android.
SwiftUIReact NativeExpoiOSAndroid
The release path
A flow is code until it safely becomes product.
- 01Register
Expose the components your app already owns.
Stock primitives and custom screens form a versioned contract. Product logic stays inside the app.
- 02Author
Let an agent compose the journey in your repository.
Flow specs are inspectable artifacts, so your team can diff, review, and validate the exact experience.
- 03Release
Conform, sign, and publish a compatible flow.
Weir checks the schema and component registry before a signed artifact can reach an eligible build.
- 04Learn
Measure the journey, not just the final paywall.
A fixed event contract connects assignment, progress, outcomes, and experiment evidence.
The useful tradeoff
Remote change should not mean surrendering the product surface.
Weir is for journeys where onboarding is part of the product: assessments, cameras, calculators, native previews, gesture-led moments, and personalized reveals.
Fast remote changes.
The journey is primarily authored and rendered outside your repository.
App-owned screens. Remote composition.
Compatible changes are reviewed in Git, verified against installed builds, and delivered with a local baseline.
Weir is not a WYSIWYG editor, a generic tooltip tool, or subscription infrastructure. Keep Superwall or RevenueCat for paywalls and purchases.
Refuse safely
Remote speed needs a local answer to failure.
The v4 integration model requires an app-shipped baseline. Remote flows must match the build and its component registry before the app can render them.
Compatibility check ready.
Refused builds keep their app-shipped baseline; no remote flow renders on them.
Signed artifacts
The app verifies what it receives before treating it as a flow.
Exact compatibility
Delivery excludes components and properties an installed build did not register.
Baseline + rollback
The model retains a known onboarding path and can return to a prior release.
Kill switch
The host app can return to its native onboarding path when remote delivery is disabled.
Experiment discipline
Know which flow ran before asking which flow won.
Assignments, flow versions, step events, sample-ratio checks, and decision horizons create an evidence trail from device to result. The funnel below is illustrative — no conversion-lift claim is being made from the current dogfood apps.
start
profile
reveal
outcome
Choose an experiment arm
Select an arm to see its summary. Figures shown are illustrative, not measured lift.
SwiftUI dogfood evidenceRecorded internally · public capture not approved
Qualified integration evidence covers the app’s custom fitness assessment and plan-reveal path; it is not a public production claim.
React Native dogfood evidenceRecorded internally · public capture not approved
Qualified evidence covers the React Native integration. Complete Android device proof remains a release gate.
No conversion-lift claim is being made from the current dogfood apps. Powered outcome evidence requires sufficient production traffic. Read the exact evidence boundary
Native onboarding recipes
For onboarding that is part of the product — not a stack of generic slides.
Composition patterns, not remotely rendered templates. The app supplies the product-specific native component; Weir supplies the reviewable, compatible journey around it.
Camera-led assessment
Permission timing → app-owned capture → assessment → personalized plan reveal → paywall handoff.
CameraAssessment.v2Adaptive product setup
Intent quiz → conditional branch → app-owned product preview → permission timing → upgrade.
WorkspacePreview.v1Interactive calculation
Inputs → native calculator → personalized explanation → recommendation → purchase handoff.
ProjectionCalculator.v3Capabilities ship with the app. Compositions ship with Weir. Read the component contract.
Honest status
Building in the open, inviting partners privately.
Live private alpha
v4 API, flow delivery, and dashboard; qualified SwiftUI and React Native dogfood evidence; two pre-registered, fixed-horizon dogfood experiments now running.
Verifying now
Released-build device journeys, complete Android device proof, native custom-component capture, and the experiment readout at its fixed horizon.
Not claimed yet
Production-proven v4, publicly supported Kotlin/Compose, integration-in-minutes, or conversion lift.
Start where the agents start
Make your next onboarding change from the repository.
The toolkit is public. It scaffolds an app, authors a flow, runs the release gate, and previews the result end to end — with no account, no API key, and no server URLs.
npx -y -p weir-toolkit weir init