Disclosure up front: I work at ZoopCoder, an Indian dev studio. The rupee figures below are the ones we publish on our own pricing page, shown next to the wider market band — including the tiers cheaper than us.
"Cross-platform saves you 30–40%" is repeated so often that it has stopped meaning anything. I want to put actual numbers under it, from the Indian market in 2026, and then argue about where the saving really comes from — because it is not where most people think.
The numbers first
Relative build cost, same app, same scope:
| Approach | Relative cost | Choose it when |
|---|---|---|
| Flutter (one codebase) | Baseline — 100% | Most business, commerce, booking and content apps |
| React Native (one codebase) | ~100% | You already have a React web team and want to share skills |
| Android native only | 70–80% | India-only audience (Android ≈ 95% of the market here) |
| Native Android and native iOS | 150–180% | Heavy hardware use, background processing, platform-specific features |
In rupees, for a medium-complexity app (logins, payments, admin panel, two user roles), the cross-platform build lands at ₹1,00,000–₹2,50,000 at a small Indian agency, on an 8–14 week timeline. The two-native-codebases version of that same app is the 150–180% row.
Where the saving actually comes from
It is not mostly the UI layer. That is the intuition — "one widget tree instead of two" — and it is the smaller half.
The bigger half is everything that silently doubles when you have two codebases:
- Test suites. Two of them. Every business rule asserted twice.
- CI pipelines. Two build matrices, two signing setups, two flake surfaces.
- Release trains. Two store submissions, two review rejections to argue with, two rollback plans.
- Bug triage. Every bug now has a "does it repro on the other platform?" step before you can even file it.
- OS updates. Android and iOS each ship a major version annually. Two codebases means you pay that tax twice, every year, forever.
That last point is why I think the 150–180% number understates native's true cost. The 150–180% is the build. The maintenance delta never ends — and in India that shows up as ₹5,000–₹30,000/month of maintenance that quietly becomes two streams instead of one.
When native is still the right call
I am not arguing Flutter always wins. Pay for native when the app's core value depends on the platform:
- Heavy device hardware (camera pipelines, sensors, Bluetooth peripherals)
- Serious background processing
- Platform-specific features you'd otherwise be fighting a plugin to reach
If you are writing a business, commerce, booking or content app, though, you are usually paying the native premium for nothing — and paying it again every year.
The costs the framework choice doesn't change
Whatever you pick, these don't move, and they're the ones that catch first-time app owners:
- Google Play Console: $25, one-time
- Apple Developer Program: $99/year — stop paying and the app is delisted
- Backend hosting: ₹3,000–₹25,000/month, scaling with active users
- Maintenance: ₹5,000–₹30,000/month — an unmaintained app breaks in roughly 12–18 months
Budget for these on day one, or you have built something with an expiry date and not noticed.
Full breakdown — cost by complexity, by app type (brochure → fintech), vendor rate bands from freelancer to enterprise, and timelines: https://zoopcoder.com/guides/mobile-app-development-cost-in-india.php
If you think the 150–180% figure is wrong for your stack, I'd genuinely like to hear it — that number is the one I'm least certain generalises.
Top comments (1)
The real cost comparison the article is pointing at involves a few moving parts that many Indian businesses don't fully model out. Specifically on the GST dimension:
The input credit math:
If you are a GST-registered business buying from a GST-registered vendor in India, you pay 18% GST on the invoice, but you claim it back as input tax credit (ITC) in your GSTR-3B. Net GST cost = 0 (cash flow delay only , you pay this month and claim it next month when filing 3B).
If you buy from an unregistered vendor (no GST), you pay 0% GST on invoice, but there's no input credit. Cost = face value.
Where it gets interesting:
For services purchased from foreign vendors (SaaS, AI tools), you apply Reverse Charge Mechanism (RCM) , self-account 18% IGST. You pay this to the government, then claim it back as ITC in the same return period. Net: near zero (slight cash flow cost, no actual tax cost if your output tax exceeds your RCM liability).
The 30-40% saving scenario:
This typically arises when comparing:
For businesses with >90% output GST ratio, the registered vendor is almost always cheaper on a net-of-ITC basis.
One check the article may have covered: verify the vendor has actually filed their GSTR-1 and the invoice appears in your GSTR-2B. If it doesn't match, your ITC claim is blocked under the current reconciliation rules.