TransportationNetri Mobility (in-house)
Building a ride-hailing platform for Tier-2 India
A rider app, a driver app and an operations backend built from scratch for cities where metro-designed ride-hailing does not work.
- Rider and driver, shipped from one codebase
- 2 apps
- Bookings survive dropped connections
- Offline-first
- SOS available on every live trip
- 1-tap
The challenge
- Ride-hailing apps built for metros assume long trips, constant connectivity and card payments — none of which hold in Vijayapura.
- Riders, and women travelling after dark in particular, needed safety tooling present at launch rather than promised later.
- Drivers compare take-home earnings across apps daily, so opaque fare breakdowns cost supply immediately.
The solution
- Two native-feel React Native apps sharing one design system, so rider and driver experiences stay consistent as features land.
- Offline-tolerant booking: requests queue locally and reconcile when signal returns, instead of failing outright.
- Safety built into the first release — one-tap SOS, live trip sharing and verified driver profiles.
- Transparent fare breakdown and a real-time earnings dashboard on the driver side.
Implementation
- Mapped the real trip shapes in the city before writing code — distances, timings and payment habits.
- Shipped the rider app first to a small driver pool, then expanded supply once completion rates held.
- Instrumented booking funnel drop-off from day one so pricing and UX changes could be measured, not argued.
Technology
React NativeSignalRASP.NET CoreAzure MapsUPIRedis
Outcome
Netri runs as a live mobility platform with both apps published on Google Play, and remains the reference implementation for PolBrothers' mobility work.
Have a similar problem?
Tell us what you are trying to build and we will come back with an approach — not a sales deck.