Mega Cabs runs fixed-fare airport and city transfers across five Indian cities. This case study audits the live rider app against its own store data and rider feedback, then rebuilds the booking flow, safety tools, and the ops team's dispatch console around what was actually breaking.
Trusted by startups, growing businesses, and enterprise clients worldwide
App Store and Google Play reviews (2023–2026) cluster around fare transparency, dispatch reliability, and driver accountability — all addressable through product and ops-tooling design, not just support policy.
Quoted "fixed fares" frequently don't match the final bill, with no in-app breakdown to dispute.
"Quoted ₹1000... driver demanded ₹1600 instead of the agreed amount."
Confirmed bookings are sometimes left unassigned close to pickup, with no proactive alert to the rider.
"Cab was not assigned... later called to say there are no cabs, please arrange alternate."
When a trip goes wrong, there's no shared record tying driver, trip and fare together for support to resolve fast.
"Driver blames Mega, Mega blames driver. Customer is never considered."
Pulled directly from Mega Cabs' own App Store release notes (v1.1.0 – v1.4.6) — the redesign below builds on these shipped capabilities rather than inventing new ones.
Locked price shown before confirmation, no surge pricing.
Book across multiple cities in one reservation.
UPI, cards, netbanking via PayU; prepaid or postpaid.
Real-time trip tracking, shipped in v1.4.5.
One-tap SMS + call to the control room mid-trip.
Flags when a driver strays from the expected route.
Unified view of past and upcoming trips with status.
Dedicated phone lines per service city, always staffed.
Not part of Mega Cabs' published feature set — this is a proposed intelligence layer on top of the same booking and trip data, designed to prevent the exact complaints found in reviews.
Flags a final bill that deviates from the quoted fixed fare before it reaches the rider.
Forecasts assignment risk per booking so ops can act before a cab goes unassigned.
Tracks cancellations, disputes and route deviations per driver over time.
Predicts peak-hour demand per city to pre-position drivers near airports.
Classifies support tickets (fare, no-show, vehicle condition) to route them faster.
Surfaces riders who had a bad trip so support can proactively follow up.
Illustrative concept layer — not a documented or confirmed Mega Cabs capability.
Real screens captured from Mega Cabs' own App Store listing, followed by three concept additions designed to close the exact gaps found in rider reviews.

Phone-number sign-in, no password required.

Delhi, Bangalore, Amritsar or Goa — booking is gated to live cities.

Pickup, drop and an upfront estimated fare per car type.

Booking on behalf of a contact, who also gets driver details.

Booking confirmed → driver assigned → pickup → trip end, with OTP.

Structured reason codes — cab delay, driver behaviour, cab condition.

Upcoming vs. past trips, including cancelled bookings.

Favourite places, contact details and support number.
Surfaces the shipped v1.4.5 SOS feature directly on the trip screen instead of a menu.
Directly answers the "surprise final bill" complaint pattern from reviews.
UPI, card and netbanking via PayU, matching the app's real release notes.
Mega Cabs doesn't publish a driver-facing app publicly, so this is an original concept — built so the fare shown to the driver always matches what the rider confirmed, closing the "driver blames Mega, Mega blames driver" gap.
Same fixed fare the rider sees, shown up front.
Per-trip fare log that matches the rider's receipt.
Mega Cabs' internal dispatch tooling isn't public, so this console is an original concept — designed around the exact gaps reviews point to: no shared fare record, no live dispatch visibility, no unified driver accountability log.
| Booking | Rider | Driver | Fare | Status |
|---|---|---|---|---|
| #MC-8841 | A. Sharma | Rakesh K. | ₹649 | En route |
| #MC-8842 | P. Verma | — | ₹899 | Unassigned |
| #MC-8843 | R. Iyer | Suresh M. | ₹520 | Completed |
| #MC-8844 | N. Kapoor | Devendra S. | ₹1,240 | Fare disputed |
A reporting layer inside the same Ops Console — built so city managers can see trends without exporting anything to a spreadsheet.
| City | Trips (30d) | Revenue | Avg. rating | On-time % |
|---|---|---|---|---|
| Delhi & NCR | 1,420 | ₹9.6L | 3.9★ | 94% |
| Bengaluru | 760 | ₹5.1L | 3.6★ | 88% |
| Goa | 410 | ₹2.4L | 3.4★ | 81% |
| Hyderabad | 250 | ₹1.3L | 3.7★ | 90% |
Illustrative analytics view built for this case study — figures are representative, not Mega Cabs' actual reported numbers.
An illustrative stack for this class of product — not a confirmed list of Mega Cabs' actual technology choices.
Unedited excerpts, used to ground the design goals above — not testimonials, and not resolved by this concept case study alone.
"Despite paying 40% higher price... gave me a final bill with 10% more charge. Driver blames Mega, Mega blames driver."
"I had booked 2 cabs 3 hrs prior for airport but the cab was not assigned... later called to say there are no cabs."
"They take the booking and at the last moment deny coming to pickup... we have to call to hear take another cab."
Every fact, rating and review quote above is sourced from Mega Cabs' public App Store, Google Play and website listings. Every screen and console shown is an original concept created for this case study.
From safety-net engines to conversational AI consoles — we design and build the full stack, end to end.
Here's what our clients have to say about working with CodeChaps.
Noida, India
Pennsylvania, USA
Ontario, Canada
Hi there, Welcome to CodeChaps!
We're excited to turn your ideas into reality. What kind of development project are you thinking about?
Let's chat! 👇