App development cost in India: the real bill arrives in year two

A founder once put three quotes for the same app on our table. One agency proposed Flutter, one React Native, and one a pair of native apps in Swift and Kotlin. The first two totals were almost identical. The native quote was about 40% higher, and she could not tell whether the extra money bought anything.

We asked her a different question. Who fixes this app next October, when new versions of iOS and Android arrive and the payment library needs an update in the same week?

That question is the whole of this guide. On the whiteboard in our Mumbai studio, every app estimate gets two columns, and the second is always headed “year two”. Founders tend to photograph the first column. I ask them to photograph the second. Below: what an app costs to build in India in 2026, why Flutter and React Native quotes look so alike, and where the three approaches part ways once the app is live.

What an app costs to build in India in 2026

These are the ranges we quote for a first release on iOS and Android together, built cross platform. They include product design, the backend, an admin panel, testing and the store launch, delivered by a senior team in India. They leave out marketing, content writing and your own team’s time.

Scope	What it usually includes	INR	USD	AED	Timeline
Focused first release	Sign-in, 10 to 20 screens, one core flow, notifications, a simple admin panel	₹12 to 18 lakh	US$15,000 to 22,000	AED 55,000 to 80,000	12 to 14 weeks
Growth app	Payments, accounts, a catalogue or bookings, loyalty, analytics, links to your store or CRM	₹18 to 33 lakh	US$22,000 to 40,000	AED 80,000 to 147,000	14 to 20 weeks
Platform app	Several user roles, live tracking, offline sync, marketplace payouts, heavy integrations	₹35 lakh upwards	US$42,000 upwards	AED 155,000 upwards	20 to 32 weeks

Most projects open with a three week Discovery Sprint, from ₹3.5 lakh / US$4,000 / AED 15,000, which ends in a tested prototype and a fixed price for the build. A Product Build starts from ₹12 lakh / US$15,000 / AED 55,000. Both follow the same Ampersand Method we use for every product.

If you are researching app development cost in Dubai, the same scope built by a local Gulf team usually costs more, because senior salaries there are higher. Location is the smaller decision, though. Notice what is missing from the table above: the framework. That is deliberate.

Flutter, React Native and native, in plain words

We build in all three through our mobile app development practice, so we gain nothing by selling you one. First, vocabulary. People often ask about native vs hybrid apps. “Hybrid” used to mean a web page wrapped inside an app, and those apps earned their sluggish reputation. Modern Flutter and React Native apps are not that. They are cross platform: one codebase, a proper app in each store.

Flutter

An open source toolkit written in Dart. Flutter draws every pixel on screen with its own rendering engine, so an app looks and behaves the same on iOS and Android. That makes it a natural fit for brand-led apps with custom motion and a strong visual identity. The trade-off is a smaller hiring pool, and screens that feel slightly foreign on each platform unless someone adds platform polish on purpose.

React Native

An open source framework written in JavaScript or TypeScript. It uses each platform’s own interface components, and its newer architecture, now the default, answered most of the old performance complaints. Its biggest advantage is people. If your web team already writes React, then code, tooling and developers can move between your website and your app.

Native Swift and Kotlin

Two separate apps: Swift for iOS, Kotlin for Android, each built with the platform’s own tools. You get the most direct route to the camera, sensors and Bluetooth, and every new OS feature on the day it ships. You also pay for the app layer twice, in year one and in every year after.

Factor	Flutter	React Native	Native (Swift and Kotlin)
Codebases for iOS and Android	One	One	Two
Year one build, same scope	Baseline	Within about 5% of Flutter	About 40 to 50% more
Hiring in India	Fewer candidates, often specialists	The largest pool, thanks to React on the web	Two separate hires, both in demand
Camera, AR, Bluetooth, background work	Good, through plugins	Good, through native modules	Best
Yearly upkeep	One codebase plus plugin upgrades	One codebase plus library upgrades	Two codebases to update and test

Why year one quotes look alike

Because the framework only touches part of the bill. In a typical cross platform build, the app layer, meaning the code that runs on the phone, is less than half of the cost. Design, the backend, the admin panel, testing and the store launch cost much the same whether the screens are written in Dart or TypeScript.

Where a ₹24 lakh cross platform build goes	Cost	Share	Changes with the framework?
Product, UX and UI design	₹4.5 lakh	19%	Barely
App layer on the phone	₹11 lakh	46%	Yes
Backend, APIs and admin panel	₹6.5 lakh	27%	No
Testing, release and store launch	₹2 lakh	8%	Slightly

Flutter and React Native need roughly the same effort on the app layer, so honest quotes land within a few percent of each other. Native writes that layer twice, at around ₹10 lakh per platform, adds design time for two sets of platform conventions and doubles the testing. That is how ₹24 lakh becomes about ₹35 lakh: more, but nowhere near double, which is why the native quote on that founder’s table was 40% higher rather than 100%.

So if year one does not separate the three, what does? Three things, and they all arrive after launch.

Where the three really differ

Hiring: who looks after it in year two

In India, the deepest pool of mobile talent sits around React, because so many web developers write it every day. A React Native app can often be maintained, at least for small changes, by the people who already look after your website. Good Flutter engineers are fewer, which is fine when a studio maintains the app and harder when you plan to bring it in-house. Native means two hires, one for Swift and one for Kotlin, and whichever of them is on leave becomes the bottleneck.

Performance: where it actually matters

