How solomon-wilson/urban-mobility-management-system works
This is a public-transport management web application with authentication, operator dashboards, compliance tracking, infrastructure mapping, and mobility analytics. The visible user-facing flow begins at the Next.js app shell, which provides authentication context around the page; the dashboard and domain modules represent operational views. The excerpts confirm AssetMapView selects and supplies assets to one of two map renderers. The README is empty, and unsampled page, dashboard, compliance, and data-access code limits conclusions about their wiring; the Supabase files establish integration support and domain types, not confirmed runtime reads or writes.
Main entry points: AssetMapView.tsx Asset mapping · layout.tsx Root layout · page.tsx App page · AuthContext.tsx Auth provider
Components 16
App and access
- Root layout
src/app/layout.tsx - App page
src/app/page.tsx - Auth provider
src/components/auth/AuthContext.tsx - Login form
src/components/auth/LoginForm.tsx - User profile
src/components/auth/UserProfile.tsx
Operations dashboard
- Dashboard layout
src/components/dashboard/DashboardLayout.tsx - Operator overview
src/components/dashboard/OperatorOverview.tsx - Mobility analytics
src/components/dashboard/SmartMobilityPlatform.tsx
Transport domains
- Compliance module
src/components/compliance/ComplianceModule.tsx - Asset mapping
src/components/maps/AssetMapView.tsx - Interactive map
src/components/maps/InteractiveMap.tsx - Google map
src/components/maps/GoogleMapsView.tsx
Data foundations
- Supabase client
src/lib/supabase.ts - Database types
types/database.types.ts - Supabase types
src/types/supabase.ts
Other components
- User
Connections 4
- User → App page: opens app
- Root layout → Auth provider: wraps children
- Asset mapping → Interactive map: renders assets
- Asset mapping → Google map: renders assets