Staging environment — entry points
| POS — Conversational Thread | v1 | Adapts the full POS purchase flow into a conversational thread pattern. Each completed step collapses into a compact confirmed row at the top; the active step floats below as a new card. Uses /pos stub data and the existing component library as design reference. Explores whether this pattern reduces cognitive overhead for booth agents during high-traffic periods compared to the current multi-page linear flow. |
| Date/Performance/Seat Explorer | v1 | Focused on finding the best seats across a range of dates. The agent can quickly flip between dates, compare availability across performances, and walk the customer through seat options without losing context. Built on the StackedLayout + SidebarLayout block components with tabs for switching between views. |
| TKTS Booth — Conversation vs Tabs UX | v1 | Side-by-side comparison of two UX paradigms for the TKTS booth sell flow. Exploration A ("Conversation") uses a linear, receipt-style thread where each completed step locks into a summary row and the next step appears as a card below. Exploration B ("Tabs") uses a sidebar + breadcrumb-trail layout with focused cards that replace in place. Both cover the full 5-step sell flow: show selection, performance, seat map, Merchant payment handoff, and order confirmation. Includes orders list and reports views. |
| Mobile Threads & Steps | v1 | Mobile-focused prototypes: a conversational thread model (A) and a step-by-step wizard model (B). Designed to compare how each pattern handles progressive disclosure on small screens. |
| Operations Dashboard | v1 | Testing Dashboard prototype. |
| TKTS Booth System (Basic) | v1 | Sass-style prototype of the TKTS booth point-of-sale system. Covers the core booth management workflow: shift login, show selection, and ticket selling. |
| TKTS Thread Purchasing | v1 | Conversational thread (vertical) presentation of payment steps. Covers the full ticket-selling workflow: shift login, show/performance/seat selection, Merchant payment handoff, order history, and reporting (hourly, daily, weekly closeout, transaction log). |