Martina’s original research, user flow and paper sketches survive. The final app screens are unavailable. The interface shown here is a new portfolio reconstruction based on those materials, not a recovered original or a shipped product. CHW echoes the “Cool Hotel Website” label in the sketches; hotels, photos, prices and availability are illustrative.
Original work
Research synthesis, journey mapping, user flow and sketches
Course
UX Design Institute
Design direction
Mobile hotel booking for iOS & Android
Shown here
Reconstructed UI and browser prototype
The challenge
Booking a room shouldn’t feel like solving a puzzle.
The PDF brings together three usability-test note sets, affinity clusters and a six-stage journey map. It follows entry to the mobile site, destination/date/guest selection, filters, hotels, room options and booking confirmation.
The flow explores a Paris trip for a family of three with a pet, where parking and proximity matter. It also includes guest checkout, room choices and a final booking summary.
What the research materials show
Three moments worth getting right.
Dates need to stay visible
The journey map records unexpected calendar navigation, confusion about weekday ordering and dates that required scrolling to find.
Reconstruction response
A Monday-first date picker with a highlighted arrival/departure range, month navigation and a visible summary.
Filters need to be useful
The notes describe missing or confusing options, excessive text and availability that did not always reflect selected dates.
Reconstruction response
A focused filter panel, clear result counts, persistent search criteria and a map preview tied to the same stays.
Rooms need clarity
The journey map mentions confusing pricing, membership colours and offers. Photos were used to understand the room.
Reconstruction response
Room photos and bed layouts beside the offer, visible cancellation/deposit terms and one currency through checkout.
The PDF contains three colour-coded usability-test note sets. These are qualitative observations, not population-level results. They include inconsistent weekday ordering, too much text, hard-to-find hotel locations, confusing rate types and restricted phone-country options.
The original process
Research, mapped into a journey.
Original work · The six-stage journey map from Martina’s research PDF. Select to enlarge.
The 23 sketched screens begin with guest/member entry, then move through location suggestions, a date range, adults and children’s ages, hotel filters, photo-led listings and room deals. They finish with a selection summary, contact and deposit details, payment and a clear “pack your bags” confirmation. The rebuilt prototype now follows that progression, with Map, Saved and Trips navigation.
Original work · A single sketch sheet (screens 9–11): guest counts, hotel listings and filters. The full set of 23 screens informed the reconstruction.
Reconstructed screens
A calm interface, with clear next steps.
Plan without losing context
Destination, dates, guests and practical filters sit together.
See the stay before choosing
Hotel details, bed layouts and offers appear in a useful order.
Review, then confirm
One total, clear terms and a separate demo payment step.
The surviving work shows how Martina moved from research observations to a structured journey, connected flows and low-fidelity screens. This reconstruction makes that thinking tangible.
No usability or business results are claimed for the rebuilt interface. Next steps would be to validate it with hotel-booking tasks, review native iOS and Android conventions, and iterate on what people actually struggle with.