Summary
Add a Lite mode that runs entirely in-browser with no backend persistence. In Lite mode, users create an event from scratch, run dispatch locally, export CSV, and optionally wipe all local data.
Motivation
Some teams need a privacy-first workflow where no user-entered operational or patient data is sent to cloud services. Lite mode also reduces setup friction and supports low/no-connectivity operations.
Proposed solution
- Add dedicated Lite routes under /lite in the same Next.js app.
- Build a separate Lite event creation page (do not reuse cloud create flow with mode toggles).
- Lite create page should include essential setup only:
- Event name/date
- Teams
- Supervisors
- Posts (text locations; no map UI)
- Posting schedule
- Equipment
- Do not support venue presets in Lite; users create event setup each session/event.
- Generate a local event ID in-browser and persist data locally (IndexedDB recommended).
- Route from Lite create to Lite dispatch using local ID (/lite/events/[localEventId]/dispatch).
- Add CSV export directly from Lite dispatch/end-event flow.
- Add “Wipe local data” action to clear all Lite records.
- Ensure Lite mode has no Firebase/Auth/Firestore/DataConnect writes or reads for event data.
Alternatives considered
- Reusing existing cloud event create/dispatch pages with conditional branches. Rejected due to heavy Firebase coupling and higher risk of accidental backend writes.
- Storing “non-HIPAA” setup data in backend while keeping patient data local.
Rejected for Lite v1 to keep guarantees simple: no user-entered Lite data on backend.
Mockups / Examples
- User opens /lite
- User clicks Start Lite Mode
- User completes Lite event creation (no map/presets)
- User is taken to Lite dispatch
- User exports CSV
- User optionally wipes local data
Acceptance criteria
- Lite routes are accessible without cloud authentication.
- Lite mode stores event/dispatch data locally in-browser only.
- Lite mode performs zero Firebase/Auth/Firestore/DataConnect requests for Lite event data.
- Lite create supports teams, supervisors, posts, schedule, and equipment without maps/presets.
- Lite dispatch works from locally created event data and persists across page refresh.
- CSV export includes dispatch logs needed for post-event reporting.
- “Wipe local data” fully clears Lite records and returns user to Lite start page.
- Existing cloud routes and behavior remain unchanged.
Priority
High
Additional context
This issue is an umbrella for Lite v1. Child issues should be created for:
- Lite routing/shell isolation
- Lite create page
- Lite local dispatch persistence
- CSV export + wipe flow
Summary
Add a Lite mode that runs entirely in-browser with no backend persistence. In Lite mode, users create an event from scratch, run dispatch locally, export CSV, and optionally wipe all local data.
Motivation
Some teams need a privacy-first workflow where no user-entered operational or patient data is sent to cloud services. Lite mode also reduces setup friction and supports low/no-connectivity operations.
Proposed solution
Alternatives considered
Rejected for Lite v1 to keep guarantees simple: no user-entered Lite data on backend.
Mockups / Examples
Acceptance criteria
Priority
High
Additional context
This issue is an umbrella for Lite v1. Child issues should be created for: