How shivram-aade/movesmart works
MoveSmart is a passenger-facing transit search, tracking, and ticketing application. Riders search between stops, compare direct or transfer journeys by ETA, fare, seats, and crowding, then follow buses or book a demo ticket. The backend also supplies account features, saved searches, notifications, and ticket documents. The README documents simulation, PDF/QR tickets, maps, and user features; some of those implementations are unsampled, so their internal links are left undocumented rather than inferred.
Main entry points: App.jsx Page router · RoutesPage.jsx Route search · api.js API client · server.js HTTP API
Components 23
Passenger app
- Page router
frontend/src/App.jsx - Route search
frontend/src/pages/RoutesPage.jsx - Live tracking
frontend/src/pages/Live.jsx - Dashboard
frontend/src/pages/Dashboard.jsx - Alerts view
frontend/src/pages/Notifications.jsx - Auth forms
frontend/src/pages/Auth.jsx - API client
frontend/src/api.js - Auth state
frontend/src/AuthContext.jsx - Stop planner
frontend/src/components/PlannerForm.jsx - Trip details
frontend/src/components/TripCard.jsx - Bus map
frontend/src/components/liveMap.jsx
Transit information
- Trip and ETA engine
backend/transit.js - Timetable calculations
backend/utils.js - Bus simulator
backend/simulate.js
Accounts and alerts
- Authentication
backend/auth.js
Ticketing
- Booking dialog
frontend/src/components/Bookmodal.jsx - Digital tickets
frontend/src/pages/tickets.jsx - Ticket service
backend/tickets.js
Persistence and simulation
- HTTP API
backend/server.js - MySQL pool
backend/db.js - Transit and user data
database/schema.sql
Other components
- Passenger
- OpenStreetMap
Connections 29
- Passenger → Page router: uses
README.md - Page router → Route search: routes to
frontend/src/App.jsx - Page router → Live tracking: routes to
frontend/src/App.jsx - Page router → Dashboard: routes to
frontend/src/App.jsx - Page router → Alerts view: routes to
frontend/src/App.jsx - Page router → Auth forms: routes to
frontend/src/App.jsx - Route search → API client: requests trips
frontend/src/pages/RoutesPage.jsx - Live tracking → API client: requests buses
frontend/src/pages/Live.jsx - Auth forms → Auth state: uses
frontend/src/pages/Auth.jsx - Auth state → API client: requests auth
frontend/src/AuthContext.jsx - Route search → Stop planner: renders
frontend/src/pages/RoutesPage.jsx - Route search → Trip details: renders
frontend/src/pages/RoutesPage.jsx - Route search → Bus map: renders
frontend/src/pages/RoutesPage.jsx - Live tracking → Bus map: renders
- Route search → Booking dialog: opens
frontend/src/pages/RoutesPage.jsx - Booking dialog → API client: submits booking
frontend/src/components/Bookmodal.jsx - Digital tickets → API client: requests tickets
frontend/src/pages/tickets.jsx - API client → HTTP API: sends API requests
frontend/src/api.js - HTTP API → Trip and ETA engine: dispatches trips
backend/server.js - HTTP API → Ticket service: dispatches tickets
backend/server.js - HTTP API → Authentication: uses auth
backend/server.js - Trip and ETA engine → Timetable calculations: calculates ETAs
backend/transit.js - Trip and ETA engine → MySQL pool: loads transit data
backend/transit.js - Ticket service → MySQL pool: reads and writes
backend/tickets.js - HTTP API → MySQL pool: queries account data
backend/server.js - Bus simulator → MySQL pool: updates bus state
backend/simulate.js - Transit and user data → MySQL pool: defines stored tables
- Bus map → OpenStreetMap: displays map tiles
- Trip and ETA engine → Bus simulator: uses simulated state