How to build a ride-hailing app in Ghana

To build a ride-hailing app in Ghana you need the same three products as anywhere: a rider app, a driver app and an admin dashboard. What changes is everything around them. How people give directions. How they pay. How you prove a driver is who he says he is.

Get those three right and you have a product. Get them wrong and you have a nice demo.

Is there room next to Bolt, Uber and Yango?

They cover the big cities, and they take a cut of somewhere around a fifth to a quarter of each fare, depending on who you ask. That leaves gaps. Other vehicles. Other towns. Drivers who feel squeezed.

A new player doesn't win by being a cheaper Bolt. It wins by serving something Bolt doesn't. Decide what that is before you spend anything.

How should pickups work?

Not with a street address. Nobody gives directions like that. People say: the blue kiosk after the filling station.

So the rider drops a pin on the map and adds a short landmark note. The driver sees both. Simple, and it saves ten phone calls a day per driver.

How do people pay?

Three ways, and you need all three.

Mobile money comes first. MTN MoMo, Telecel Cash, AT Money. For a lot of riders that is the bank. A payment provider that covers all three, plus cards, saves you building each one.

Cards matter for visitors and the top of the market.

Cash is the tricky one. The rider pays the driver in his hand, so the driver is holding your commission. The way the big apps handle it works: the app records the fare, the driver owes the commission, and he settles it from his wallet. If the balance runs too high, new jobs pause until he clears it.

Build cash properly or you will not get paid on half your rides.

How do you check drivers?

This is where trust is won. A photo of a licence is not a check. Anyone can photograph a licence.

A proper check confirms the Ghana Card against the national record with a live selfie, and confirms the driving licence with the licensing authority. There are verification services built for exactly this. Then an admin approves each driver by hand, with the result in front of them.

Expiry dates matter too. Insurance and roadworthy certificates run out. The system should pause a driver the day a document lapses, without anyone having to remember.

What about weak signal and cheap phones?

Plan for both. The driver app has to keep a trip alive when the data drops and catch up when it returns. It has to go easy on the battery and the data bundle, because the driver is paying for both.

We learned this on our own apps. One of them is used at shop counters where the wifi dies, so it queues every action on the phone and sends it when the signal is back, without ever counting twice. Same problem, same fix.

What do the rules say?

Check them before you design anything, because they shape the app. Who can drive commercially, what licence they need, what the transport and tax authorities expect platforms to record, and how you must handle personal data. Ghana has a data protection law and a commission that enforces it.

Build the checks to support the rules from day one. Bolting compliance on later costs more and looks worse.

What should the first version include?

• Rider app: pin and landmark, upfront fare, live tracking, pay by MoMo, card or cash, rate the trip.
• Driver app: sign-up with documents, go online, accept, get directions, see earnings and what is owed.
• Admin: approve drivers, set fares per city and vehicle type, watch trips, handle disputes.
• Safety: share my trip, an SOS button, phone numbers hidden between rider and driver.

Everything else can wait for real riders to ask for it.

I wrote separately about what an app like this costs. If you are planning one and want it scoped properly, tell me what it has to do. This is the kind of platform we build.