@busflow/passenger

Status: Scaffold — not yet implemented

Purpose

Standalone post-booking passenger portal. Entry via Magic Link (email/WhatsApp/Wallet). Covers the full post-purchase lifecycle: digital tickets, self-service payments, live tracking, booking modifications, and reviews.

Tech Stack

• Framework: Nuxt 3 (Mobile-optimized SPA)
• Design: @busflow/ui-core with .theme-passenger
• Auth: Passwordless Magic Link + booking code

Key Features (planned)

• Apple/Google Wallet pass display & dynamic updates
• Self-service balance payments (final payment via Magic Link)
• Invoice downloads & booking modifications
• Live bus tracking ("Where is my Bus?" ETA map)
• WhatsApp-triggered entry point
• Post-trip review requests

Architecture

Follows Feature-Sliced Design.

Public API / Entrypoints

• Planned app entrypoint: Nuxt mobile SPA reached from Magic Links, Wallet passes, and booking codes.
• Passenger-facing routes should remain token-safe and shareable only where intended.

Key Commands

• No package-specific commands yet; use the eventual app filter once package.json exists.

Related Docs

• App Structure
• Product User Journeys
• Notification Pipeline Protocol
• Commerce Schema

Common Pitfalls

• Do not expose backoffice-only booking data in passenger self-service views.
• Keep Magic Link flows compatible with email, WhatsApp, and Wallet entry points.