01
Today — Home
Step 1 in the Runna Dismiss banner — see the next one flow. Atlas detected 14 UI elements on this screen.
Revyl Atlas flow
Runna Dismiss banner — see the next one flow
Tap X on the Refer-a-friend banner; the home rotates to a Sync your apps banner.
2Screens
promoFlow type
iOSPlatform
Today — HomeStarts at
Research notes
Why the Runna Dismiss banner — see the next one flow matters
Navigation pattern This flow shows how Runna carries a user from Today — Home to Today Home — Sync Banner Variant 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
Runna Dismiss banner — see the next one screenshots
This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Runna Dismiss banner — see the next one path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.
02
Today Home — Sync Banner Variant
Step 2 in the Runna Dismiss banner — see the next one 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