Skip to main content
Elimane BADeveloper
FREN
← WorkCase study 01 / 09

01

Orbits

Ride-hailing platform

A complete ride-hailing platform for the New York market, designed and delivered end to end.

Role
Lead Software Engineer & Full-Stack Mobile Developer
Disciplines
Mobile / Backend
Stack
  • Flutter
  • Dart
  • Laravel
  • PHP
  • MySQL
  • Firebase
  • Google Maps Platform
  • Stripe
  • REST API
  • FCM
Links
Rider app — App Store ↗Rider app — Google Play ↗Driver app — App Store ↗Driver app — Google Play ↗
  • Orbits app screens: vehicle selection and ride tracking
  • Orbits — visual 2
  • Orbits — visual 3
  • Orbits — visual 4
OrbitsApp
Orbits app screens: vehicle selection and ride tracking
OrbitsFig. 01
Orbits — visual 2
OrbitsFig. 02
Orbits — visual 3
OrbitsFig. 03
Orbits — visual 4
OrbitsFig. 04

01 / The problem

Launching a credible ride-hailing platform in a demanding market without an established product team: two apps (rider, driver), a robust backend and an admin panel — while guaranteeing reliable payments and real-time tracking.

02 / The solution

End-to-end design of the Rider and Driver Flutter apps, the Laravel backend and the admin panel. Real-time geolocation, ride booking and management, secure Stripe payments, a digital wallet handling commissions and driver payouts, push notifications and an analytics dashboard.

03 / Architecture

Architecture

A Laravel backend exposing a REST API consumed by two Flutter apps (Rider, Driver) and an admin panel. MySQL for persistence, Firebase (FCM) for real-time notifications, Stripe for payments, Google Maps Platform for geolocation and ride tracking.

04 / Highlights

Highlights

  1. 01Complete architecture designed for two distinct user profiles (rider / driver)
  2. 02Built-in digital wallet with fine-grained commission and payout management
  3. 03Real-time tracking and secure payments in production

05 / Results

Results

  1. 01Two separate mobile apps published (Rider and Driver)
  2. 02Payment system and digital wallet running in production
  3. 03Admin panel for real-time tracking of rides, drivers and payments

Lesson learned

“Designing for two user profiles from the architecture stage — not as an afterthought — avoids heavy technical debt on a multi-app product. A clear separation of roles in the API was the most structuring decision of the project.”

Next project02

Scan Tickets →

Have a similar project in mind?

Get in touch →