What screens are in the Finch Do a Focus breathing session flow?

This Atlas flow includes Home — with active adventure, Hamburger drawer — top (Account + Features), Activities hub, Breathe — Focus category, Focus Breathing — intro modal, Focus Breathing — setup, Focus Breathing — active session, Focus Breathing — paused, Focus Breathing — Exit? confirm.

What can teams learn from this Finch flow?

The flow helps teams inspect real mobile app navigation, compare product patterns, plan QA coverage, and give AI agents reliable app context.

Revyl Atlas flow

Finch Do a Focus breathing session flow

Open Activities > Breathe, pick Focus (4-4-4-4 box breathing), walk the intro → setup → active session → pause → exit confirm.

View full report Open map

9Screens

Self-careFlow type

iOSPlatform

Home — with active adventureStarts at

Research notes

Why the Finch Do a Focus breathing session flow matters

Navigation pattern This flow shows how Finch carries a user from Home — with active adventure to Focus Breathing — Exit? confirm 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

Finch Do a Focus breathing session screenshots

This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Finch Do a Focus breathing session path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.

Home — with active adventure

Step 1 in the Finch Do a Focus breathing session flow. Atlas detected 8 UI elements on this screen.

Hamburger drawer — top (Account + Features)

Step 2 in the Finch Do a Focus breathing session flow. Atlas detected 17 UI elements on this screen.

Activities hub

Step 3 in the Finch Do a Focus breathing session flow. Atlas detected 10 UI elements on this screen.

Breathe — Focus category

Step 4 in the Finch Do a Focus breathing session flow. Atlas detected 10 UI elements on this screen.

Focus Breathing — intro modal

Step 5 in the Finch Do a Focus breathing session flow. Atlas detected 10 UI elements on this screen.

Focus Breathing — setup

Step 6 in the Finch Do a Focus breathing session flow. Atlas detected 10 UI elements on this screen.

Focus Breathing — active session

Step 7 in the Finch Do a Focus breathing session flow. Atlas detected 4 UI elements on this screen.

Focus Breathing — paused

Step 8 in the Finch Do a Focus breathing session flow. Atlas detected 5 UI elements on this screen.

Focus Breathing — Exit? confirm

Step 9 in the Finch Do a Focus breathing session flow. Atlas detected 4 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