Ride Plus
Admin dashboard, rider and driver tools, and passenger surfaces for a taxi platform.
Outcome
One dashboard for 42K+ driver records, trips, and payments.
- Year
- 2022-2023
- Role
- Front-end developer
- Status
- Client work
- Stack
- React, MUI data grids, Docker, REST APIs
The problem
Dispatch teams needed one view of drivers, trips, and payments while riders and drivers used separate surfaces.
What I built
Built the admin dashboard with driver records, trip views, and operational controls.
Worked on rider, driver, and passenger-facing screens.
Used MUI data grids for large operational tables and Docker for local and deploy environments.
Surfaces
- Admin dashboard
- Rider app
- Driver tools
- Dispatch APIs
Decisions
Operational data stayed in dense tables instead of cards.
Admin, rider, and driver surfaces shared the same API contract.
Scope
I worked on the dashboard, rider and driver tools, and passenger surfaces.
Team context
Ride Plus is part of RIDE 8294, a taxi platform operating in Ethiopia and Djibouti. The admin view I worked on held 42K+ driver records.
Result
The dashboard handled 42K+ driver records alongside trip and payment views.