01
Home — main dashboard
Step 1 in the Finch Tour the bottom tabs flow. Atlas detected 18 UI elements on this screen.
Revyl Atlas flow
Finch Tour the bottom tabs flow
From Home, visit every tab in the bottom nav: Home, Quests, Shop (Outfit store), Friends, Bag, and Ash profile.
8Screens
NavigationFlow type
iOSPlatform
Home — main dashboardStarts at
Research notes
Why the Finch Tour the bottom tabs flow matters
Navigation pattern This flow shows how Finch carries a user from Home — main dashboard to Ash — pet profile (About) 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 Tour the bottom tabs screenshots
This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Finch Tour the bottom tabs path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.
02
Quests — daily + special
Step 2 in the Finch Tour the bottom tabs flow. Atlas detected 11 UI elements on this screen.
03
Shop — category selector sheet
Step 3 in the Finch Tour the bottom tabs flow. Atlas detected 7 UI elements on this screen.
04
Outfit shop
Step 4 in the Finch Tour the bottom tabs flow. Atlas detected 15 UI elements on this screen.
05
Friends — empty state with coach sheet
Step 5 in the Finch Tour the bottom tabs flow. Atlas detected 12 UI elements on this screen.
06
Friends — main (coach dismissed)
Step 6 in the Finch Tour the bottom tabs flow. Atlas detected 11 UI elements on this screen.
07
Bag — inventory hub
Step 7 in the Finch Tour the bottom tabs flow. Atlas detected 9 UI elements on this screen.
08
Ash — pet profile (About)
Step 8 in the Finch Tour the bottom tabs flow. Atlas detected 16 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