Disclosure: I work at ZoopCoder, a small development agency in India. We build in both React Native and Flutter, and our internal default is Flutter — so discount everything below accordingly. I've linked our own pricing at the end so you can check whether I'm quoting real numbers or marketing ones.
I've watched this argument happen in maybe forty client kickoffs now, and it almost always gets decided on the wrong axis. Someone brings a comparison table full of rendering-engine details, someone else says "Flutter will be cheaper," and the actual cost driver never comes up.
So here is the uncomfortable version, with our real published numbers.
The build cost is identical, and I'll show you our own price list to prove it
This is the part agencies avoid publishing because it removes a sales lever. Here is what we charge for the same scope in each framework:
| What you're building | React Native | Flutter | What actually moves the price |
|---|---|---|---|
| Simple app, 4–8 screens, no login | ₹50,000 – ₹1,00,000 | ₹50,000 – ₹1,00,000 | Screen count, how custom the design is |
| Medium app, logins + payments | ₹1,00,000 – ₹2,50,000 | ₹1,00,000 – ₹2,50,000 | The backend and the payment gateway |
| Marketplace / on-demand | ₹2,50,000+ | ₹2,50,000+ | User roles, live tracking, payouts |
| Backend hosting, monthly | ₹3,000 – ₹25,000 | ₹3,000 – ₹25,000 | Users and data — framework irrelevant |
| Maintenance, monthly | ₹5,000 – ₹30,000 | ₹5,000 – ₹30,000 | OS releases, store policy changes |
The columns are the same on purpose. What consumes an app budget is screen design, API integration, the payment gateway, testing on real low-end Indian Android devices, and getting through store review. Every one of those costs the same in Dart as it does in TypeScript.
If a vendor quotes you meaningfully cheaper "because Flutter," they are discounting to win the job and will find the money back somewhere. That's worth saying plainly even though it's a sentence that costs us work.
So what does the framework actually decide? Your year-two hiring cost
The rule we use internally:
Pick Flutter if the app is under about ₹2,50,000 and its job is screens, forms, lists and payments. Pick React Native if you already run a React or Next.js web product, or if you plan to hire an in-house mobile developer in India within twelve months.
That second clause is the one that matters and the one nobody prices. React Native recruits out of the enormous Indian JavaScript pool — the same pool your web hiring already draws from. Dart is a separate specialism with much thinner local supply, so you wait longer and pay more for equivalent seniority.
Note what is not on that list: code sharing with your React website. You do not share code. You share the language, the tooling, the state patterns, the reviewers and the hiring pipeline. That distinction has cost founders real money when they budgeted for the first and got the second.
The thing that makes "which one builds faster" irrelevant
Framework comparisons argue about build speed in days. Your launch date is decided by something almost no RN-vs-Flutter article mentions.
If you publish under a personal Google Play developer account opened after November 2023, Google requires a closed test with at least 12 testers opted in continuously for 14 days before you can even apply for production access.
Not 12 downloads. Twelve people opted in and staying opted in, for a fortnight, before the application is even accepted. Apple review then adds its own days on the other platform.
That is a two-to-three week gate that is completely indifferent to your framework, your agency, and your code quality. A framework choice that saves three developer-days cannot save you a fortnight of Google's clock.
Two practical consequences:
- Put the store gate in the plan before anyone argues about compile times.
- Start recruiting your 12 testers while the app is still being built. Staff, friends, early customers, a WhatsApp group. For a small business with no existing user base this is a genuinely hard requirement, and in our experience it is the single most common reason a first app launches later than promised.
An organisation-type developer account is exempt from the 12-tester rule, which is often reason enough to register one properly.
Cross-platform means one codebase, not one machine
iOS release builds must be compiled and signed on macOS — in React Native and in Flutter alike. Neither framework removes Apple's requirement. Add the Apple Developer Program (99 USD/yr) and Google Play's one-time 25 USD, and if nobody on the project owns a Mac you are paying for hardware or a cloud build service on top of the quote.
Ask any vendor, in writing, whether iOS build and signing infrastructure sits inside their price. It is the most common surprise line in an Indian cross-platform budget, and choosing the other framework does not avoid it.
Where we tell clients to overrule our own Flutter default
We prefer Flutter. An agency that recommends the same framework to every client is describing its own comfort, not your project. The cases where we say React Native against our own preference:
- You already run a React or Next.js web product. Strongest tie-breaker on the list; wins on its own.
- You'll hire an in-house mobile developer in India within a year. Hire-ability beats everything on the feature table.
- A vendor SDK you depend on ships React Native support first. Some payment, KYC, chat and analytics providers still maintain an official RN package and leave Flutter to the community. One missing official SDK becomes weeks of native bridging. Listing every SDK your app needs and checking both takes about an hour and has reversed the decision on real projects of ours.
- Install size is a real constraint. Flutter adds roughly 4–8 MB. For most apps that's noise. Selling into price-sensitive markets on entry-level Android phones with tight storage, it can be conversion.
And the mirror image — we hold the Flutter line for heavily animated, design-led apps, anything that must look pixel-identical across devices, and a first app at a company with no existing JavaScript team.
What getting it wrong costs
Switching frameworks later is not a migration, it's a rewrite. Budget 60–80% of the original build: every screen built again from scratch, while the backend, API, design and product decisions carry over. On a ₹2,00,000 app that's ₹1,20,000–₹1,60,000 to arrive exactly where you already were, feature for feature, with nothing new to show a customer.
Which is why the protective move matters more than the choice: keep business logic on the server, not in the app. Anything that lives on your backend survives a framework change untouched.
The full version of this — the buyer-facing comparison table, both price columns, and the store-gate detail — is on our site: React Native vs Flutter in India (2026). Our actual price list is at zoopcoder.com/pricing.php if you want to check the numbers above against what we publish.
Third-party figures (Apple/Google fees, Play Console policy) are accurate as of July 2026 and do move — verify against the console before you rely on them.
