What Mobile App Development Really Costs in India in 2026

Last month a founder from Pune called me, furious. He'd signed a fixed-price contract for ₹3.5 lakh to build a food-delivery app. Eight months and two "final versions" later, the app crashed on every Android phone running below version 12, the payment gateway was never integrated properly, and the vendor was now asking for another ₹1.8 lakh to "fix the architecture." He wanted to know one thing: was he stupid, or was he cheated?

The honest answer is neither. He just never got a real breakdown of what he was buying. The mobile app development cost in India ranges wildly, from ₹80,000 for a template-based app to over ₹40 lakh for something with real backend complexity, and the price you're quoted usually has very little to do with what you'll actually spend by launch day. The hidden costs are where founders bleed.

I've built and shipped apps for logistics companies, D2C brands, clinics, and a couple of fintech startups over the last decade. In this post I'll give you the itemized numbers I actually use when scoping projects, a real case study with rupee figures, a comparison of your build options, and a checklist you can hand to any vendor to keep them honest.

Key Takeaways

• A production-ready app for an Indian SMB typically costs ₹6–18 lakh in year one, not the ₹2–3 lakh most vendors advertise.
• The build quote is only about 55–65% of your real cost. Backend infrastructure, payment gateway fees, app store accounts, and post-launch maintenance are the rest.
• Fixed-price contracts feel safe but push vendors to cut corners; time-and-material with a capped estimate usually delivers better quality.
• Budget 15–20% of build cost per year for maintenance, OS updates, and bug fixes. An unmaintained app dies within 18 months.
• GST at 18% applies to almost every line item. Factor it in before you sign, and check if your vendor is MSME-registered for smoother terms.
• Native vs cross-platform (Flutter/React Native) is a real cost decision, often saving 30–40% without hurting most SMB use cases.

Why do app development quotes in India vary so much?

When someone quotes you ₹1.5 lakh and someone else quotes ₹12 lakh for what sounds like "the same app," they are not describing the same thing. They're describing different levels of engineering, and neither is lying.

The ₹1.5 lakh quote is usually a template. Someone takes an existing codebase, swaps your logo and colours, connects a basic database, and ships it. It works until you have 500 concurrent users, or until you need a feature the template never supported. The ₹12 lakh quote includes proper architecture, a scalable backend, security review, testing across real devices, and a team that will still answer your calls after launch.

The real variables that move the price:

• Number of screens and unique flows. A 10-screen app is not twice the work of a 5-screen app; complex flows like multi-step onboarding, in-app payments, and real-time tracking cost disproportionately more.
• Backend complexity. A simple content app needs almost no backend. A marketplace with buyers, sellers, orders, and payouts needs serious server-side engineering.
• Platform choice. iOS only, Android only, both, or cross-platform. This alone can swing your cost 40%.
• Team location and seniority. A Tier-1 Bangalore studio bills ₹1,200–2,500 per hour. A solid team in Indore or Coimbatore might bill ₹500–900 per hour for comparable output.
• Integrations. Payment gateways, WhatsApp notifications, maps, SMS OTP, analytics. Each one adds days.

What are the real mobile app development cost tiers in India for 2026?

Here's the breakdown I use in scoping calls. These are build costs only, before infrastructure and running costs, which I cover further down. All figures exclude 18% GST.

Tier	Example use case	Build cost (₹)	Typical timeline	Team
Template / MVP	Simple catalogue, booking form, single-user app	80,000 – 2,50,000	3–6 weeks	1–2 developers
Standard business app	Login, profiles, payments, notifications, admin panel	4,00,000 – 9,00,000	2–4 months	3–4 people
Marketplace / platform	Two-sided marketplace, real-time tracking, wallet	10,00,000 – 22,00,000	4–7 months	5–7 people
Complex / fintech / healthtech	Regulated data, high concurrency, custom ML	22,00,000 – 45,00,000+	7–12 months	8+ people

Most SMB founders think they're in tier one and end up in tier two the moment they add "and users should be able to pay inside the app." Payments alone push you across a line, because now you need secure token handling, refund logic, transaction reconciliation, and PCI-adjacent hygiene.

If you're weighing whether to build custom at all, it's worth reading our take on whether SMBs should trust AI app builders. For genuine business logic they're not there yet, but for a rough internal tool they can save you a tier.

What are the hidden costs nobody quotes you upfront?

This is where the Pune founder got burned. The build quote is the visible iceberg. Here's the rest.

App store and developer accounts

Apple charges $99/year (about ₹8,500) for a developer account. Google Play is a one-time $25 (roughly ₹2,100). These are non-negotiable and paid to Apple and Google directly, not your vendor. Make sure the account is registered under your company, not the vendor's. I've seen founders locked out of their own app because the vendor owned the developer account.

Backend and cloud infrastructure

