A ride-hailing and designated-driver platform — a Flutter driver app and a React Native customer app, both owned end-to-end from architecture to store release.
XE is a ride-hailing and designated-driver platform — two apps, one for drivers and one for riders. I owned both end-to-end: architecture, state, feature delivery, and store publishing.
The driver app is a Flutter build carrying the whole ride pipeline — driver lifecycle, WebSocket trip dispatch, live routing, and a multi-stage fare flow. The customer app mirrors the rider side on a modern React Native stack.
A driver app can't afford to drop a trip because the network blinked. Most of the engineering went into resilience — reconnect, heartbeat failover, duplicate filtering, and a background mode that survives the OS trying to kill it.
The driver side carries the real-time pipeline, so it's a Flutter build I could push hard on. The customer side mirrors the rider flow on React Native. Both apps talk to the same dispatch backend.
dart · androiddriver lifecycle · WebSocket trip dispatch · polyline routing · multi-stage fare flow
ts · react native + exporider flow · Expo Router · Redux Toolkit + Saga · NativeWind
trip matching · WebSocket dispatch · fare + voucher data
The hard part of a ride-hailing app isn't the happy path — it's everything the network and the OS do to break it. These four are where that work went.
Trip dispatch runs over a WebSocket with up to 10 reconnect attempts, a 90-second heartbeat failover, and duplicate filtering — so a flaky signal never costs a driver a fare, and never shows the same request twice.
Drivers leave the app backgrounded for hours. A foreground service with a hidden notification, plus wake and WiFi locks and FCM wake-ups, keeps the driver online when Android would otherwise reclaim the process.
Dynamic polyline routing from pickup to dropoff with an auto-fit camera, and a multi-stage fare flow — estimated, then final, then actual — that folds in vouchers, VAT, and waiting fees. The number a rider sees has to survive every stage.
The driver app is Flutter; the customer app mirrors the rider flow on React Native with Expo Router, Redux Toolkit and Saga, and NativeWind. Owning both meant keeping one product coherent across two ecosystems — plus OTP, image-based KYC, and a native-layer Android namespace patch.
Platform figures — rides/day, match latency, SLA, and the five-week timeline — are from NEWDEV's published case study for XE. Reconnect, heartbeat, and download figures are from the apps I built. Snapshot taken May 2026.
