Two founders ask us the same question in the same week. One has a booking app for a small chain of studios. The other has a marketplace with payments, chat and two types of users.
The honest answer is that the framework is not what sets the price. Scope sets the price. React Native changes the maths in one important way, because one codebase serves both iPhone and Android. But features, integrations, design depth and backend work still decide whether you are looking at a focused first version or a serious platform build.
TL;DR: A simple React Native app with a handful of screens and no custom backend typically lands in the $15,000 to $40,000 range with a US agency. A mid-level app with accounts, payments and a backend usually runs $40,000 to $90,000. A complex app or marketplace is commonly $90,000 to $200,000 or more. Building the same app natively for iOS and Android separately often adds 60 to 80 percent on top of the app build itself, because almost everything gets built and tested twice. Maintenance after launch usually adds 15 to 20 percent of the build cost per year.
These are market ranges founders see across US agencies, not a quote. This post shows where the money goes, so you can judge any quote, including ours.
1. React Native App Cost by App Type
The fastest way to sanity check a quote is to place your app in the right band first. Most founder apps fall into one of four groups.
Simple app: Typical React Native cost: $15,000 to $40,000; What is usually included: 5 to 10 screens, standard login, content or booking flow, no custom backend or a very light one
Mid-level app: Typical React Native cost: $40,000 to $90,000; What is usually included: Accounts, payments, a custom backend, an admin panel, push notifications, one or two integrations
Complex app: Typical React Native cost: $90,000 to $150,000; What is usually included: Real time features, chat, maps and location, multiple user roles, several integrations, heavier QA
Marketplace or platform: Typical React Native cost: $120,000 to $200,000+; What is usually included: Two user types, two apps or one app with two modes, payments and payouts, trust and safety, a full admin system
How to read this table:
Design depth moves you within a band. Template-like screens sit at the low end. Custom animation and brand work sit at the high end.
The backend is often the hidden half. Founders price the screens they can see. Accounts, data, payments and admin tools are built behind them.
Store launch and first release support are usually included in an agency build. Ongoing maintenance usually is not, and is priced separately.
If a quote lands far below the band for your app type, something has been left out. If it lands far above, ask which features are driving it. Both answers are useful, and both are cheaper to learn before you sign.
2. Why One Codebase Changes the Maths
React Native lets one team build one app that runs on both iOS and Android. To see what that saves, compare it with building two separate native apps for the same product.
The same mid-level app, priced three ways:
React Native, one codebase: one design pass, one build, one test cycle, one team. Call this the baseline, for example $60,000.
Two native apps: the design is shared, but the iPhone app and the Android app are built as two separate engineering projects. Two builds, two test cycles, and often two sets of specialists. The same scope commonly lands around $95,000 to $110,000.
Native iOS only: the cheapest build today, perhaps $50,000 to $55,000 for the same scope, but Android users get nothing, and adding Android later costs close to a second full build.
The saving is not magic and it is not exactly half. Design, backend and project management are shared in every model, so they do not halve. What you save is the duplicated app build and the duplicated testing. As a working rule, one codebase usually saves 30 to 40 percent against building both platforms natively, and it saves far more over the life of the app, because every future feature is also built once.
We compare the engineering trade-offs honestly in our guide on React Native vs native app development. There are cases where native is the right call, mainly apps built around heavy device hardware or extreme performance needs. For most founder apps, booking, commerce, content, community and business tools, the cost case for one codebase is strong.
3. What Actually Drives React Native Development Cost Up
When founders ask how much does react native development cost for their specific idea, these are the factors that move the number most.
The biggest cost drivers:
Number of distinct flows, not screens. Ten screens in one simple flow are cheap. Three flows with branching rules, like buyer, seller and admin, are not.
Payments and payouts. Taking a card payment is standard. Paying money out to other users, holding funds and handling refunds and disputes is a different level of work and testing.
Integrations. Each external service, maps, chat, video, shipping, a CRM or an existing internal system, adds build time plus testing against a system you do not control.
Real time behaviour. Live chat, live tracking and live availability need infrastructure that stays awake and scales, not just screens.
Accounts, roles and permissions. One user type is simple. Staff, customers and admins who each see and do different things multiply the design, build and QA work.
Design ambition. A clean standard interface is fast to build. Custom transitions, complex charts and heavily branded screens take specialist time.
Data migration. Moving users, content or transaction history from an old system adds careful, unglamorous work that cannot be rushed safely.
Compliance. Healthcare, finance and children-facing apps carry legal and store requirements that add scope in design, security and review handling.
A useful test: if a feature needs the words "and then it automatically" in your description, it is probably more expensive than it sounds. Automation is backend work, rules and edge cases, not a screen.
None of this means cut these features blindly. It means price them knowingly. The common budget failure is a quote that assumed the simple version of each feature, and a founder who expected the complete version.
4. The Costs Around the Build That Founders Forget
The build quote is not the whole react native app cost in year one. Budget for the items around it, because none of them are optional for a live app.
Developer accounts: Apple charges $99 per year and Google charges a one time $25 fee. Small numbers, but the accounts must be in your company name.
Backend hosting and services: a modest live app usually runs on $50 to $500 a month of hosting, database, storage, email and push services at first, rising with usage.
Third party subscriptions: maps, analytics, crash reporting, messaging and payment tools often start free and become monthly costs as you grow. Payment processors also take a percentage of every transaction.
Your own time: discovery answers, prototype reviews and weekly build testing. A founder who disappears for three weeks does not save money. The project waits, then pays to restart.
Our breakdown of what app development costs covers these surrounding costs in general, and the same list applies here.
5. What Maintenance Adds After Launch
A React Native app is not a one time purchase. Plan on 15 to 20 percent of the original build cost per year to keep it healthy. On a $60,000 build, that is roughly $9,000 to $12,000 a year, whether it arrives as a monthly retainer or as a series of urgent one off fixes. The retainer version is almost always cheaper in practice, because the work is planned instead of panicked.
What that money actually buys:
Operating system updates. iOS and Android release major versions every year. React Native apps need testing and usually small fixes against each one.
React Native and library upgrades. The framework moves fast. Staying current in small steps is cheap. Jumping three versions at once, after something breaks, is not.
Store compliance. Both stores raise target requirements and change privacy rules regularly. Miss a deadline and your update gets blocked.
Crash fixing and small improvements. Real users find edge cases no test pass caught. Batching those fixes into regular releases is the normal rhythm of a live app.
One genuine React Native advantage shows up here too. Over the air updates let a team ship many fixes and small changes instantly, without waiting for store review, and one fix covers both platforms at once. That lowers the cost of every release for the life of the app.
Our post on mobile app development services sets out what a full service should cover at each stage, including handover and maintenance.
6. How to Lower the Cost Without Building a Worse App
Founders usually cannot change their budget. They can change what the budget buys first.
Cut scope, not quality. Launch with the one flow that makes money or proves demand. A small app built properly beats a big app built thinly, and you can add features to a healthy codebase later.
Use one codebase. This is the React Native decision itself. For a two platform launch it is the single biggest saving available, and it keeps saving on every release.
Use proven services instead of custom builds. Payments, chat, maps and analytics all have mature providers. Paying a small monthly fee beats paying to build and maintain your own version.
Decide design once. Approve a clickable prototype before engineering starts. Changing a prototype costs hours. Changing built screens costs weeks, and it is the most common reason builds overrun.
Keep one decision maker. Every extra approver adds review rounds. Review rounds are billed time, whichever pricing model you are on.
Do not skip QA or security to save money. These are the cuts that come back as public reviews, refunds and rebuilds. Founders who have been burned once already know this is the most expensive saving there is.
Our React Native app development page explains how we scope these projects, and the questions to ask any team before you compare numbers.
7. So, What Should You Budget?
Pulling it together for a typical founder plan:
Testing an idea: budget $15,000 to $40,000 for a simple, real, store-ready app, not a demo that has to be thrown away.
Launching a serious product: budget $40,000 to $90,000 for the build, plus hosting and services, plus 15 to 20 percent a year for maintenance.
Building a marketplace or platform: budget $120,000 upward for the first version, and expect the admin, payments and trust work to be as large as the customer facing app.
If those ranges are far above what you have, the answer is usually a smaller first version, not a cheaper builder. A tight scope on a proper foundation can grow. A full scope on a weak foundation has to be rebuilt, and a rebuild means paying for the app twice. Our guide on how to take an MVP to production shows how to plan that first version so it does not need to be discarded later.
Get the scope priced properly before you compare builders. Two quotes are only comparable when both teams are pricing the same flows, the same integrations and the same standard of testing.
Frequently Asked Questions
How much does a React Native app cost for a startup? Most startup first versions built by a US agency land between $15,000 and $90,000, depending on scope. A simple store-ready app sits at the low end. Accounts, payments, a custom backend and an admin panel move it into the mid range. Marketplaces and real time apps cost more.
Is React Native cheaper than building native apps? For a launch on both iOS and Android, usually yes, by roughly 30 to 40 percent on the total build, because the app is designed, built and tested once instead of twice. The saving continues after launch, since every feature and fix is also built once. For a single platform app, native can be slightly cheaper to build, but it closes the door on the other platform.
How much does React Native development cost per hour? Rates vary by location and seniority. US agency teams commonly charge in the $75 to $150 per hour range, while offshore freelancers quote far less and carry far more risk on communication, testing and handover. The same app can take one team twice as long as another, which is why a fixed scope and a total price matter more than the rate.
Why do React Native quotes vary so much for the same app? Because teams price different assumptions: which features are included, how much design and testing is in the number, whether the backend and admin panel are included, and what happens after launch. Ask each team to list what is included and excluded, then compare those lists, not just the totals.
Does React Native cost more to maintain? No. Maintenance is usually cheaper than for two native apps, because OS updates, framework upgrades and fixes are handled in one codebase. Budget the standard 15 to 20 percent of build cost per year, with over the air updates reducing the cost and delay of small releases.
Can I start with a smaller React Native app and add features later? Yes, and for most founders that is the right plan. Start with the core flow, built on a proper foundation with real accounts, a clean backend and tested code. Adding features to that foundation is routine work. The expensive path is an oversized scope on a weak foundation, then a rebuild in year two.
Get a React Native Cost Estimate Based on Your Actual Scope
Ranges only take you so far. The number that matters is the one attached to your flows, your integrations and your launch plan.
Tell us what your app needs to do and who uses it. My team will map the scope, place it in the right band, and tell you plainly where the cost sits and what could be cut or staged without weakening the product.
Want that estimate before you commit to a budget? Message us and we will work through your scope this week.
Code Baiz is a mobile and web app development agency in Brooklyn, New York. Our team of around 20 engineers has shipped more than 300 projects since 2019, most of them in React Native. We build, rescue and maintain apps for founders who cannot afford to get it wrong twice.