Travel party now comes first; slots and movement are derived instead of asked directly.
See the full onboarding flow on one page.
This mirrors the SwiftUI planner onboarding as a static review surface: every live question, every option, and the current starter defaults are visible without clicking through step by step.
Who are you traveling with?
This comes first because pacing and atmosphere change a lot by group.
Just me
Flexible pacing, easy seats, and calm solo-friendly stops.
Boyfriend / girlfriend
Date-friendly pacing, atmosphere, and dinner picks.
Friends
Shareable food, lively rooms, and easy group energy.
Family
Comfort, seating ease, and mellow pacing matter.
What should your Prague plan include?
Pick every theme that matters. The app derives the day structure from this.
What do you want included?
Select as many as you like. Beer and coffee sit first because they are strong Prague signals.
Anything you want us to avoid?
Tourist traps are filtered by default. Add any extra hard no's below.
Avoid tourist traps
Preselected so the plan starts with the right local vibe.
How many days are you staying?
We'll build a concrete day-by-day plan for the full stay.
Is your current location where you're staying?
Using your base keeps each day coherent instead of zig-zagging across Prague.
Yes, use my current location
We can use it as your stay anchor.
No, I'll enter where I'm staying
Use a hotel, street, or neighborhood instead.
Where are you staying instead?
Only appears when the traveler chooses manual stay entry instead of current location.
What budget feels right?
Slide from value-first to fancy-but-worth-it places.
What kind of Prague plan do you want?
This first answer shapes the rest of the onboarding.
Food-first days
Breakfast, coffee, lunch, and dinner built into each day.
Food + nightlife
Food-led days with bars and late-night energy layered in.
Coffee-heavy roaming
Shape the trip around standout coffee stops and light food.
Flexible recommendations
Less rigid timing and more room to freestyle.
What do you want included?
Select as many as you like. These become strong positive signals in the planner.
Which parts should each day include?
The itinerary will only build the slots you enable.
Anything you want us to avoid?
Hard no's will be filtered out before the ranking starts.
How many days are you staying?
We'll build a concrete day-by-day plan for the full stay.
Is your current location where you're staying?
Using your base keeps each day coherent instead of zig-zagging across Prague.
Yes, use my current location
We can use it as your stay anchor.
No, I'll enter where I'm staying
Use a hotel, street, or neighborhood instead.
Where are you staying instead?
Only appears when the traveler chooses manual stay entry instead of current location.
How much moving around is okay each day?
This controls whether the plan stays compact or happily crosses the city for better picks.
Mostly one area
Keep each day compact and walkable.
Two areas max
A little bouncing around is fine.
Happy to cross the city
Optimize for the best places, not proximity.
What budget feels right?
We'll use this as a hard filter first and a ranking preference second.
Budget
Casual places and strong value.
Mixed
A normal mix with room for a standout meal.
Treat us
Price is secondary to quality and atmosphere.
Who is this trip for?
This nudges the algorithm toward better pacing and atmosphere.
Solo
Easy seats, calm coffee, and flexible pacing.
Couple
Room for romance, pacing, and dinner atmosphere.
Friends
Shareable, lively, and social works better.
Family
Comfort, seating ease, and mellow pacing matter.
How local should it feel?
This question still exists in the onboarding code, even though it is not currently included in the steps array.
Iconic
You want classic Prague names and polished heavy-hitters.
Polished
A refined version of Prague with less tourist noise.
Balanced
A mix of well-known and local places.
Neighbourhood
Mostly places locals would genuinely keep coming back to.
Hidden gems
Bias hard toward authentic, low-tourist, local favorites.