Journeys

Booking accommodation

The ordered journey demonstrates selecting/configuring a hotel, homestay or other overnight stay toward booking or ordering. A blocked/payment boundary is allowed and must not be described as completion. Mere content browsing is insufficient. Study captured mobile app examples for UI/UX research.

Compare Booking accommodation UX flows side by side

  1. Booking.com: Choose and configure a stay

    Compare properties, choose a room and rate, set room preferences, and reach the protected reservation boundary.

    Booking.com Choose and configure a stay flow preview
  2. Cleartrip: Book a hotel stay

    A captured natural-root journey establishes hotel criteria, selects a property and room, reviews the itinerary, enters traveller details, and stops safely at the visible Pay now boundary.

    Cleartrip Book a hotel stay flow preview
  3. EaseMyTrip: Book a hotel

    Search Goa stays, review a property and room rate, enter guest details, and stop before payment.

    EaseMyTrip Book a hotel flow preview
  4. MakeMyTrip: Book a hotel stay

    The end-to-end stay-booking goal, proven for a guest (not signed in) checkout on one city/property/date fixture through to the payment-instrument forms. No variant has been observed to complete a payment.

    MakeMyTrip Book a hotel stay flow preview
  5. redBus: Hotel checkout

    Choose a destination and room, review completed guest details, and reach the payment-method gate without implying payment or booking completion.

    redBus Hotel checkout flow preview