How much does it really cost to build an app in India in 2026? A founder's honest breakdown

Ask ten business owners in India what an app costs and most give you the same answer: lakhs of rupees and several months of waiting. For years, they were right. I've spent 15 years building and shipping apps, and that genuinely used to be the honest answer.

It isn't anymore. The economics changed, and most people are still quoting — and paying — 2019 prices for a 2026 problem. This is the full, honest breakdown: what an app really costs in 2026, the four things that actually move the number, the bills nobody prints on the quote, and how to read a proposal so you never overpay. By the end you'll be able to look at any quote and know within a minute whether it's fair.

The short answer, and why the range is so wide

Let me give you the real numbers first, then explain them. Here's what a store-ready app costs in India in 2026, depending on how it's built. "Store-ready" means live on the Play Store and App Store, not a demo on someone's laptop.

Those agency figures aren't made up — they track the going market. Across 2026, Indian agencies bill blended team rates of roughly ₹1,200–₹2,500 an hour, freelancers ₹500–₹1,000, and a "medium complexity" app with logins, a dashboard and payments is widely quoted at ₹10–30 lakh. A basic app still lands at ₹3–8 lakh at most shops. Those numbers are real — but they describe the old way of building, where every app is assembled from an empty screen.

Here's the thing almost nobody tells small-business owners: you are very rarely in the top row. You think you need a fully custom app. You almost always need six to ten screens that do a few things reliably — and in 2026 that's the third row, not the first. The gap between those two rows is the single biggest source of overspending in this industry.

Want a real number for your own app right now? Our free app cost calculator gives you an instant estimate — pick your app type and features and see a real price, delivery time and what's included, with no signup.

What actually drives the price

The number on a quote isn't random, and it isn't mostly about "how good the developer is." Four things move it more than everything else combined. Understand these and you can control your own cost.

1. The number of screens

This is the biggest lever. A simple app has about five or six screens: a home or landing screen, a list (products, services, classes), a detail page, a form or cart, and a profile. Every additional screen is real design and build work — layout, states, edge cases, testing.

Scope creep here is the number-one reason a ₹15,000 app quietly becomes a ₹60,000 one. Someone says "while we're at it, let's add a rewards screen, a blog, a referral system…" and each addition feels small. It isn't. Before you approve any screen, ask one question: does this screen either save me time or make me money? If it does neither in the first version, it waits.

2. Whether you need a backend

A "brochure" app that simply shows your services, gallery and contact details is cheap, because there's no data to store or manage. The moment you need to store and change things — orders, bookings, inventory, users, messages — you need a backend (a database) and an admin panel to run it.

This is a genuine step up in cost, and it's usually worth every rupee, because a backend is what turns an app from a digital pamphlet into something that runs part of your business. But be honest about whether you need it yet. Many businesses launch beautifully with a no-backend app and add one once they've proven people actually use the thing.

3. Whether you take payments

Accepting money inside the app — UPI or cards — adds a payment gateway (Razorpay, PhonePe and the like), plus the careful testing that anything touching real money demands: successful payments, failed payments, refunds, disputes, receipts. It's not hugely expensive on its own, but it must be done properly, because a payment bug doesn't just annoy a user, it loses their money and your trust. If selling or taking deposits in-app is core to your model, pay for this and pay for it to be tested well.

4. How many outside tools you connect

Every integration — a delivery partner, Google Calendar, WhatsApp, a CRM, an accounting tool, a shipping API — is extra work to build, authenticate and test, and something that can break when the other company changes their system. One or two integrations is normal and healthy. Five is a different, more expensive project, and each one is a small ongoing maintenance commitment. Be ruthless about which connections genuinely earn their place.

A rule that has saved my clients lakhs over the years: every feature you add should either save you time or make you money. If it does neither, cut it from version one. You can always add it later — and by then you'll know whether you actually need it.

