Add a guided tour mode to HydraHeadiPad. A visitor selects a tour for a venue, receives a welcome and a few introductory questions, and is guided from place to place. At each installation, the app loads and triggers the relevant experience, supports the interaction, then returns to the guide for a takeaway and directions to the next stop. The visit ends with a global takeaway and a thank-you.
This is the master ticket for the capability. FYI is the intended first application; more information will follow. Start development and validation with the simpler Rupelmonde case, which has two installations.
Visitor journey
Select venue/tour — choose an available tour for the venue and start a visit.
Welcome and introductory questions — introduce the visit and ask a short, configurable set of questions. Keep the answers available throughout the visit; the actual questions and how they influence the experience remain to be defined.
Guide to installation 1 — explain where to go and what to look for.
Interact with installation 1 — confirm arrival/readiness, load and trigger the appropriate experience, and let the visitor interact.
Installation 1 takeaway — return to the tour and present a short reflection or key point.
Guide to installation 2 — give directions and an introduction to the next stop.
Interact with installation 2 — load and trigger its relevant experience and support the interaction.
Installation 2 takeaway — return to the tour for the second stop's reflection or key point.
End of visit — clearly indicate that the route is complete.
Global takeaway — connect the installations into an overall reflection on the visit.
Thank you — close the visit and provide a clear finish action.
The repeating unit is guide → interact → takeaway. Support an ordered list of stops so additional venues can reuse this pattern without changing the app flow.
Scope and proposed implementation breakdown
Venue tour definition and selection: venue/tour identity, welcome, questions, ordered installation stops, directions, experience references, per-stop takeaways, closing content, global takeaway and thank-you. Determine where this content is managed and served.
Tour session and guide UI: retain the selected tour, answers, current stop and phase, and completed stops across experience launches and returns. Show clear progress and the next action.
Installation experience handoff: connect each stop to the appropriate installation and experience. Load/trigger it at the right point, show loading and failure states, and return to the same tour session afterward. Separate completion, cancellation and interruption so a failure cannot silently advance the route.
Rupelmonde content and configuration: configure the two actual installations in the agreed order, with approved directions, questions and takeaways.
Closing and reset: end-of-visit screen, global takeaway, thank-you and a clean new-visitor session. Define resume/restart behavior for interruptions and app relaunch.
Venue validation: walk the complete two-installation journey on an iPad, including failed launches and return from an experience. Confirm existing standalone experience selection still works.
FYI extension: add the FYI venue, route and experience requirements when the promised details arrive.
These are workstreams for later child tickets; this master records the overall product behavior.
Acceptance criteria for the Rupelmonde starting case
A visitor can select the Rupelmonde tour and complete the welcome/questions flow.
The guide visits exactly the two configured installations in order, with guidance before each interaction and a takeaway afterward.
Each stop loads/triggers its configured experience at the intended moment; the visitor returns to the correct stop in the same tour session afterward.
Returning from an installation does not lose the introductory answers, progress or remaining route.
Loading failure or interruption leaves the visitor at the current stop with an explicit recovery action; it does not count as completion or launch repeatedly on its own.
After the second takeaway, the app presents end of visit → global takeaway → thank-you, without an extra next-installation step.
Finishing/resetting clears the previous visitor's answers and progress.
Another venue can supply a different ordered list of stops using the same flow.
Existing integration points
The current app has a standalone experience grid (ExperienceGridView), venue-scoped experience retrieval and body discovery (HydraClusterClient), and stream start/stop/interruption handling (AppState, ContentView). The tour should coordinate these mechanisms and add a return destination for the active visit. Physical installation control may require an additional integration; do not assume that launching an iPad stream covers every installation type.
Details to fill in
Rupelmonde's exact installation identities, route order, locations and directions, and the experience/control target for each. Existing repository material mentions Castle Viewer and Mercator Talks, but their mapping and order for this tour still need confirmation.
Introductory questions, supported languages, approved welcome text, individual takeaways and the global takeaway.
What signals arrival/readiness and successful completion at each installation. Proposed simple starting point: an explicit visitor action to confirm arrival; automatic proximity triggering is not yet specified.
Whether each interaction runs on the carried iPad, controls a fixed installation, or combines both; loading/preloading and trigger timing follow from that choice.
Whether takeaways are authored content or personalized from the visit, and whether visitors can keep them afterward.
FYI venue details and any additional routing or installation requirements, to follow.