What screens are in the Finch Write a reflection flow?

This Atlas flow includes Home — with active adventure, Hamburger drawer — top (Account + Features), Activities hub, Reflections — Calm category, Reflection entry editor, Reflection editor — filled state, Reflection save reward (adventure speed-up).

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 Write a reflection flow

From the hamburger drawer, open Activities, pick a Reflections prompt, type an entry, save, and land on the reward sheet where Ash finds Rainbow Stones and shortens today's adventure.

View full report Open map

7Screens

Self-careFlow type

iOSPlatform

Home — with active adventureStarts at

Research notes

Why the Finch Write a reflection flow matters

Navigation pattern This flow shows how Finch carries a user from Home — with active adventure to Reflection save reward (adventure speed-up) 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 Write a reflection screenshots

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

Hamburger drawer — top (Account + Features)

Step 2 in the Finch Write a reflection flow. Atlas detected 17 UI elements on this screen.

Activities hub

Step 3 in the Finch Write a reflection flow. Atlas detected 10 UI elements on this screen.

Reflections — Calm category

Step 4 in the Finch Write a reflection flow. Atlas detected 15 UI elements on this screen.

Reflection entry editor

Step 5 in the Finch Write a reflection flow. Atlas detected 7 UI elements on this screen.

Reflection editor — filled state

Step 6 in the Finch Write a reflection flow. Atlas detected 6 UI elements on this screen.

Reflection save reward (adventure speed-up)

Step 7 in the Finch Write a reflection 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