Your app needs servers. A modest app might run on ₹3,000–8,000 per month of cloud spend. A busy marketplace can hit ₹40,000–1,50,000 per month. This is recurring and grows with your users. Getting the architecture right early matters more than the monthly bill, and our cloud migration and managed services team helps SMBs avoid over-provisioning from day one. If you're deciding between buying cloud direct or through a partner, read reselling cloud vs direct billing.

Payment gateway fees

Razorpay, Cashfree, and PayU charge roughly 2% per transaction plus GST. On UPI it's often lower or zero, but cards and net banking carry the full cut. This is not a build cost, it's a permanent tax on your revenue. Budget for it in your unit economics, not your project plan.

Third-party API costs

• SMS OTP: ₹0.12–0.20 per SMS through providers. Our bulk SMS services keep transactional OTP costs predictable at scale.
• WhatsApp notifications: increasingly the preferred channel. Order updates and alerts via the WhatsApp Business API often convert better than SMS and cost per conversation.
• Google Maps: free up to a monthly credit, then metered. A delivery app can rack up ₹15,000+/month easily.

Maintenance and updates

This is the cost that kills apps. Apple and Google release OS updates yearly. Libraries deprecate. Without maintenance, your app breaks silently. Budget 15–20% of the build cost annually just to keep the lights on. A ₹8 lakh app costs ₹1.2–1.6 lakh a year to maintain properly.

Common Mistake: Signing a build contract with no maintenance clause, then discovering six months later that "fixing the app after Android's update" is billed as new work at full rate. Always negotiate a fixed post-launch support window (I recommend 3 months free bug fixes) and an annual maintenance retainer before you sign the build contract, when you still have leverage.

A real cost breakdown: how a Jaipur clinic chain budgeted their booking app

Let me make this concrete. A three-location diagnostic clinic in Jaipur wanted a patient app: book tests, view reports, pay online, get reminders. Here's how the numbers actually landed over year one. They initially had a ₹4 lakh budget in mind.

Line item	Cost (₹)	Notes
Build (Flutter, iOS + Android)	6,80,000	Cross-platform saved ~35% vs native
Admin web panel	1,40,000	Staff manage bookings and reports
GST @ 18% on the above	1,47,600	Often forgotten in budgeting
Cloud (year 1)	72,000	~₹6,000/month, modest load
Payment gateway setup	0	2% per transaction thereafter
SMS + WhatsApp reminders (year 1)	54,000	High volume, reminders drive attendance
App store accounts	10,600	Apple + Google
Maintenance retainer (9 months)	90,000	3 months free, then ₹10K/month
Year 1 total	~11,94,200	Nearly 3x the initial mental budget

The clinic didn't overspend. They just budgeted for the visible part only. Two things saved them real money. First, they chose Flutter instead of two separate native codebases, which cut the build by over three lakh. Second, they used WhatsApp reminders instead of relying on phone calls, which dropped no-show rates and paid for the app inside the first year through recovered revenue.

The lesson: the app's ROI wasn't in the app, it was in what the app enabled. We scope every mobile app development project this way, working backward from the business outcome instead of the feature list.

Should you build native or cross-platform to save money?

For 80% of Indian SMBs, cross-platform is the right call in 2026. The two candidates are Flutter (Google) and React Native (Meta). Here's how they compare against native for a typical business app.

Criteria	Native (Swift + Kotlin)	Flutter	React Native
Relative build cost	Highest (2 codebases)	~60–65% of native	~60–70% of native
Performance	Best	Excellent	Very good
Best for	Heavy graphics, games, AR	Most business apps, clean UI	Apps sharing code with a React web app
Developer availability in India	Good	Very high	Very high
Long-term maintenance	Two teams needed	Single codebase	Single codebase

Go native only when you genuinely need it: heavy real-time video, AR features, or bleeding-edge OS APIs. For a booking app, a D2C store, a service marketplace, or an internal ops tool, cross-platform will save you lakhs and years of duplicate maintenance. Don't let a vendor upsell you native "for performance" unless they can name the specific feature that requires it.

How do you budget realistically and avoid the traps?

Here's the step-by-step process I walk founders through before they spend a rupee.

1. Write your feature list, then cut it in half. Your version one should do one thing brilliantly. Every extra feature is cost and delay. You can add the rest after real users tell you what they want.
2. Get three itemized quotes, not lump sums. Demand a line-by-line breakdown: design, frontend, backend, integrations, testing, deployment. If a vendor won't itemize, walk away.
3. Ask who owns the code and accounts. Get it in writing that source code, the Git repository, and both developer accounts belong to your company. This is the single most important clause.
4. Confirm GST and MSME status. An 18% GST is added to everything. If the vendor is MSME-registered, you get better payment terms and legal protection under the MSME Act on delayed disputes.
5. Separate build from maintenance in the contract. Negotiate both together but bill them separately, with a defined free-support window post-launch.
6. Plan your cloud architecture before coding starts. Retrofitting scalability is expensive. Our IT consulting team does architecture reviews so you don't rebuild the backend at 10,000 users.
7. Budget year one, not launch day. Add build + GST + cloud + integrations + maintenance. That's your real number. Multiply your build quote by roughly 1.6 for a safe year-one estimate.

