Kero Ride

Kero is a ride-hailing product made up of four connected pieces: a rider app for booking trips and tracking the driver live on the map, a driver app for accepting, managing and completing trip requests, a Node.js backend that matches riders to drivers in real time, and a web dashboard where the team manages users, drivers and ride analytics. I've worked on Kero since 2024 across the mobile apps, the backend and the admin.

Ride-hailing is unforgiving. A rider wants to see their driver moving on the map, a driver needs a new request to appear the moment it's assigned, and riders and drivers need to reach each other without sharing phone numbers. Most users are on mid-range Android phones and patchy mobile data, and four separate surfaces all have to agree on the state of every trip.

1. 1Built the rider and driver apps with React Native, Expo Router and NativeWind, with Zustand for state, so iOS and Android ship together and behave the same.
2. 2Live trip tracking with React Native Maps, Google Places autocomplete and route directions, kept in sync over Socket.IO.
3. 3In-app voice calls between rider and driver using Agora, with CallKeep and VoIP push so calls ring like a normal phone call.
4. 4Push notifications through Firebase Cloud Messaging, Google sign-in, and card payments with Paystack.
5. 5A Node.js + Express backend on MongoDB, with Socket.IO scaled through a Redis adapter, BullMQ queues and cron jobs for background work.
6. 6A React operations dashboard with Google Maps / Leaflet views and Recharts analytics for managing riders, drivers and trips.

• React Native
• Expo Router
• NativeWind
• Zustand
• React Native Maps
• Socket.IO
• Agora (in-app calls)
• Firebase Cloud Messaging
• Paystack
• Node.js
• Express
• MongoDB
• Redis
• BullMQ
• React
• Recharts

Kero runs as a full platform rather than a single app: riders, drivers and the operations team each have a tool designed for how they actually work, connected by one real-time backend.