
What an app like Uber, iFood or Airbnb costs: what's in the bill
By Leonel Rocha · Product Designer
· 7 min read
An app like Uber, iFood or Airbnb isn't one app. It's at least three products (the customer app, the partner app and the operator's dashboard), tied together by maps, split payments and real-time notifications. The price comes from the scope of the first version, not from the name of the app you're copying. On top of development, there are monthly costs for services like maps and payment payouts, and they grow with usage.
An app like Uber, iFood or Airbnb isn't one app. It's at least three products (the customer app, the partner app and the operator's dashboard), tied together by maps, split payments and real-time notifications. The price comes from the scope of the first version, not from the name of the app you're copying. On top of development, there are monthly costs for services like maps and payment payouts, and they grow with usage.
- 10,000
- free calls per month for each Google Maps Essentials service, like maps, routes and addresses
- R$6
- per active account per month, plus 0.25% + R$0.67 per payout, on Stripe Connect in Brazil when the platform sets pricing
“I want an app just like Uber, but for my industry.” It's one of the lines I hear most in a first conversation. Sometimes it's an Uber for tow trucks, sometimes an iFood for neighborhood pharmacies, sometimes an Airbnb for beach houses on the coast. The next question is always the same: how much does it cost?
The short answer is that the name of the app you're copying says almost nothing about the price. The Uber, iFood and Airbnb you use today are the result of years of evolution, built by huge teams. What you need to budget is something else: the first version that puts your model live and proves it works. In this article I show what sits behind this kind of app, what drives the price and what can wait.
An app like Uber is really three products
Every app in this model is a marketplace. It connects two sides that don't know each other (whoever buys and whoever delivers the service), with your company in the middle handling the rules and the money. In practice, that becomes at least three products:
- The customer app. Sign-up, search, order or booking, payment, tracking and ratings.
- The partner app. The driver, the courier, the restaurant or the host. They get requests, accept or decline, update the status and see how much they'll earn.
- The admin dashboard. Where your team approves partners, sets fees, handles complaints, issues refunds and tracks the numbers.
Each one has its own screens, rules and tests. That's why an “app like iFood” costs more than a single-business app, like a restaurant taking direct orders. If your real question is whether to build your own channel or stay on someone else's marketplace, I compared both paths in your own delivery app or iFood.
What drives cost: real time, maps and split money

I covered the general factors that drive the price of any app (platforms, login, integrations, dashboard, publishing) in how much it costs to build an app. In a marketplace, three items weigh much more:
- Real time. The customer wants to watch the car arrive. The restaurant needs to know about the order right away. The partner needs to get the request even with the app closed. That takes a server built to update many screens at once and reliable notifications.
- Location and maps. Showing where the partner is, calculating the route, estimating time and price by distance, autocompleting the address as the user types. Each of these is a call to a mapping service.
- Split payments. The customer pays a single amount, but the money has to be split between the partner and your company, with payouts on the right date, refunds, cancellations and invoices.
Add the part nobody sees in the demo: partner sign-up and approval, cancellation rules, ratings on both sides, support and fraud prevention. This is where scope grows without anyone noticing.
What maps cost per month
Maps are a cost that keeps running after launch. Since March 1, 2025, Google Maps Platform has replaced the old US$200 monthly credit with a free quota per service, according to Google's pricing page. The categories table sets three tiers:
- Essentials: 10,000 free calls per month, per service. This covers the dynamic map, basic route calculation, converting addresses into coordinates and address autocomplete.
- Pro: 5,000 free calls per month, per service.
- Enterprise: 1,000 free calls per month, per service.
The quota is per service and doesn't add up across services. For a small app, that covers the beginning. For an app where every order opens a map, calculates a route and updates the partner's position several times, the bill shows up fast. That's why the project needs to decide early which calls are truly necessary, when to cache a result instead of asking again and how much maps will cost per order.
Split payments: who gets paid, when and at what cost
Splitting payment between partner and platform requires a gateway that can pay out to multiple accounts. In Brazil, Stripe Connect is one example with public pricing. It offers two options:
- Stripe sets pricing for partners: the platform pays no Connect fee, and the processing fee is charged directly to the partner's account.
- The platform sets pricing: R$6 per active account per month, plus 0.25% + R$0.67 per payout sent. An account counts as active in any month it receives a payout.
There are other gateways in Brazil with split payments, each with its own rules and fees. The point is that this choice shapes your business model: who pays the fee, how many days until the partner gets paid and how much you keep on each order. It has to be made before the first payment screen, not at the end.
The store rules that change the project
Three App Store rules directly affect anyone launching an app in this model. All of them are in Apple's App Review Guidelines:
- Physical services pay no store commission. Under guideline 3.1.3(e), physical goods and services consumed outside the app must be paid for by other means, like a card or Apple Pay. Rides, deliveries and stays fall here. I explained what pays commission and what doesn't in App Store and Google Play fees.
- Copies get rejected. Guideline 4.1 asks you to “come up with your own ideas” and not copy the latest popular app with minor changes. Using another app's name, icon or brand without permission is also prohibited. “Just like Uber” works as a model reference, never as a cloned interface.
- Accounts must be deletable. Under guideline 5.1.1(v), if the app lets users create an account, it must offer account deletion inside the app. In a marketplace, that applies to both sides and affects the history of orders and payouts.
What you can cut from the first version
The way to fit the budget is to cut scope, not quality. In the first version of a marketplace, these are the cuts I usually look at:
- One city or region. Fewer partners to approve, fewer map calls, and an operation your team can follow up close.
- Partner on the web before the app. For a restaurant or host, a web dashboard works at the start. A driver or courier, out on the street, usually needs an app from day one.
- Tiered pricing instead of dynamic. A table by distance or neighborhood is simpler to build and to explain than pricing that shifts with demand.
- Weekly payouts instead of instant. Fewer payouts, lower fees and less fraud risk while volume is small.
- Support over WhatsApp. Before building a help center inside the app.
Every cut is a business decision, not just a technical one. It needs to be written down, along with what moves to the second version.
How we do it at the Studio
When someone asks for an “app like Uber,” the first thing we do is separate the three products and ask what each side needs for the first order to happen. The price is fixed after that discovery, with the scope in writing, and the deadline goes into the contract.
Our dev team is in-house. We use Claude Code and Figma for design and build. The code, files and access stay in the client's name, including the store, gateway and mapping accounts, because those accounts hold your business's money and data. And every system ships with an AI agent that runs daily, flags failures, suggests improvements and checks that the data makes sense, which in a marketplace includes making sure orders, payments and payouts match.
If you have a marketplace model to launch, bring the idea to an audit with our app development team and leave with the scope of the first version defined.
Common questions
Can you build an app like Uber for a fixed price?
Yes, as long as the scope of the first version is closed and written down. What you can't do is fix a price for a full Uber, because today's Uber is the result of years of evolution. We set the price after discovery, with a list of what's in and what comes later.
Do I need to build all three apps at once?
Not necessarily. In many cases the partner side starts as a simple web version or dashboard, and only becomes a native app when volume justifies it. The customer side is usually the one that needs to be in the stores first.
Does Apple take a cut of rides or orders?
No. Under App Store guideline 3.1.3(e), physical goods and services consumed outside the app must be paid for by other means, like a card or Apple Pay, not in-app purchase. The store's commission applies to digital content and features.
What does an app like this cost per month?
It depends on usage. You pay for servers, maps, notifications, payment fees and the updates the stores require. Some items are free up to a limit, like the 10,000 monthly calls per Google Maps Essentials service, and start being billed as the app grows.
Sources
Related service
Systems and apps
Systems, SaaS and iOS and Android apps from diagnosis to launch, with design, code and AI on the same team
News Responsivo
Get the next article in your inbox
Cost, timelines, AI and behind the scenes of shipping products. No spam.


