Building an app like Uber, Bolt or a boda and delivery app in East Africa is a bigger job than a normal business app, and the price depends on how much of the platform you launch with. A lean MVP that people can actually ride or order on costs far less than a full platform with surge pricing, wallets and a fleet dashboard. The range is wide because "an app like Uber" is never one app. It is a rider app, a driver app and an admin console, tied to live maps, a matching engine and Mobile Money, and each of those pieces adds real cost. In Uganda there is also a new fact on the ground: Uber has left. Below is the honest breakdown, including the price for your region, so you can see exactly where your budget goes.
September 2026: Uber has left Uganda
Uber told customers it was winding down its Ugandan operations effective 2 September 2026, after about ten years in the country, following what it called a review of its business. It closed its Nigerian operations the same day. Uber has not given a Uganda-specific reason and has not said the market was unprofitable. Reports in the Daily Monitor and elsewhere point to competition, high running costs and drivers who uninstalled the app or took trips off it, but Uber itself has not confirmed those reasons.
If you are thinking about building a ride app, here is what that means in practice:
- There is a gap, but not an empty market. Riders and drivers who used Uber now have to use other apps. Bolt, SafeBoda and several others were already working in Kampala, and they are competing for the same people.
- The exit is a warning about the economics. A global company with a large budget chose to leave after a decade. A new app only works if drivers can earn a living on it and riders get a vehicle quickly, so the driver side deserves as much attention as the rider side.
- Start narrow. One town, one vehicle type or one niche, such as boda trips, parcel runs or a fixed route, is cheaper to build and easier to keep supplied with drivers than a city-wide Uber clone. That is the MVP path covered below.
The local players you would compete with
These are the main ride-hailing apps named in Ugandan press coverage after Uber's exit in September 2026. The market moves fast, so check each app yourself before you decide anything.
| Player | What it offers | What it means for a new app |
|---|---|---|
| Bolt | Car-hailing, plus boda boda and delivery services | Competes on rides, boda and delivery, so a new app cannot assume a free field in any of the three |
| SafeBoda | Started with boda boda and is strong in Kampala's motorcycle market. Added SafeCar, car-hailing, in 2022 | Operating in Uganda since 2015. Beating it on boda needs a clear driver or price advantage. See the cost to build an app like SafeBoda |
| Faras, Yango and Tinka | Named in local coverage as further competitors | We have not compared their fares or commissions, so do that research before you set yours |
| Little | Reported as joining the market after Uber's exit, and says it has the lowest commissions in the market | A commission claim, with no figure in the coverage we read. Expect commission to be a battleground |
Food and grocery delivery is a separate fight with different economics, which we cover in food delivery app development in Uganda.
Why "an app like Uber" is a wide price range
When someone says "like Uber" they might mean a simple boda-booking app for one town, or a multi-city platform with cashless wallets, ratings, promotions and a support back office. Those are different projects with a 5x difference in price. Uber itself is thousands of engineer-years of work. Nobody in Kampala or Nairobi is quoting you that, and you do not need it. What you need is the slice of Uber that serves your riders and drivers, built well. The job of a good quote is to define that slice precisely, then price it, which is why we scope before we quote instead of hiding behind "contact us".
You are paying for three apps, not one
This is the single biggest reason a ride or delivery app costs more than a normal business app. A working marketplace needs three connected surfaces:
- The customer app, where a rider sets a pickup and drop-off, sees the fare, tracks the driver and pays.
- The driver or rider app, where a boda or courier goes online, accepts jobs, navigates and gets paid out.
- The admin dashboard, where you approve drivers, set pricing, watch live trips, handle disputes and pull out your commission.
We build the two phone apps from one codebase with Flutter or React Native (see Flutter vs React Native), so Android and iOS ship together instead of being priced twice. That is a deliberate cost saving. The admin side is a web dashboard. Skip the dashboard and you have no business, just an app you cannot control, so it is not optional.
The features that actually drive the cost
| Feature | Why it costs | Cost weight |
|---|---|---|
| Live maps and tracking | Map tiles, routing, ETAs and a moving car on the screen, tuned to work on slow data | High |
| Dispatch and matching | The engine that finds the nearest free driver, offers the job and reassigns if declined | High |
| Two phone apps plus admin | Three surfaces to design, build and test instead of one | High |
| Mobile Money and M-Pesa | Ledgers, webhooks, retries and reconciliation so no fare is ever lost | High |
| Ratings and trip history | Trust features that keep drivers and riders honest | Medium |
| Wallets and driver payouts | Holding balances and paying drivers safely needs a proper double-entry ledger | Medium to high |
| Surge and promo pricing | Dynamic fares and discount codes add rules and edge cases | Medium |
Maps and matching are where a ride app earns its keep and where the engineering is genuinely hard. A car that jumps around the map, or a driver who never gets the ping, kills the product on day one. That work is a large slice of the budget for a reason.
The driver side: what drivers want and what it costs you
Drivers decide whether a ride app works. Press coverage of Uber's exit describes drivers uninstalling the app, taking trips off it, and struggling with fuel and running costs. Al Jazeera notes that drivers in Uganda protested Uber's 25% commission in 2019 while fares stayed low. So the driver app is where a new platform wins or loses. The table lists what drivers ask for, the honest trade-off for you as the owner, and whether we would put it in the first release.
| Driver feature | Why drivers want it | The honest trade-off for you | First release? |
|---|---|---|---|
| Clear commission and fare breakdown | Drivers see exactly what the platform takes from every trip, so payout day holds no surprises | It puts your fee next to your rivals' fees. A lower fee wins drivers but leaves less to cover maps, SMS, hosting and support | Yes |
| Fast payouts to Mobile Money | Drivers buy fuel daily and want their money the same day | You need enough balance to pay from, someone has to absorb Mobile Money fees on payouts, and disputed trips need clear reversal rules | Yes, one channel |
| Document checks and approval at sign-up | A clear checklist, and riders trust verified drivers | It slows driver sign-up and someone has to review documents. It also supports the licensing duties you carry as operator | Yes |
| Fixed fares or driver-negotiated fares | Negotiation lets a driver hold out for a fair price | Fixed fares book faster and are simpler to build. Negotiation adds a bidding screen, slower booking and more disputes | Fixed fares first |
| Low-data mode | Mid-range Android phones and expensive data | Lighter maps and fewer live updates mean a less rich map, and tuning it takes extra engineering | Yes, built in |
| SOS button and trip sharing | Safety on night trips and long routes | A button nobody answers is worse than none, so a person has to watch the alerts | Yes, if you can staff it |
| Earnings after costs (fuel and expenses log) | Drivers care about take-home pay, not gross trips | It only helps if drivers keep entering costs. Extra screens that few people use are build cost with little return | Later |
| In-app chat and masked calling | Protects the driver's number and keeps the trip on the platform | Calls through the app carry telephony costs, and no feature fully stops drivers and riders going off the app. Fair pay does more than locks | Chat first, calls later |
Every row is a choice, not a given. When we scope your app we mark each one as first release or later, because the more you add, the longer the build runs and the more it costs. Drivers choose the app that pays them best, so work out the arithmetic on your commission before you build, not after.
Payments are the make-or-break in this market
An app like Uber only works when money moves cleanly, and in East Africa that means Mobile Money first, cards second. We wire MTN MoMo and Airtel Money in Uganda and Rwanda, M-Pesa in Kenya, and Tigo Pesa, Airtel and M-Pesa in Tanzania. This is not a payment button. It needs ledgers that always balance, webhooks that confirm every transaction, retries for when the network drops mid-payment, and reconciliation so your figures and the telco's figures agree. We know this work because payments and double-entry ledgers are what we build: Moyo Pay, our dual-currency wallet platform, runs Mobile Money and USSD on a proper ledger, and Growth Informer, our own cloud POS, handles live transactions every day. That is capability evidence, not a claim that we already built a taxi app for someone else. For the mechanics, see our Mobile Money integration guide.
MVP first, full platform later
The smartest way to control cost is to launch a real MVP, not a half-built dream. An MVP is the smallest version that lets a rider book, a driver accept, both track the trip on a map, and money change hands. It skips surge pricing, wallets, promo codes, scheduled rides and the analytics suite. You launch in one town, learn what your drivers and riders actually do, then spend on the features they ask for instead of the ones you guessed. This staged path is exactly what our MVP development in East Africa approach is built for, and it is why an MVP can cost a third of a full platform while still being a live, earning product.
What it costs, priced for your region
Prices on this page adjust to your region, so you see a figure that makes sense where you work. The bands below are our general app ranges. A ride or delivery platform is a customer app, a driver app and an admin dashboard with live maps, matching and Mobile Money, so it is priced above a single app, as one fixed figure after we scope it.
| Build | What it covers | Price |
|---|---|---|
| App on one platform | A single app on Android or iOS, the reference band for any one app we build | priced for your region |
| App on Android and iOS | The same app on both platforms from one codebase | priced for your region |
| Ride or delivery platform | Customer app, driver app, admin dashboard, live maps, matching and Mobile Money | Fixed quote after scoping, above a single app |
You get one fixed figure before work starts, you pay it 50/25/25, and you own the source code and the data at the end.
Timeline and payment plan
A ride or delivery MVP is typically an 8 to 14 week build, depending on how much of the matching and payment logic you need on day one. A full platform with wallets, surge and a mature admin console runs longer. Every project runs on our 50/25/25 plan: 50% to start, 25% at the review milestone, 25% at completion. You see working screens weekly on WhatsApp, never a black box, and you own all the code and accounts at the end. For the broader picture of building for mid-range Android on slow data, see our guides on app development in Uganda and the detailed app development cost in Uganda.
What moves your number up or down
| Cheaper | More expensive |
|---|---|
| Android first, iOS later | Both platforms polished from launch |
| One city, fixed pricing | Multi-city with surge and zones |
| Cash plus one Mobile Money channel | Wallets, card gateways and every telco |
| MVP feature set | Ratings, promos, scheduling, analytics at once |
| Standard map and routing | Custom heatmaps and demand forecasting |
| Fixed fares | Driver-negotiated fares and bidding |
| One vehicle type, boda or car | Boda, cars and delivery in one platform |
The right question is not "how much is an Uber app". It is "what is the smallest version that earns in my town, and what does that cost". We quote that, in writing, before any work starts.
Tell us whether you are building for riders, food, parcels or boda deliveries, which cities, and which payment channels matter, and we will turn it into a fixed quote and a milestone plan you can budget against.
If your idea is boda only, read what an app like SafeBoda costs to build. If it is restaurant or grocery delivery, see food delivery app development in Uganda. For parcels and fleets, see delivery and logistics software.
Frequently asked questions
Can I launch a ride app in Uganda now that Uber has left?
Yes. Uber stopped operating in Uganda on 2 September 2026, and nothing about that stops you building and launching your own app. The market is not empty, though: Bolt, SafeBoda and others are already running, so most new entrants do better starting with one town or one niche, such as boda trips, parcel runs or a fixed route, than trying to serve every rider at once. Ride-hailing platforms in Uganda are brought under licensing by the Ministry of Works and Transport through the Traffic and Road Safety (Amendment) Act, 2020. Getting and keeping that licence is the operator's obligation, so confirm the current requirements with the Ministry before you launch. We build the software that supports it, including driver records, trip logs and reports, on a fixed written quote and a 50/25/25 payment plan. This is not legal advice.
How much does it cost to build an app like Uber in East Africa?
A lean but real MVP with a customer app, a driver app, an admin dashboard, live maps, matching and one Mobile Money channel is a mid-sized build, and a full platform with wallets, surge pricing and a mature back office costs considerably more. The price bands for your region are in the pricing section of this page, and your exact figure comes after scoping. You get a fixed written quote and a milestone plan before any work begins, on a 50/25/25 payment plan.
Why is a ride or delivery app more expensive than a normal business app?
Because it is really three apps working together: the customer app, the driver app and the admin dashboard, plus a live map, a dispatch engine that matches the nearest driver, and Mobile Money with proper ledgers. Each of those pieces is genuine engineering, so the total is several times the cost of a single-screen business app.
Can I launch Android only to save money?
Yes, and it usually makes sense. Most riders and drivers in Uganda, Kenya, Tanzania and Rwanda use mid-range Android phones, so an Android-first launch reaches your market for less. Because we build from one codebase with Flutter or React Native, adding iOS later is far cheaper than building two native apps from scratch.
How do payments work for a ride app here?
Mobile Money first, cards second. We integrate MTN MoMo and Airtel in Uganda and Rwanda, M-Pesa in Kenya, and Tigo Pesa, Airtel and M-Pesa in Tanzania, with ledgers, webhooks, retries and reconciliation so no fare is ever lost. This is the same payments and double-entry ledger work behind Moyo Pay and our own Growth Informer POS.
Should I start with an MVP or build the full Uber clone?
Start with an MVP. Build the smallest version that lets a rider book, a driver accept, both track on a map and money change hands, launch it in one town, then spend on the features your users actually ask for. An MVP can cost about a third of a full platform while still being a live, earning product.