Taxi or ride booking app without coding: rider and driver apps

Every city has a ride business that runs on phone calls and a WhatsApp group: a keke fleet in Port Harcourt, twelve okada riders around a Lagos estate, an airport transfer company in Abuja with four Sienna buses. The dispatcher knows every driver by voice, the customer never knows where the car is, and the fare is whatever was agreed before the driver saw the traffic on Third Mainland Bridge. A ride booking app with a rider side and a driver side turns that into something customers trust: a pin for pick-up, a pin for drop-off, a fare estimate before they commit, the car moving on the map, and a rating at the end that tells you which driver to give the next airport run.

Ride apps have a reputation for being expensive to build, and they are if you commission one from scratch. Most of that cost is the same set of screens every ride app has, wired to a backend that matches riders with drivers. When you describe your service to App Builder Agent, the agent writes those screens in React Native, deploys a hosted backend for the matching and status, and gives you an APK for the drivers' phones. The part you should spend your attention on is what makes your service different: your zones, your vehicle types, your fare rules, and how you onboard drivers.

What a ride booking app must handle

• Two roles in one app — Rider and driver, chosen at sign-up, with an admin login for you. Each role sees only its own screens.
• Map pick-up and drop-off — A map with a draggable pin, an address search, and “use my location” for the pick-up.
• Fare estimate before booking — Base fare plus per-kilometre and per-minute rates, by vehicle type, shown before the rider confirms.
• Driver matching — Requests go to nearby online drivers; first to accept gets the ride; the rest are told it is taken.
• Ride status — Requested, accepted, driver arriving, in progress, completed, cancelled. Both sides see the same status.
• Live location — The driver's GPS position streams to the backend so the rider watches the car approach.
• Ratings and history — Star rating with an optional comment both ways, and a ride history with receipts.
• Admin view — Drivers online right now, rides today, cancellations, and a button to suspend a driver.

Build it with App Builder Agent, step by step

Riders and drivers must see the same ride at the same moment, so this is a hosted-backend app from the very first message. Say so, and name your city so the map opens in the right place.

1. Create a mobile app project. Drivers will install the APK; riders will too, or use the web version from a link in your ads.
2. Describe the roles, the map and the fares. Numbers matter here: the agent turns them into the fare calculation.
   Build a ride booking app called “Swift Ride” for Lagos, Nigeria, prices in naira. Roles at sign-up: rider or driver, plus an admin login. Rider: map centred on Lekki, set pick-up (default to my GPS position) and drop-off by dragging a pin or searching an address, choose vehicle type (Keke ₦300 base + ₦120/km, Car ₦800 base + ₦250/km + ₦30/min, Bus 7-seater ₦1,500 base + ₦300/km), see the fare estimate and ETA, confirm. Driver: go online/offline toggle, incoming request card with pick-up distance and fare, accept within 20 seconds, navigate, start and end ride. Ride status screen on both sides: requested, accepted, arriving, in progress, completed. Send the driver's location every 5 seconds while on a ride. Rating 1–5 with comment after every ride. Admin: online drivers, today's rides, cancellations. Hosted backend. Deep green and white design.
3. Run a ride in the preview with two roles. Sign up as a rider, request a ride, then sign in as a driver in a second preview session and accept it. In the browser, the driver's GPS is simulated: open the Simulate panel, set a position near the pick-up and move it along a route to watch the rider's map update. On a real phone the same code reads the actual GPS.
4. Add the parts that stop arguments. Cancellation rules, a fare breakdown on the receipt, and an emergency contact.
   Add a cancellation fee of ₦200 if the rider cancels more than 2 minutes after a driver accepted, shown clearly before they confirm the cancel. On the receipt, show distance, time, base fare and the per-km and per-minute lines separately. Add a “Share my trip” button that sends the live ride link via the share sheet, and an SOS button that calls a number I set in admin.
5. Install on the drivers' phones. Download the APK, put it on every driver's Android phone, and run a week of real rides alongside the WhatsApp group before you retire the group.

Prompts that work well

The rider–driver structure fits more than city taxis. Change the vehicle, the zones and the pricing rule.

Common mistakes (and the fix)

• Two drivers accept the same ride. Acceptance must be decided on the backend, not the phone. Tell the agent the first accept wins and everyone else gets a “ride taken” message, and test it with two driver sessions.
• Fare estimate from a straight line. As-the-crow-flies distance underestimates Lagos traffic badly. Ask for route distance from the map and a visible “estimate” label, with the final fare computed from the actual route driven.
• Sending GPS every second. It drains the driver's battery by lunchtime. Every 5 seconds on a ride and every 30 seconds while idle is plenty.
• Location permission asked at the wrong moment. Ask when the rider taps “use my location”, with one sentence explaining why, not on app launch. Denied permissions are the top support message on ride apps.
• No offline behaviour. Drivers go through areas with no data. Ask for the current ride to be cached on the phone, status changes queued, and a clear “reconnecting” banner.
• Ratings that punish honest drivers. Show the rider's rating to the driver too, and let the admin see comments before a low rating affects anyone.

Make it feel finished

• Show the driver's name, photo, plate number and vehicle colour the moment a ride is accepted; it is the single biggest trust signal.
• Put an ETA countdown on the arriving status and a notification when the driver is 1 minute away.
• Keep a saved-places list (Home, Work, Mum's house) so repeat riders book in two taps.
• Let drivers see their day: rides, distance, earnings and cash collected, right on the home screen.
• Add a receipt the rider can share, with the fare breakdown and the route on a small map.

Installing, publishing and next steps

The driver app should be an installed APK: from the Preview tab, “Download APK” gives you a release-signed build straight from the AI app builder, and a signed APK and AAB with your own package id when you want a Play Store listing so drivers update automatically. Riders can install the same APK or open the web version from a link in your ads; both talk to the same hosted backend, which is included with the project. For a first look at how map-based apps turn out, browse the ready-made maps and location apps.

Once rides are flowing, two guides pick up where this one stops: the maps and location tracking guide goes deeper on geofences, trails and background-friendly location updates, and the booking and appointment guide covers advance reservations, which is how airport transfers and school runs are really sold. Open the builder, name your city and your fares, and request your first ride.

Frequently asked