01
Home — with active adventure
Step 1 in the Finch Explore reflection tags flow. Atlas detected 8 UI elements on this screen.
Revyl Atlas flow
Finch Explore reflection tags flow
Open Insights and tap Explore your tags to browse People / Activity / Emotion / Other tags extracted from goals and reflections.
4Screens
AnalyticsFlow type
iOSPlatform
Home — with active adventureStarts at
Research notes
Why the Finch Explore reflection tags flow matters
Navigation pattern This flow shows how Finch carries a user from Home — with active adventure to Insights — Tags explorer (empty) 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 Explore reflection tags screenshots
This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Finch Explore reflection tags path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.
02
Hamburger drawer — top (Account + Features)
Step 2 in the Finch Explore reflection tags flow. Atlas detected 17 UI elements on this screen.
03
Insights — analytics dashboard
Step 3 in the Finch Explore reflection tags flow. Atlas detected 12 UI elements on this screen.
04
Insights — Tags explorer (empty)
Step 4 in the Finch Explore reflection tags flow. Atlas detected 8 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