SabiGo: The Engine Behind Sabi Ride
Sabi Ride is about much more than displaying a car on a map. Its product has to coordinate real people, uncertain locations, driver availability, fares, live movement, cancellations and the moment a journey or delivery is actually complete. I was a pioneering core developer of SabiGo, the service that makes those operations possible.
Turned transport ideas into coordinated ride, sharing and delivery journeys, from booking to fulfillment.
My role: Pioneering SabiGo developer and core ride-services owner
Public interface previewThe challenge
A transport marketplace cannot operate on booking screens alone. Drivers and passengers need to find each other, understand a trip, agree on and track the journey, receive timely updates and complete payments. Shared/group journeys and parcel deliveries introduce different participants and completion rules.
The part I led
I pioneered the SabiGo backend and owned substantial parts of its ride service: matching and proximity, fare estimation and trip states, group and shared rides, location streaming, driver/passenger messages and delivery flows. I also handled the less visible work of reorganizing services and addressing notification loss and disconnects. This was foundational product engineering within the wider Sabi Ride team.
The result
The system supports the operating journey behind ride-hailing, ride sharing, group coordination and dispatch delivery: requesting, matching, tracking, communicating, completing and recording what happened. Sabi Ride publicly presents these as services; the repository shows the service work behind them. I do not attribute the entire company or every app feature to myself, and no unverified volume or revenue figure is claimed.
The decisions and work behind it
- Pioneered the SabiGo ride-service foundation and evolved it into a set of connected journeys instead of isolated request handlers.
- Built driver/passenger matching, proximity and location-aware decisions so requests could become actual assignments.
- Developed the mechanics for shared and group rides, including joining, coordinating passengers and managing journeys in progress.
- Extended the same operating foundation into dispatch and parcel delivery, with recipient details, order states and proof/confirmation steps.
- Improved real-time communication, reconnection, acknowledgement and notification fallback so critical journey updates were less likely to disappear.