Busflow Docs

Internal documentation portal

Skip to content

@busflow/driver

Status: Scaffold — not yet implemented

Purpose

Driver Operations PWA — daily assignments, live passenger manifest, QR check-in, offline-first.

Tech Stack

  • Framework: Quasar (PWA + Capacitor)
  • Offline: Aggressive local caching via Service Workers
  • Design: @busflow/ui-core with .theme-driver (oversized touch targets, dark mode)

Key Features (planned)

  • daily-assignments/ — View shift schedule, trip details
  • passenger-checkin/ — QR scanner for Wallet passes/PDFs
  • missing-passengers/ — Alert dispatcher about no-shows
  • bordverkauf/ — Onboard POS (seat-linked food/beverage)
  • receipt-scanner/ — AI OCR receipt capture
  • vehicle-inspection/ — Digital pre-trip checklist
  • commercial-routing/ — Heavy-coach navigation

Architecture

Follows Feature-Sliced Design (simplified flat variant).

Public API / Entrypoints

  • Planned app entrypoint: Quasar PWA / Capacitor mobile shell.
  • Offline sync boundaries must remain explicit and testable.

Key Commands

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

Common Pitfalls

  • Assume unreliable connectivity and large touch targets by default.
  • Do not block check-in or safety workflows on optional online services.

Internal documentation — Busflow