In commerce, booking, learning and content apps, people cannot tell a well built Flutter or React Native app from a native one. The gap shows in narrow places: continuous camera processing, AR, maps with thousands of live markers, audio work and long background tasks. Flutter apps also carry a slightly larger minimum download, which matters to people who clear storage every few weeks. Whatever the stack, we test on a mid range Android that is a few years old, over a throttled connection, because that phone is far closer to your customer than the one on the founder’s desk.

Maintenance: the autumn bill

Every September and October, new versions of iOS and Android arrive. Google Play asks every app to target a recent Android version each year, and Apple expects new builds to use its latest tools. Libraries for payments, maps and notifications follow their own schedules. With one codebase, that is one round of upgrades and one round of testing. With native it is two, done by two people, and the release waits for the slower one. This is why the native gap widens after launch instead of closing.

A worked example: one app, two ways, two years

Here is a composite of a brief we see often. A D2C tea brand in Mumbai has 30,000 repeat customers on its online store and wants an app for its regulars: saved orders, subscriptions, one tap reorder, loyalty points shared with the website, UPI and card payments, and notifications people do not mute. In the table above, that is a growth app.

Line	Cross platform	Native (two apps)
Discovery Sprint, three weeks	₹3.5 lakh	₹3.5 lakh
First release build	₹24 lakh (16 weeks)	₹35 lakh (20 weeks)
Care after launch, rest of year one	₹2.8 lakh (7 months at ₹40,000)	₹3.9 lakh (6 months at ₹65,000)
Hosting, notifications and store fees	₹0.7 lakh	₹0.6 lakh
Year one total	₹31 lakh	₹43 lakh
Care for twelve months	₹4.8 lakh	₹7.8 lakh
Two feature releases	₹6.5 lakh	₹11 lakh
Hosting and services	₹1.2 lakh	₹1.2 lakh
Year two total	₹12.5 lakh	₹20 lakh
Two year total	₹43.5 lakh	₹63 lakh

Watch the gap. In year one, native costs about 39% more. In year two it costs 60% more, because every OS update and every new feature is done twice. Over two years the cross platform route saves ₹19.5 lakh, a little over 30%. That is roughly US$53,000 against US$77,000, or AED 194,000 against AED 281,000.

Flutter or React Native for this brand?

We would choose React Native. The brand’s web team already works in React, so loyalty logic can be shared and its in-house developer can ship small changes without waiting for us. The same reasoning put the Dubai skincare brand’s app on React Native beside its Next.js storefront, sharing one catalogue and one customer account. Had the tea brand wanted a playful, heavily animated app with no web team to share code with, Flutter would have been the stronger pick, at almost exactly the same price.

If the brand later wants a camera feature that recognises a tin and plays brewing guidance, we would add it as a native module inside the cross platform app, not rebuild everything for one screen.

What year two actually pays for

Year two line	What it covers	Typical cost
Keeping it healthy	OS updates, store policy changes, security patches, crash fixes, library upgrades	15 to 20% of the build a year
Improving it	New features, experiments, fixes to what the analytics reveal	20 to 30% of the build a year, if you are growing
Running it	Hosting, database, push notifications, OTP messages, maps, email	₹3,000 to ₹15,000 a month for a small app
Store accounts	Apple developer account and Google Play Console	US$99 a year, plus a one time US$25

A Care & Grow plan, from ₹40,000 a month / US$500 / AED 1,800 a month, rolls the first line and part of the second into one monthly fee, with monitoring, agreed response times and a planned release each month. Whoever does the work, budget for year two before you sign for year one. An app with no maintenance budget decays: a payment library is retired, a store warning arrives, and one autumn it quietly stops installing on new phones.

The decision matrix

If this describes you	Flutter	React Native	Native
Brand-led design and custom motion, no web team to share code with	Best fit	Good	Good, at a higher cost
Your web team writes React and TypeScript	Good	Best fit	Poor fit
A tight budget, with iOS and Android from day one	Best fit	Best fit	Poor fit
You plan to hire in-house within a year	Good	Best fit	Good, if you can hire two
Camera, AR, Bluetooth hardware or background location at the core	Possible	Possible	Best fit
Widgets, watch apps or new OS features on release day	Partial	Partial	Best fit
A native app that works today, with a native team behind it	Rarely worth a rewrite	Rarely worth a rewrite	Keep it

When two columns tie, pick the one your year two team already knows. That single rule settles more of these debates than any benchmark.

A short checklist before you ask for quotes

• Write down the one job the app must do better than your website. If you cannot, a faster mobile site may be the better first step, and our website cost guide covers that budget.
• List every type of user. Each extra role, such as a driver, a vendor or an admin, is close to another product.
• Name the integrations: payments, your store, CRM, ERP, maps and SMS.
• Decide who maintains the app in year two, and what they already know.
• Ask every studio for year one and year two costs on the same page.
• Ask which phone they test on, and whether it resembles the one your customers carry.
• Confirm that the code, store accounts and signing keys sit in your company’s name from day one.
• Put 15 to 20% of the build into next year’s budget before you sign this year’s.

For a fuller template, see how to brief a digital product studio.

The number worth asking for

The cheapest year one quote is rarely the cheapest app. Flutter and React Native will cost you about the same to build. Native will cost more, though less than double. What separates them is who looks after the app, how often it needs attention, and whether the stack suits your customers’ phones and your team. Ask for the two year number, and choose the stack your year two team can live with.

If you would like a second opinion on quotes you already hold, or a two column estimate of your own, send us the brief. A partner from our mobile app development team replies within one working day, usually with a few sharp questions first.