Fleet management for ride-hailing drivers in LATAM. Live at checker.lab2next.com.
Fleet owners in LATAM (people who own a few cars and rent them to Uber, Didi, Cabify, and InDrive drivers) still run their business on WhatsApp messages and paper notebooks: who is on shift, how much each driver made, which car has which plates. I built Checker to put all of that in one place.
The design constraint that shaped the whole product: drivers use it at night, while working, with one hand. That is why check-in is a giant circular button and the driver view defaults to dark mode. The owner gets a desktop dashboard; the driver gets two taps and zero typing.
- Two roles, two interfaces: fleet owner dashboard (live KPIs, drivers on shift, vehicles, filterable reports) and a mobile-first driver view (check-in/check-out, trip logging in seconds, real-time net earnings per shift)
- Multi-platform earnings: Uber, Didi, Cabify, and InDrive in one dashboard, with gross vs net and automatic commission math
- Vehicle management: plates, models, assignments, one tap to reassign
- Guided onboarding: from account creation to first registered shift in about 10 minutes
- Dark mode by default for drivers, because most of this work happens at night
| One dashboard, every platform | Built for drivers on the go |
|---|---|
 |
 |
| Real-time numbers | Always in your pocket |
|---|---|
 |
 |
Next.js (App Router) · TypeScript · Tailwind CSS · shadcn/ui · pnpm
pnpm install
pnpm devCopy .env.example to .env.local and fill in the values.
Functional MVP with a live demo. Built end to end (product, design, and code) as part of my habit of building SaaS for real LATAM problems, the same muscle behind Lab2Next.
Designed and built by Javier Chi Ortiz in Mérida, México 🇲🇽