How 420doma/trip works
420Doma’s Trip is documented as a motorcycle telemetry tracker: a phone sends GPS updates, a Flask service processes and stores rides, and a browser dashboard presents mileage, maps, charts, calendar details, and device status. The file tree contains only the frontend shell, PWA manifest, and service worker; the README documents the backend and database, but their source files are absent. Those components are therefore shown with null paths, and documented relationships are cited to the README.
Main entry points: index.html Web Dashboard · sw.js Service Worker · manifest.json Install Metadata
Components 14
Telemetry Processing
- Flask API
- GPS Processing
- Ride Database
Ride Dashboard
- Web Dashboard
index.html - Mileage Stats
index.html - Road Heatmap
index.html - Activity Charts
index.html - Ride Calendar
index.html - Phone Status
index.html
PWA Support
- Install Metadata
manifest.json - Service Worker
sw.js
Other components
- Rider
- Phone Tracker
- Web Browser
Connections 18
- Rider → Phone Tracker: starts tracking
README.md - Phone Tracker → Flask API: sends GPS
README.md - Flask API → GPS Processing: processes points
README.md - GPS Processing → Ride Database: stores rides
README.md - Flask API → Ride Database: persists data
README.md - Web Dashboard → Flask API: polls telemetry
README.md - Flask API → Web Dashboard: returns ride data
README.md - Web Dashboard → Mileage Stats: renders mileage
README.md - Web Dashboard → Road Heatmap: renders routes
README.md - Web Dashboard → Activity Charts: renders activity
README.md - Web Dashboard → Ride Calendar: shows daily detail
README.md - Web Dashboard → Phone Status: shows status
README.md - Rider → Web Dashboard: views dashboard
README.md - Web Browser → Web Dashboard: loads app
README.md - Web Browser → Install Metadata: installs app
README.md - Web Browser → Service Worker: runs worker
sw.js - Service Worker → Web Browser: claims clients
sw.js - Service Worker → Web Dashboard: notifies activation
sw.js