What AI genuinely changed (and what it didn't)

People assume AI simply made apps cheaper by magic. That's not quite it. AI changed which parts of building an app are expensive, and understanding that is how you save money without getting burned.

The planning and design stages used to eat weeks and a big chunk of the budget: discovery calls, requirement documents, wireframes, revision rounds, more calls. Today, you can describe your app in plain English and get a structured blueprint and live, on-brand mockups in minutes. At Roy Digital we do exactly this — the plan and the look are near-instant now, which strips out a whole layer of slow, billable time that used to sit at the front of every project.

What AI did not remove is the real craft. Your app still has to be assembled properly, themed accurately to your brand, tested on actual phones (not just an emulator), and submitted to both stores by someone who has done it before and knows why apps get rejected. That last part matters more than people realise — a meaningful share of first submissions bounce for avoidable reasons: missing privacy policy, unclear permissions, broken links, login required for reviewers with no test account. This is exactly why "I'll just get AI to build my whole app for free" usually ends in something that half-works, looks a bit off, and never actually reaches the store.

So the saving is real — but it comes from cutting the slow, wasteful stages, not from skipping the work that makes an app trustworthy enough to put your name on.

The bills nobody puts on the quote

This is where people feel ambushed three weeks after saying yes. Budget for these from day one and there are no surprises.

• Store accounts. A Google Play developer account is a one-time fee of about $25. An Apple Developer account is about $99 per year. Google and Apple bill you directly — these are almost never part of a build price, and they're yours to keep, in your name (which is exactly how it should be, so you own your store listings). You can confirm both on Google's Play Console and Apple's Developer Program pages.
• Your own content. Photos, product details, descriptions, prices, your logo and colours. On most projects, the build waits on the owner here far more than the owner waits on the build. Having this ready before you start is the single biggest thing you can do to keep a project fast and on budget.
• Maintenance after launch. Phones and operating systems update constantly, and a store will occasionally require a resubmission to stay compliant. A small care plan — commonly ₹500–₹2,000 a month — keeps your app working, fixes small things, and handles those re-submissions. Skipping this is how a perfectly good app quietly breaks a year later and nobody knows why.
• GST. In India, build prices are usually quoted exclusive of 18% GST. Factor it in from the start so the final invoice isn't a jolt, and make sure you get a proper GST invoice for it.

A real, itemised example

Abstract ranges only get you so far, so here's a concrete one. A home baker I worked with was quoted ₹4 lakh by an agency for a "custom ordering app." She had about 40 products and was taking orders over WhatsApp, losing track of them in the chaos.

She did not need ₹4 lakh of software. She needed a catalogue, a cart, UPI payments, order tracking, and a simple admin screen to manage it all — around seven screens. Built on a proven commerce template and themed to her brand, here's roughly how that broke down:

She was live in a week for a small fraction of the agency quote. Six months later, once she could actually see which products sold through the app and when, we added exactly one thing: scheduled delivery slots. That's the right order of operations — get live cheaply, watch real behaviour, then invest precisely where the data points. She spent on the delivery feature because the numbers told her to, not because a salesperson bundled it in on day one.

Where the money actually gets wasted

Fifteen years in, the overspending I see almost always comes from the same handful of mistakes:

• Over-scoping version one. Building the two-year dream app before proving anyone wants the six-month one. Every unused feature is money spent to learn nothing.
• Custom when a template would do. Paying to build a login, a cart or a booking flow from scratch when a proven, tested version already exists. You're paying to reinvent solved problems.
• Paying for meetings. Long discovery phases, weekly status calls, thick documents. In 2026 a blueprint takes minutes, not weeks. If a big slice of your quote is "discovery," ask what you're actually getting for it.
• Building before validating. Spending lakhs before a single real customer has tried anything. The cheapest app is the one you didn't need to build because a two-week test told you the idea needed to change.

How to read a quote so you never overpay

When a proposal lands, run it through this checklist before you react to the number:

1. Fixed price or hourly? For a well-defined small-business app, prefer a fixed price tied to a clear scope. Hourly is where budgets quietly balloon.
2. What's explicitly excluded? Store fees, content, third-party subscriptions, post-launch changes. The exclusions tell you the real total.
3. Who submits to the stores? "We build it, you figure out submission" is a red flag. Store submission is skilled work and part of shipping.
4. Do you own it? On handover you should get full ownership of the app and its backend (Firebase or otherwise), in your accounts. If you don't own it, you're renting your own business.
5. How is it tested? On real devices, with a test account for the store reviewers. "It works on my machine" is not testing.
6. What does 'done' include? Revisions, a warranty period, a care plan. Know what happens the day after launch, not just the day of.

And a specific warning about suspiciously cheap quotes: cheap-and-good comes from templates and reuse; cheap-and-broken comes from skipping testing, using someone else's developer account, and vanishing after launch. Ask the six questions above and the difference becomes obvious fast.

Android, iOS, or both? The decision that quietly moves the number

One choice affects your cost more than most owners expect: which platforms you build for. Here's the honest guidance.

Build for both from day one if you possibly can. The old assumption was that "both" meant two separate apps at roughly double the cost — one team for Android, another for iOS. In 2026 that's outdated. Modern cross-platform tools like Flutter produce a single codebase that ships to Google Play and the App Store together, so building both costs far less than two separate projects, and you never face the expensive, awkward job of "adding iOS later" as a second build.

Why both matters in India specifically: Android is where the large majority of your users will be, so if budget forces a choice, Android first is the sensible call. But iOS users, though fewer, often spend more per head and expect a polished experience — and being on both stores simply makes you look established and trustworthy. A customer who can't find you on their platform assumes you're not serious. For the small premium that cross-platform building costs today, launching on both is almost always the right call.

The trap to avoid: agencies that quote Android and iOS as two line items at near-full price each. If you see that, ask directly whether they build cross-platform. If they don't, you're paying twice for something that should cost once and a bit.

Five red flags in a cheap quote

Not every low quote is a bargain. Watch for these, which separate cheap-and-good from cheap-and-sorry:

• No test account for store reviewers. If they can't submit your app properly, it won't reach the stores.
• *The app is published under their developer account, not yours.* That means they own your store presence. Insist on your own accounts.
• No mention of testing on real devices. "It works on the emulator" is not testing.
• Vague or missing handover terms. You should get the code and the backend project, in your name, on completion.
• They disappear at launch. Ask what the day after launch looks like. Silence there is the most expensive kind of cheap.

So what should you actually spend?

Match the spend to your stage, not to your ambition.

Just testing an idea? Get live for the least money. A clean, template-based app in the ₹10,000–₹20,000 range is enough to put a real product in real hands and learn what people actually tap on. Ambition is cheap; evidence is what you're buying.

Already have customers and want to sell or book in-app? Now paying for payments, a cart or bookings, and a light admin panel is worth it — roughly ₹15,000–₹30,000. This is where an app stops being a brochure and starts earning its keep.

Running real volume and need depth? A more complete build with multiple modules and a full admin panel makes sense — a considered investment, not a starting point, and one you make once the usage justifies it.

The honest bottom line

In 2026, a real app for a small business in India is a ₹10,000–₹50,000 decision built the modern way, not a ₹5-lakh one. The technology to build it quickly and well genuinely exists now. What still matters — and always will — is scoping it tightly, having your content ready, insisting that you own the result, and working with someone who will actually get it onto both stores and keep it alive afterwards.

If you'd like to see this for your own idea, you can describe your app in plain English and get a real blueprint and live mockups in minutes — free — with a fixed price from ₹9,999 before you commit to anything. No lakhs, no six-month wait, and no quote that moves on you halfway through.