Conventional search starts with a region and leaves travel-time calculation to the guest. The platform must also hold inventory and avoid double booking.
Project case study4 / 7Self-initiated concept
Booking service
Тиходаль
A beautiful place you can actually reach in a couple of hours.
I designed a mobile-first short-trip search with map, calendar and a transparent booking builder.
Working frontend prototype1
Task and constraints
City residents planning spontaneous short weekend escapes.
My goal was to make travel time a first-class filter and carry the mobile journey from idea to a clear booking.
Prototype scope
These figures describe concept coverage, not business results.up to 2 hcore search intent
15 minhold scenario
mobile firstprimary context
2
Key decisions
Each decision answers a specific product question instead of existing for visual effect.
1
Time before region
I begin with a realistic journey duration, then refine property type, dates and budget.
2
The map explains choice
Route, duration and reachable area appear with results without overwhelming the phone screen.
3
Booking as a state system
I expose hold, extras, total and error recovery instead of designing only the happy path.
3
What you can test
Capabilities marked “Available in the demo” open their exact working screen.
1Travel-time and map searchAvailable in the demoOpen screen2Calendar and booking builderAvailable in the demoOpen screen3Additional servicesAvailable in the demoOpen screen
4Payments, iCal and host accountDesigned, not connectedNo live demo screen
4
Interface foundation
The material behind the product structure, states and logic.
1
Booking state machine
2
Commission model
3
Role matrix
5 / Working prototype
Open interactive prototype
The core journey works in the browser. This is a demonstration build: entered data is neither sent nor stored.
Next case study
5MorrowlaneSaaS product interface