Scenic Route Discovery
Design a navigation option that trades the fastest route for interesting, safe stops matched to a traveler's available time.
The brief
Understand the problem
Background
Conventional navigation optimizes for arrival time. On a flexible day, travelers may prefer a route with viewpoints, independent shops, architecture, or quiet walking streets, provided the detour is predictable.
User context
Jon has ninety minutes to walk from his hotel to a museum that is normally twenty-five minutes away. He enjoys modern architecture and coffee, but wants to avoid steep hills.
Product problem
Recommendations must form a coherent route rather than a loose list. The product also needs to communicate the cost of each detour and adapt when time changes.
Objective
Create a preference-led scenic route flow with transparent timing and in-route adjustments.
What to design
Define the experience
Required experience
- Interest and time setup
- Route comparison
- Guidance with optional stops
Screens and states
- Route preferences
- Fast versus scenic comparison
- Active route
- Stop detail
Core user flow
Follow the critical path
- 01
Jon enters his destination and arrival deadline
- 02
He chooses architecture, coffee, and low incline
- 03
He compares two scenic options
- 04
He skips a crowded stop and the route updates
Product rules
Requirements and constraints
Requirements
- Show total time and added distance
- Explain why each stop was selected
- Allow stops to be skipped without ending navigation
- Respect mobility and safety preferences
Constraints
- Opening hours may change
- Some route segments lose data coverage
- The arrival deadline cannot be exceeded without confirmation
Reality check
States worth considering
Ready-to-use content
Mock data
Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.
Suggested stops
- Civic Library facade, 8 minute detour
- Kopi Corner, open until 18:00, 6 minute detour
- Riverside footbridge, step-free route
Finish line
What to deliver
- A four-screen mobile flow
- A route comparison component showing the value and cost of each option
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.