01
Welcome — House Rules
Step 1 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 3 UI elements on this screen.
Revyl Atlas flow
Tinder Sign up — basics (name → bio) flow
House Rules → name → birthday → gender → orientation → who you want to see → distance → relationship goal → education → lifestyle → personality → interests → photos → bio.
18Screens
onboardingFlow type
iOSPlatform
Welcome — House RulesStarts at
Research notes
Why the Tinder Sign up — basics (name → bio) flow matters
Navigation pattern This flow shows how Tinder carries a user from Welcome — House Rules to Onboarding — Bio (filled) 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
Tinder Sign up — basics (name → bio) screenshots
This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the Tinder Sign up — basics (name → bio) path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.
02
Onboarding — First Name
Step 2 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 4 UI elements on this screen.
03
Onboarding — Welcome <Name> Modal
Step 3 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 2 UI elements on this screen.
04
Onboarding — Birthday
Step 4 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 3 UI elements on this screen.
05
Onboarding — Gender
Step 5 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 8 UI elements on this screen.
06
Onboarding — Sexual Orientation
Step 6 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 10 UI elements on this screen.
07
Onboarding — Interested In
Step 7 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 7 UI elements on this screen.
08
Onboarding — Distance Preference
Step 8 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 3 UI elements on this screen.
09
Onboarding — Relationship Goal
Step 9 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 8 UI elements on this screen.
10
Onboarding — Education Level
Step 10 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 10 UI elements on this screen.
11
Onboarding — Lifestyle Habits
Step 11 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 7 UI elements on this screen.
12
Onboarding — What else makes you-you
Step 12 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 6 UI elements on this screen.
13
Onboarding — Interests
Step 13 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 8 UI elements on this screen.
14
Onboarding — Add Photos
Step 14 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 4 UI elements on this screen.
15
Onboarding — Photos (2 of 6)
Step 15 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 5 UI elements on this screen.
16
Onboarding — Share More About Yourself
Step 16 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 5 UI elements on this screen.
17
Onboarding — Add Bio
Step 17 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 4 UI elements on this screen.
18
Onboarding — Bio (filled)
Step 18 in the Tinder Sign up — basics (name → bio) flow. Atlas detected 4 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