Experiences & Activities · Documentation

User Journey

The end-to-end path through Experiences & Activities, from trigger to outcome.

Live diagram — an experience books exactly like a stay, reusing the host payment and comms shells; payment is the one simulated step.

1
Browse → book
`listExperiences` filters the generated catalog by city/POI and category. `bookExperience` creates a 0-night booking against the chosen experience, captures a simulated payment, and sends a confirmation notification — reusing the host's payment and comms shells so an experience books exactly like a stay. An `experience.booked` event is emitted on the shared bus.
2
Reuse + connections
The view is embeddable: `compact` + `onAddToTrip` let #39 Trip Planner render the same component inside the trip builder, so an experience can be added straight to an itinerary. The app owns the experiences catalog and reads shared-core `poi` / `property` / `guest_profile`; it uses the #34 payments shell, the #35 comms shell, and connects to #39.