The source material describes rider mobile, driver mobile with a fleet role, browser booking, admin and corporate access. It calls this five applications while also naming dispatcher and fleet logins. Agree the actual applications, role boundaries and code repositories rather than treating that label as a fixed package.
Rider mobile and browser
Map guest browsing, OTP, Google or Apple sign-in, saved/recent places and map pins. The rider selects a service and vehicle, compares an itemised estimate and ETA, books for self or another person, then tracks, pays, rates or rebooks. Agree which of these paths the browser also supports.
Driver mobile
The proposed driver path includes sign-in, availability, live map, timed offer, accepted job, pickup verification, trip detail, completion, earnings and support. Define the record returned after reconnect, document expiry and eligibility checks before an offer can be accepted.
Dispatch desk
Phone bookings need the same service, zone, vehicle, price and trip record as app bookings. Scope manual assignment, cancellation and reassignment with an audit trail; reject offline, ineligible or busy drivers and remove obsolete offers from other devices.
Fleet-manager role
Separate fleet-owned drivers and vehicles from platform-wide administration. Scope the fleet map, driver/vehicle documents and expiry, earnings by period, payout responsibility and permitted exports. A fleet must not read another fleet’s trips or balances.
Corporate portal
Define company membership, departments, approvers, booking policies, permitted travellers, company wallet or credit rules, invoice cycle and billing disputes. Trip visibility, personal data and delegated bookings must follow the company role and rider permissions.
Operator admin
Inventory ride requests, rider profiles, segments, vehicle types, zones, peak zones, heat maps, surge, documents, incentives, companies, invoices, payment settings, complaints and notifications. Agree CSV/Excel/PDF export contents, per-role access and retention.