If you don't have a technical co-founder, having an independent advisor review vendor quotes usually pays for itself many times over. Even a single consulting session can catch a ₹2 lakh mistake before it happens.

What compliance and legal costs apply to Indian apps?

This is the part most cheap vendors skip entirely, and it's where you get exposed.

• DPDP Act 2023. India's Digital Personal Data Protection Act is now in force with rules being operationalised. If your app collects personal data (and almost all do), you need a privacy policy, consent flows, and a defined data retention and deletion process. Retrofitting consent is painful; build it in from day one.
• Data localisation. Depending on your sector, you may need to store certain data within India. RBI's rules already require payment data to be stored locally. If you're unsure where your data should live, our post on data sovereignty in 2026 breaks it down.
• App store policies. Apple and Google both require a working privacy policy URL and clear disclosure of data collection before they'll approve your app. A missing policy is the most common reason first-time apps get rejected.
• GST registration. If you're taking payments through the app, your business needs GST registration. Founders operating remotely often use a virtual office address for GST and company registration to establish a valid place of business.

None of this is optional if you're serious. A privacy-compliant build costs a bit more upfront and saves you from penalties and app store rejection later.

How eDarpan approaches app projects

We don't sell apps by the screen. We start with the business outcome, scope the minimum that gets you there, and give you an itemized year-one budget with no surprises. Whether it's a custom software platform, a customer app, or connecting your app to an AI voicebot for support, we build it to scale and hand you full ownership of the code.

If you already have systems running, we also help with Google Workspace and Microsoft 365 licensing so your team's tooling doesn't become another line of hidden cost. You can see the full picture on our services overview, or just reach out for a straight-talk scoping call. No obligation, and we'll tell you if you shouldn't build an app at all.

Frequently asked questions

How much does it cost to make an app in India in 2026?

A simple template app starts around ₹80,000, a standard business app with payments and notifications runs ₹4–9 lakh, and a marketplace or fintech app can cost ₹10–45 lakh or more. Add 18% GST and roughly 1.6x the build quote to estimate your full year-one cost including cloud and maintenance.

Is Flutter cheaper than building separate iOS and Android apps?

Yes. Because Flutter uses a single codebase for both platforms, it typically costs 35–40% less to build than two native apps, and it's cheaper to maintain since you update one codebase instead of two. It's the right choice for most SMB business apps.

Why do app maintenance costs matter so much?

Apple and Google release OS updates yearly, and libraries your app depends on get deprecated. Without maintenance, your app breaks or gets removed from the store, usually within 12–18 months. Budget 15–20% of your build cost per year to keep it running.

Who should own the app source code and developer accounts?

Your company, always. Get it in writing that the Git repository, source code, and both Apple and Google developer accounts are registered to and owned by you. If the vendor holds them, you can be locked out of your own product.

Do I need to worry about the DPDP Act for my app?

If your app collects any personal data such as names, phone numbers, or location, then yes. You need a privacy policy, proper consent flows, and a data deletion process. Build these in from the start, because retrofitting compliance later is expensive and app stores will reject you without a privacy policy.

Can I use a virtual office to register my app's business for GST?

Yes. Many remote and early-stage founders use a virtual office address to obtain GST registration and establish a legal place of business without the cost of a physical office. It's a legitimate and common practice for app-first businesses.

Should I pay a fixed price or hire on time-and-material basis?

For well-defined, small projects a fixed price is fine. For anything with evolving requirements, time-and-material with a capped estimate usually delivers better quality, because fixed-price contracts pressure vendors to cut corners once they've locked the number. Negotiate a cap so you keep budget certainty either way.

The bottom line

The mobile app development cost in India in 2026 isn't a single number, it's a budget with visible and hidden layers. The founders who succeed are the ones who plan for the full year, insist on itemized quotes, own their code, and build only what version one actually needs. The ones who get burned are the ones who chase the cheapest quote and discover the real cost after launch.

Cut your feature list in half, budget 1.6x your build quote, get everything in writing, and treat maintenance as non-negotiable. Do that and your app becomes an asset instead of a liability. If you want a second opinion on a quote you've received, or a clean scope built from your business goals, talk to us. We'd rather tell you the honest number now than watch you find out the hard way.

Image credit: Sad Cartoon versus Technology by Sean Loyless via flickr (BY 2.0), sourced through Openverse.