RideShare Platform
A complete ride-hailing ecosystem — rider, driver, and operations — running on one real-time backend.
RideShare Platform is a production-grade ride-hailing ecosystem comprising three integrated applications: a passenger app, a driver app, and a web-based operations dashboard. Built on Flutter, Laravel 11, PostgreSQL with PostGIS, Redis, and real-time WebSockets, it delivers the full lifecycle of on-demand transportation — from ride request and driver matching through trip completion, payment, and operational oversight.
A full ride-hailing platform, not just a clone
RideShare Platform consists of three coordinated products sharing one Laravel backend: a Rider App for booking, tracking, and paying for rides; a Driver App for onboarding, going online, and completing trips; and an Operations Dashboard for monitoring the fleet and running the business. All mobile clients authenticate via phone OTP and talk to a versioned REST API (`/api/v1`), while real-time updates flow through Laravel Reverb and driver locations are indexed in Redis for sub-second geospatial queries — a single source of truth instead of three disconnected products.
Ride-hailing is deceptively hard to build right
Organizations entering the mobility market all need the same things: a unified experience across rider, driver, and admin touchpoints; real-time coordination for matching, tracking, and status updates; operational control over drivers, vehicles, pricing, and support; and trust-and-safety features like SOS and audit trails. Point solutions or disconnected apps fail to meet these needs — they multiply integration cost and leave operations blind to what's actually happening in the fleet.
- Rider, driver, and admin experiences are usually built as disconnected products
- Real-time driver matching and live tracking demand infrastructure most teams underestimate
- Safety tooling (SOS, support tickets, audit trails) is often an afterthought, not a first-class flow
- Ops teams need live visibility into fleet activity, not just a database to query later
Three apps, one backend, one source of truth
I built the Rider App in Flutter with Riverpod state management, Material 3, and Google Maps, supporting English and Urdu localization. The Driver App follows Clean Architecture with feature-based modules and gates drivers behind document onboarding and admin approval before they can go online. Both apps share a Laravel 11 API secured with Sanctum, while an Operations Dashboard built on Filament v3 gives Admin, Ops, and Support roles a live map, driver management, and surge controls — all reading and writing the same ride, driver, and payment data.
Everything a real ride-hailing operator needs
- Phone OTP authentication across rider and driver apps with Sanctum-secured sessions
- Map-first ride booking with live fare estimates and surge multiplier visibility
- Real-time ride lifecycle tracking — searching → assigned → arriving → in progress → completed — over WebSockets
- Driver onboarding with document upload gated behind admin approval before going online
- In-ride chat between rider and driver during an active trip
- Safety center with SOS that raises an auditable support ticket instantly, visible to operations
- Filament-powered operations dashboard with a live fleet map, driver management, and surge pricing controls
- Role-based access control (Admin, Ops, Support) with two-factor authentication and full audit logging
See it in action
Mobile App
Web Dashboard
From architecture to a working three-app ecosystem
- 01
Architecture design
Designed a single Laravel 11 API (`/api/v1`) shared by both mobile apps and the admin panel, so a change to a fare rule or ride status only ever happens in one place.
- 02
Rider app
Built the Flutter rider experience on Riverpod with Google Maps integration — phone OTP login, fare estimates, live ride tracking, in-ride chat, a safety center, and English/Urdu localization.
- 03
Driver app
Built the driver side with Clean Architecture and feature modules — document onboarding gated by admin approval, ride offer dispatch with a countdown and fare preview, and an earnings dashboard.
- 04
Real-time layer
Indexed driver locations in Redis with geospatial commands for nearby-driver queries, and broadcast every ride status change over Laravel Reverb to private per-ride/per-driver channels — reaching riders, drivers, and the live admin map at once.
- 05
Operations dashboard
Built the Filament v3 admin panel with Spatie role-based access control, a live operations map, driver approval workflows, support ticket queues, and surge pricing controls.
- 06
QA & verification
Wrote automated Laravel feature tests covering the full ride lifecycle, driver onboarding gate, SOS/chat, and surge pricing, backed by Maestro end-to-end device tests and a manual checklist tying rider, driver, and admin flows together.
A production-grade, real-time stack
RideShare Platform is built natively on Android using a focused, modern stack chosen for performance, maintainability, and a clean user experience.
The decisions that shaped the platform
Keeping three apps in sync without three sources of truth
One Laravel API, one shared data model, and a versioned `/api/v1` mean rider, driver, and admin all read and write the same ride, status, and fare data — no drift between what a rider sees and what ops sees.
Real-time without melting the database
High-frequency driver location updates are throttled and written to Redis with GEOADD instead of hitting Postgres on every tick, while Reverb WebSockets push status changes to subscribed clients the moment they happen.
Gating drivers safely
Enforced the approval state machine — pending → documents_submitted → under_review → approved — in both the API and the dashboard, so an unapproved driver simply cannot go online, no matter what the client sends.
Making safety a first-class flow, not an afterthought
Wired the SOS button in both mobile apps directly into the same support-ticket pipeline operations already uses for everything else, so a safety event is never silent or siloed from normal ops workflows.
Why this project matters
RideShare Platform delivers a complete, integrated ride-hailing solution ready for real deployment and customization — three purpose-built applications sharing a robust backend, with real-time tracking, comprehensive admin tooling, and a security-first design. For a founder evaluating whether I can own a genuinely hard, multi-sided marketplace product end to end — mobile, backend, real-time infrastructure, and operations tooling together — this is the proof.
Have a mobile product idea?
I'm available for client work in Android, mobile product development, and end-to-end app delivery. Let's talk about what you're building.