Journeys

Reserving a table

The ordered journey demonstrates selecting/configuring a restaurant table or dining reservation 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 Reserving a table UX flows side by side

  1. District: Book a restaurant table

    The dining reservation goal only: configure booking preferences (party size, date, time), read the loaded availability slots and select one. Guest evidence stops at the phone/OTP sign-in sheet raised on slot selection — before the booking form and before any reservation confirmation. Discovery is now published separately as family_restaurant_discovery.

    District Book a restaurant table flow preview
  2. Swiggy: Plan table booking

    Enter Dineout from signed-in Home, choose a venue, configure a table for two, review the offer and its terms, then stop before creating the reservation.

    Swiggy Plan table booking flow preview