Why the Runna Jump to a different plan week flow matters
Navigation patternThis flow shows how Runna carries a user from Today — Home to Today — Week Selector across real app states.
Testing coverageThe screen path gives QA and product teams concrete screens to verify, including visible UI density, transition order, and repeated mobile states.
Agent groundingAtlas makes this journey usable as navigation context for AI agents that need to understand the app before executing mobile tasks.
Screen path
Runna Jump to a different plan week screenshots
This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Runna Jump to a different plan week path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.
01
Today — Home
Step 1 in the Runna Jump to a different plan week flow. Atlas detected 14 UI elements on this screen.
Today — Home
02
Today — Week Selector
Step 2 in the Runna Jump to a different plan week flow. Atlas detected 1 UI elements on this screen.
Today — Week Selector
How to use it
Apply this flow to product and testing work
For product researchUse 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 planningTurn 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.