01
Home — Learn tab (path map)
Step 1 in the Duolingo Tap a locked node to see what it requires flow. Atlas detected 18 UI elements on this screen.
Revyl Atlas flow
Duolingo Tap a locked node to see what it requires flow
Tap a locked (gray) lesson node to see the feature name and what needs to be completed to unlock it.
2Screens
LearnFlow type
iOSPlatform
Home — Learn tab (path map)Starts at
Research notes
Why the Duolingo Tap a locked node to see what it requires flow matters
Navigation pattern This flow shows how Duolingo carries a user from Home — Learn tab (path map) to Locked Node Popup — Complete levels to unlock (MAX) 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
Duolingo Tap a locked node to see what it requires screenshots
This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Duolingo Tap a locked node to see what it requires path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.
02
Locked Node Popup — Complete levels to unlock (MAX)
Step 2 in the Duolingo Tap a locked node to see what it requires flow. Atlas detected 1 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