What screens are in the Finch View mood trend flow?

This Atlas flow includes Home — with active adventure, Hamburger drawer — top (Account + Features), Insights — analytics dashboard, Mood breakdown chart.

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 View mood trend flow

From the drawer, open Insights and drill into the Mood Breakdown chart (past month vs last week vs this week).

View full report Open map

4Screens

AnalyticsFlow type

iOSPlatform

Home — with active adventureStarts at

Research notes

Why the Finch View mood trend flow matters

Navigation pattern This flow shows how Finch carries a user from Home — with active adventure to Mood breakdown chart 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 View mood trend screenshots

This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Finch View mood trend 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 View mood trend flow. Atlas detected 8 UI elements on this screen.

Hamburger drawer — top (Account + Features)

Step 2 in the Finch View mood trend flow. Atlas detected 17 UI elements on this screen.

Insights — analytics dashboard

Step 3 in the Finch View mood trend flow. Atlas detected 12 UI elements on this screen.

Mood breakdown chart

Step 4 in the Finch View mood trend flow. Atlas detected 6 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