EZ CarRide is a ride-hailing service in Texas. We built a rider app, a driver app and a fleet dashboard around one idea: drivers pick their own schedule, go online when it suits them and see what they earned today — while riders book, track and pay in the app.
Driver numbers, ride volume and revenue are the client's to share, and they are not on this page. What is on this page is what was built and why it was built that way.
EZ CarRide is a ride-hailing service operating out of Grand Prairie, Texas. Riders book a car on demand or schedule one ahead, track it on the map and pay in the app. Drivers sign up with their personal details, vehicle and licence, then go online and offline on their own terms, accept or decline ride requests, and see their ratings, completed trips and today's earnings at a glance.
The brief was the platform behind both: a rider app, a driver app and a fleet dashboard for the operator — driver approvals, bookings, transactions and a live map of the fleet. The driver's experience was the priority, because the business only works if drivers choose to drive for it.
Traditional taxi work runs on fixed shifts and slow settlements. A driver works the hours the company assigns, and the money for a week of rides arrives long after the rides. For someone driving part-time, around another job or family, that is the reason not to drive at all.
A platform that wants those drivers has to flip both. Going online has to be a switch the driver controls, and earnings have to be visible the same day — on top of everything a ride-hailing app already needs: onboarding and verification, real-time requests, live tracking and payments.
Every driver-side screen answers one of two questions — am I working right now, and what have I earned — while the rider side stays as short as booking a car should be.
Drivers toggle between online and offline from their overview, so they work the hours they choose rather than a schedule handed to them.
The driver overview shows today's earnings, trip completions and ratings, and withdrawals sit one tap away in the menu — so payout is something a driver sees daily, not waits for.
Personal details, vehicle, payment method, done — with driver licence and vehicle photos uploaded in the app, so a new driver can register without visiting an office.
New ride requests arrive with the passenger's rating and distance to accept or decline, and the trip is tracked live on the map, with updates pushed over sockets.
Riders pay by card through Stripe and Intercash, and drivers have an in-app wallet behind their earnings and withdrawals.
An Angular admin panel shows the live fleet map, drivers pending approval, active trips, bookings, transactions and monthly trip analytics.
Drivers choose their own hours by going online and offline from the app, instead of working assigned shifts.
Today's earnings, completed trips and ratings are on the driver's home screen, with withdrawals one tap away.
New drivers register in four steps with their licence and vehicle photos, and the operator approves them from the dashboard.
Riders book on demand or ahead, track the car live and pay in the app.
Ride requests, trip status and chat move in real time over sockets, so riders and drivers see the same trip.
The operator watches the whole fleet on a live map, alongside bookings, transactions and trip analytics.
Card payments for rides.
A second payment rail alongside Stripe.
Live trip tracking, ride requests on the map and the fleet view.
Social sign-in alongside email and password.
Building a platform drivers will actually choose to drive for?
The rider and driver apps and the fleet dashboard share one backend, so a booking is the same record for the rider, the driver and the operator.
Every tool below is in the build — no résumé-ware.
Start from the driver's two questions: am I working, and what have I earned. On EZ CarRide, drivers go online and offline with a toggle instead of working assigned shifts, and today's earnings, trip completions and ratings sit on their home screen with withdrawals one tap away.
EZ CarRide registers drivers in four steps — personal details, vehicle, payment method, done — with the driver licence and vehicle photos uploaded in the app. The operator then approves pending drivers from the fleet dashboard before they can take rides.
Usually, yes — riders and drivers do different jobs. EZ CarRide has a rider app and a driver app on one backend, with a fleet dashboard for the operator, so a booking is the same record on every screen.
Yes. EZ CarRide's apps are built with Ionic and Angular, which shares one codebase across platforms and lets the same team build the fleet dashboard in Angular too.
It depends on how many apps you need and what the operator side does. A rider app, driver app and fleet dashboard like EZ CarRide is scoped in phases and quoted fixed-price after a free scoping call.
Rider and driver apps, self-scheduled shifts, daily earnings and a live fleet dashboard.
See how we'd scope yours.
