Screens
Atlas captures of the onboarding screens, in journey order. Click any screen for full pixel-size, telemetry id, and re-capture command. The same screens appear inline next to each step on the Flow page.
Manifest generated 2026-05-26T17:38:07.335Z.
Registry order:
docs/atlas/registry/screens.yaml.
-
Welcomeonboarding-welcometoday -
Sign inonboarding-signintoday -
Journey statusonboarding-journeytoday -
Genderonboarding-gendertoday -
Birthdayonboarding-birthdaytoday -
Heightonboarding-heighttoday -
Weightonboarding-weighttoday -
Goal weightonboarding-goal-weighttoday -
Activity levelonboarding-activitytoday -
HealthKit benefitsonboarding-healthkittoday -
Medicationonboarding-medicationtoday -
Doseonboarding-dosetoday -
Frequencyonboarding-frequencytoday -
Injection dayonboarding-injection-daytoday -
Schedule timeonboarding-schedule-timetoday -
Last injectiononboarding-last-injectiontoday -
Your plan is readyonboarding-completiontoday
Unmapped Atlas screens
These Atlas screens exist in the registry but no flow-graph step in
src/lib/onboardingFlow.ts
currently references them. Either the flow graph is stale, or the
Atlas entry covers a screen that no longer ships — investigate and
either map or retire.
- onboarding-watch
- onboarding-healthkit-nowatch
How this works
-
Atlas captures iPhone-simulator screenshots of each onboarding screen
nightly (
.github/workflows/atlas-nightly.yml) or on demand via./scripts/refresh-atlas.sh --kind screens. -
Captures land in
.artifacts/runs/(gitignored). -
cd onboarding-dashboard && bun run sync-screensresizes the latest capture per ID to a 480-pixel-wide JPEG and writes a manifest with the capture timestamp. - This page (and the inline thumbnails on Flow) read the manifest at build time and serve the JPEGs through Cloudflare Pages.