Start Free Get a Demo

Revyl Atlas flow

Calm Home to Auth — Log In (Email) flow

Calm's home to auth — log in (email) flow moves users from Home to Auth — Log In (Email) across 10 mapped iOS app screens. Use this path for mobile UX teardown work, QA coverage planning, and AI agent navigation context.

10Screens
pathFlow type
iOSPlatform
HomeStarts at

Research notes

Why the Calm Home to Auth — Log In (Email) flow matters

Navigation pattern This flow shows how Calm carries a user from Home to Auth — Log In (Email) 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 Auth — Log In (Email) screenshots

This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Calm Home to Auth — Log In (Email) path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.

01

Home

Step 1 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 9 UI elements on this screen.

Calm Home screen in the Home to Auth — Log In (Email) flow
Home
02

Sleep

Step 2 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 11 UI elements on this screen.

Calm Sleep screen in the Home to Auth — Log In (Email) flow
Sleep
03

Discover

Step 3 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 10 UI elements on this screen.

Calm Discover screen in the Home to Auth — Log In (Email) flow
Discover
04

Reflections

Step 4 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 6 UI elements on this screen.

Calm Reflections screen in the Home to Auth — Log In (Email) flow
Reflections
05

Mood Check-In — Intro

Step 5 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 3 UI elements on this screen.

Calm Mood Check-In — Intro screen in the Home to Auth — Log In (Email) flow
Mood Check-In — Intro
06

Mood Check-In — Emotion Select

Step 6 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 14 UI elements on this screen.

Calm Mood Check-In — Emotion Select screen in the Home to Auth — Log In (Email) flow
Mood Check-In — Emotion Select
07

Mood Check-In — Tags & Note

Step 7 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 15 UI elements on this screen.

Calm Mood Check-In — Tags & Note screen in the Home to Auth — Log In (Email) flow
Mood Check-In — Tags & Note
08

Auth — Select Sign-In Method

Step 8 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 5 UI elements on this screen.

Calm Auth — Select Sign-In Method screen in the Home to Auth — Log In (Email) flow
Auth — Select Sign-In Method
09

Auth — Create Account (Email)

Step 9 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 6 UI elements on this screen.

Calm Auth — Create Account (Email) screen in the Home to Auth — Log In (Email) flow
Auth — Create Account (Email)
10

Auth — Log In (Email)

Step 10 in the Calm Home to Auth — Log In (Email) flow. Atlas detected 6 UI elements on this screen.

Calm Auth — Log In (Email) screen in the Home to Auth — Log In (Email) flow
Auth — Log In (Email)

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

More Calm mobile app journeys