How shalyagaonkar520-web/taxi works
NexRide is a role-based ride-hailing platform. Riders search locations, compare route and vehicle-tier quotes, request rides, follow dispatch and trip progress, then settle and review; drivers receive requests and manage arrival, PIN verification, navigation, and completion; admins monitor fleet and revenue and adjust pricing controls. The sampled frontend and API code supports the main entry points and quote flow; README-described real-time trip events and other capabilities are represented where their owning modules are evident, but unsampled event wiring is not detailed.
Main entry points: App.jsx Role App · api.js REST Client · server.js HTTP API · socket.js Realtime Client
Components 20
Role Workspaces
- Role App
client/src/App.jsx - Rider Booking
client/src/components/Rider/RiderView.jsx - Driver Workspace
client/src/components/Driver/DriverView.jsx - Admin Console
client/src/components/Admin/AdminView.jsx - Live Map
client/src/components/Map/LiveMap.jsx - Wallet
client/src/components/WalletModal.jsx - Trip History
client/src/components/HistoryModal.jsx
Ride Operations
- REST Client
client/src/services/api.js - Realtime Client
client/src/services/socket.js
Platform Services
- HTTP API
server/src/server.js - Socket Events
server/src/socket.js - Routing & Places
server/src/services/routing.js - Fare Pricing
server/src/services/pricing.js
Platform State
- Data Access
server/src/db.js - JSON State
server/data/db.json
Other components
- Rider
- Driver
- Admin
- OSRM
- Geocoding APIs
Connections 25
- Rider → Role App: opens role
- Driver → Role App: opens role
- Admin → Role App: opens role
- Role App → Rider Booking: renders
- Role App → Driver Workspace: renders
- Role App → Admin Console: renders
- Role App → Live Map: renders
- Role App → REST Client: loads user and ride
- Role App → Realtime Client: registers user
- Rider Booking → REST Client: searches and quotes
- Rider Booking → Realtime Client: ride updates
- Driver Workspace → Realtime Client: trip controls
- Admin Console → REST Client: loads and updates
- Wallet → REST Client: reads and tops up
- Trip History → REST Client: loads history
- REST Client → HTTP API: REST requests
- Realtime Client → Socket Events: socket events
- HTTP API → Data Access: reads and writes
- Socket Events → Data Access: ride state access
- Data Access → JSON State: persists data
- HTTP API → Routing & Places: searches and routes
- HTTP API → Fare Pricing: calculates quotes
- HTTP API → Data Access: reads settings
- Routing & Places → OSRM: requests driving routes
- Routing & Places → Geocoding APIs: searches places