riderx icon

A New Kind of Ride Sharing Experience

riderX is a new kind of ride-sharing app currently in a private beta in select US markets. Against a subscription fee, it allows the drivers to keep a much bigger cut of the ride. Happier drivers mean a better customer experience. Everyone wins.
server side
Server Side
riderx app app
When a product has two distinct customers, catering to both their needs fairly can prove to be a little tricky. Satisfaction of both is the goal, but is easier said than done. One of our clients sought to address this very issue in a ride-sharing app, where they introduced a subscription model.
This allows the drivers to keep a bigger cut of the rides, increasing motivation levels and providing incentive. Now that the drivers were happy, they were more inclined to ensure a happier experience for the other stakeholder – the ride-sharers themselves.
project life cycle

Interface & Experience

We conducted a thorough design process where we iteratively prototyped complicated app flows (such as driver onboarding which had 20 steps) with an eye towards minimalism and a simplified, delightful user experience. Additionally, we devised a design language and a brand book which allowed other components of the riderX product family to be consistent in their look and feel.
background the riderx

Mobile Engineering

We built out both the driver and rider apps - Android and iOS - for a total of 4 native apps. We built robust onboarding flows and engineered all the ride-sharing flows such as rider polling, rider and drive selection, location tracking, fare calculation, wallet management, and billing.

Backend Engineering

We designed and implemented a microservices architecture to serve the riderX product family. The microservices are a mix of Node/Mongo and Firebase services (for the real-time features), that work together in a decoupled way. The architecture is engineered to be robust, fault-tolerant and scalable.

Infrastructure Engineering

A highly scalable infrastructure for riderX was deployed. We used AWS Scaling groups and ELBs for deploying and scaling the microservices and mono cloud hosting with sharded database clusters for DB scaling. Finally, we also set up CI/CD pipelines for quick setups and deployments.