The build
Customer, driver, and rental-customer apps live in a single Melos monorepo so shared logic, design system, and networking are written once and reused everywhere. Bookings, drivers, vehicles, and fare-metering are coordinated from a Next.js + TypeScript operations portal.
Why a monorepo
Three apps that share domain models, auth, and UI benefit hugely from a workspace: one change to a shared package updates every app, analyze and test run across the whole tree, and releases stay in lockstep.
Scope
Alongside the mobile apps I maintain the back-office web portal for bookings, fleet, customers, and the fare meter — the full operator toolkit rather than just the rider-facing app.