Customer
Ride requests, payments, history, stages, and savings.

Features
Search with stage context, choose public or private movement, keep payment proof, and review sensitive transport records before they become public or operational.
Feature areas
Each area exists because someone in the transport chain needs to finish a concrete action.
Compare public vehicles, private ride options, fare estimates, route context, pickup points, and dropoff points before booking.
Keep stage information, route direction, route activity, and location context useful for riders and crews.
Help users join or organize road trips with destination details, trip records, and payment visibility.
Show event destinations on the map and connect transport planning to event attendance.
Present vehicle identity, route, images, music context, and community content with admin review before publishing.
Drivers and conductors need practical tools for route activity, passengers, bookings, receipts, and verification.
Keep payment status, fare estimates, subscriptions, and receipt records available for support and dispute handling.
Admins review jobs, documents, uploaded vehicle images, community content, reports, and approval history.
Capability map
Each group pairs product capability with backend route families from the API catalog, so the page stays grounded in what the platform can actually serve.
Search, compare, book, pay, and keep a reliable history of trips and receipts.
Make stages, routes, events, heat signals, road trips, and tours easier to act on.
Give drivers, conductors, Saccos, owners, and work sessions the records they need.
Review content, documents, job activity, payouts, and portal verification before publishing.
API coverage
These numbers come from `/platform/catalog` when the backend is reachable.
Status and catalog metadata for public clients.
Fare estimates and user-sensitive computations.
Auth, review, moderation, jobs, payments, and portal actions.
ride:update, location:update, chat:message, alert:new
Portal roles
The backend catalog keeps role-specific portals aligned with the web experience.
Ride requests, payments, history, stages, and savings.
Public route duty, private ride requests, earnings, and vehicle status.
Passenger manifests, payment verification, and reports.
Fleet, revenue, routes, drivers, and operating analytics.
Vehicle performance, earnings, and trip analytics.
Applications, status, alerts, and earnings.
Executive monitoring, verification, revenue, trips, growth, and operations.