How rayan-ite/sped-go works
Spedgo is a multi-surface logistics platform for customers, drivers, store owners, and administrators. Customers browse products, place orders with a selected driver, and track delivery; drivers accept and complete deliveries while broadcasting GPS; store owners manage stores and inventory; administrators monitor operations and fleet activity. The mobile and web clients use an ASP.NET API backed by SQL Server, with SignalR for live updates. The graph preserves the documented product areas; some client-to-API links are based on README descriptions because their implementations were not sampled.
Main entry points: AppDbContext.cs Entity data context · apiClient.js API client · App.js Mobile app entry · App.tsx Web application
Components 34
Mobile app
- Mobile app entry
App.js - Role navigation
navigation/AppNavigator.js - Session and auth
context/AuthContext.js - Marketplace and checkout
screens/CheckoutScreen.js - Orders and tracking
screens/FleetScreen.js - Driver operations
screens/DriverScreen.js - Store management
screens/StoreOwnerScreen.js - Admin fleet
screens/AdminFleetScreen.js - API client
services/apiClient.js - SignalR client
services/signalrService.js - Session storage
services/storage.js
Web app
- Web application
spedgo-web/src/App.tsx - Role-based routes
spedgo-web/src/routes/index.tsx - Customer pages
spedgo-web/src/pages/customer/MarketplacePage.tsx - Driver deliveries
spedgo-web/src/pages/driver/DeliveriesPage.tsx - Store-owner page
spedgo-web/src/pages/store-owner/StorePage.tsx - Admin dashboard
spedgo-web/src/dashboard/pages/OverviewPage.tsx - Live fleet map
spedgo-web/src/dashboard/fleet/FleetMap.tsx - Web API client
spedgo-web/src/api/client.ts - Web SignalR
spedgo-web/src/services/signalr.ts
Backend API
- Authentication API
backend/new/AuthApi/Controllers/AuthController.cs - Orders API
backend/new/AuthApi/Controllers/OrdersController.cs - Driver API
backend/new/AuthApi/Controllers/DriverController.cs - Products and stores
backend/new/AuthApi/Controllers/ProductsController.cs - Administration API
backend/new/AuthApi/Controllers/AdminController.cs - Rides API
backend/new/AuthApi/Controllers/RidesController.cs - Users API
backend/new/AuthApi/Controllers/UsersController.cs
Data and realtime
- Entity data context
backend/new/AuthApi/Data/AppDbContext.cs - SQL Server
- DriverHub realtime
backend/new/AuthApi/Hubs/DriverHub.cs
Other components
- Customer
- Driver
- Store owner
- Administrator
Connections 48
- Customer → Mobile app entry: uses
- Driver → Mobile app entry: uses
- Store owner → Mobile app entry: uses
- Administrator → Mobile app entry: uses
- Mobile app entry → Role navigation: renders
App.js - Role navigation → Session and auth: checks session
navigation/AppNavigator.js - Session and auth → Session storage: restores session
context/AuthContext.js - Session and auth → API client: uses
context/AuthContext.js - Customer → Marketplace and checkout: browses and checks out
- Customer → Orders and tracking: tracks orders
- Driver → Driver operations: manages deliveries
- Store owner → Store management: manages inventory
- Administrator → Admin fleet: monitors fleet
- Marketplace and checkout → API client: requests
- Orders and tracking → API client: requests
screens/FleetScreen.js - Orders and tracking → SignalR client: subscribes
screens/FleetScreen.js - Driver operations → API client: requests
screens/DriverScreen.js - Driver operations → SignalR client: broadcasts location
screens/DriverScreen.js - Store management → API client: manages products
screens/StoreOwnerScreen.js - Admin fleet → API client: requests fleet data
- API client → Orders API: calls
- SignalR client → DriverHub realtime: connects
- Customer → Web application: uses
- Driver → Web application: uses
- Store owner → Web application: uses
- Administrator → Web application: uses
- Web application → Role-based routes: routes
- Customer → Customer pages: shops and tracks
- Driver → Driver deliveries: manages deliveries
- Store owner → Store-owner page: manages store
- Administrator → Admin dashboard: reviews operations
- Admin dashboard → Live fleet map: shows live fleet
- Customer pages → Web API client: requests
- Driver deliveries → Web API client: requests
- Store-owner page → Web API client: requests
- Admin dashboard → Web API client: requests
- Live fleet map → Web SignalR: receives live drivers
- Web API client → Authentication API: calls
- Web SignalR → DriverHub realtime: connects
- Orders API → Entity data context: reads and writes
backend/new/AuthApi/Controllers/OrdersController.cs - Driver API → Entity data context: reads and writes
backend/new/AuthApi/Controllers/DriverController.cs - Administration API → Entity data context: queries
backend/new/AuthApi/Controllers/AdminController.cs - Orders API → DriverHub realtime: notifies drivers
backend/new/AuthApi/Controllers/OrdersController.cs - DriverHub realtime → Entity data context: updates driver state
backend/new/AuthApi/Hubs/DriverHub.cs - Authentication API → Entity data context: persists accounts
- Products and stores → Entity data context: manages catalog
- Rides API → Entity data context: manages rides
- Users API → Entity data context: manages users