01
Home
Step 1 in the Calm Home to Check-In — Discard Confirm Dialog flow. Atlas detected 9 UI elements on this screen.
Revyl Atlas flow
Calm Home to Check-In — Discard Confirm Dialog flow
Calm's home to check-in — discard confirm dialog flow moves users from Home to Check-In — Discard Confirm Dialog across 6 mapped iOS app screens. Use this path for mobile UX teardown work, QA coverage planning, and AI agent navigation context.
6Screens
pathFlow type
iOSPlatform
HomeStarts at
Research notes
Why the Calm Home to Check-In — Discard Confirm Dialog flow matters
Navigation pattern This flow shows how Calm carries a user from Home to Check-In — Discard Confirm Dialog across real app states.
Testing coverage The screen path gives QA and product teams concrete screens to verify, including visible UI density, transition order, and repeated mobile states.
Agent grounding Atlas makes this journey usable as navigation context for AI agents that need to understand the app before executing mobile tasks.
Screen path
Calm Home to Check-In — Discard Confirm Dialog screenshots
This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Calm Home to Check-In — Discard Confirm Dialog path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.
02
Sleep
Step 2 in the Calm Home to Check-In — Discard Confirm Dialog flow. Atlas detected 11 UI elements on this screen.
03
Discover
Step 3 in the Calm Home to Check-In — Discard Confirm Dialog flow. Atlas detected 10 UI elements on this screen.
04
Mindful Tools
Step 4 in the Calm Home to Check-In — Discard Confirm Dialog flow. Atlas detected 7 UI elements on this screen.
05
Auth — Select Sign-In Method
Step 5 in the Calm Home to Check-In — Discard Confirm Dialog flow. Atlas detected 5 UI elements on this screen.
06
Check-In — Discard Confirm Dialog
Step 6 in the Calm Home to Check-In — Discard Confirm Dialog flow. Atlas detected 2 UI elements on this screen.
How to use it
Apply this flow to product and testing work
For product research Use the ordered path to understand which screens appear before and after key actions, how much interface density the user sees, and where the app introduces extra decisions or interruptions.
For QA planning Turn each screen in the path into a coverage checkpoint. The screenshot sequence helps teams verify expected states, navigation transitions, and UI inventory without manually rediscovering the journey.
Related flows