In 2026, app development in India costs roughly 3 to 8 lakh for a simple app, 8 to 25 lakh for a medium one, and 25 lakh and above for complex builds. Those are the market ranges established agencies quote, and the honest version of this guide is not the table, it is what moves you between the rows, and the costs that never appear in the first quote.
The quick-reference table
| App type | Typical range (INR) | Typical range (USD) | Timeline |
|---|---|---|---|
| Simple: a few screens, sign-in, one core feature | 3 to 8 lakh | $4,000 to $10,000 | 6 to 10 weeks |
| Medium: payments, notifications, admin panel, APIs | 8 to 25 lakh | $10,000 to $30,000 | 3 to 5 months |
| Complex: marketplace, real time, AI, scale | 25 lakh and above | $30,000 and above | 5 months and up |
Hourly rates behind these numbers run $15 to $40 for an experienced Indian agency team, against $80 to $150 in the US and Western Europe. The gap is why so much of the world's software is built here; the quality difference is decided by the team, not the geography.
If your product is a web platform on a subscription rather than a mobile app, the bands shift and the cost drivers change; that version is in our SaaS development cost guide.
What developers and agencies actually charge
The bands above are project prices. If you are comparing rates instead, which is the other half of what people search for, here is what the same work costs by engagement model.
| How you buy | Typical rate in India | What it includes |
|---|---|---|
| Freelance developer, hourly | 800 to 3,000 rupees an hour | One person's time. You supply the direction, the design and the testing |
| Freelance developer, monthly | 1 to 2.5 lakh a month | The same person, retained. Cheapest per hour and the highest key-person risk |
| Agency engineer on a dedicated team | 1.5 to 4 lakh a month per person | An engineer plus the team around them: QA, a project manager, and cover when someone is ill |
| Agency project team, blended | $15 to $40 an hour, roughly 1,300 to 3,500 rupees | Design, engineering, testing and release, priced as one project rather than per seat |
| US or Western European agency | $80 to $150 an hour | The same roles at four times the rate |
Two of those rows look like they disagree and do not. A contractor billing 1 to 2.5 lakh a month is selling you hours. An agency billing 1.5 to 4 lakh for an engineer is selling you a role that stays filled, with testing and delivery around it. Which is better value depends entirely on whether you already have someone who can direct the work and catch what is wrong with it. If you are staffing people rather than buying a project, the rate card by role, and what the same engineer costs to employ in London or New York, are in our guide to the cost of hiring developers in India.
For project pricing, the number we plan against internally is a blended 16,000 rupees per person-day, which is roughly 2,000 an hour across a mixed team. It sits inside the agency band above and it is the figure behind the estimate further down.
Cost by app type
Category tables that quote one precise number per industry are marketing. Ranges, with the reason attached, are useful. Here is where each type usually lands and why.
| App type | Usually lands at | What puts it there |
|---|---|---|
| Internal business tool | 5 to 15 lakh | One user type, no app store, no payments in many cases |
| Content or education | 8 to 14 lakh | Straightforward reading and playback; cost rises with offline and DRM |
| Booking or appointments | 8 to 18 lakh | A calendar, reminders and payments, all well-trodden |
| E-commerce | 10 to 20 lakh | Catalogue, cart, payments, orders and returns |
| On-demand or delivery | 18 to 30 lakh | Live tracking, two user types and a dispatch view |
| Two-sided marketplace | 25 lakh and up | Effectively two apps plus an admin product |
| Social | 25 lakh and up | Feeds, media handling and moderation nobody budgets for |
| Fintech or lending | 30 lakh and up | Compliance, audit trails and security review |
Two of these have guides of their own: fleet and logistics software and Shopify against a custom store.
The five things that actually move the price
- The number of user types. An app for customers is one product. An app for customers, vendors and an admin team is closer to three: three onboardings, three permission models, three sets of screens.
- Payments and compliance. Taking money means gateways, declines, refunds, invoices and taxes, and in some industries audits. It is the difference between the simple and medium rows more often than any visible feature.
- Integrations. Every external system, an ERP, a courier, WhatsApp, a bank, adds work that is invisible in the design and real in the build, plus approval timelines that run on other companies' clocks.
- Offline and real-time behaviour. An app that works without a network, or updates live like a chat, costs meaningfully more than one that loads on demand.
- Decisions not yet made. Changing direction mid-build is the most expensive feature there is. A week of discovery is the cheapest insurance on this list, which is why we fix price only after it.
Where the money goes: a worked estimate
Bands hide the arithmetic, so here is a concrete one. A customer-facing app on iOS and Android built with one codebase: sign-in, profiles, one core feature, payments, push and SMS notifications, and an admin panel for your own team. This is how we break it down after discovery.
| Work package | Person-days |
|---|---|
| Discovery: the users, the core flow, the integrations, a fixed scope | 5 |
| Design: flows, screens with their empty, loading and error states, a clickable prototype | 15 |
| Accounts: sign-in, profiles, permissions | 8 |
| The core feature, the thing you actually pictured | 20 |
| Payments: gateway, declines, refunds, invoices, reconciliation | 12 |
| Notifications: push, SMS, WhatsApp | 5 |
| Admin panel for support and operations | 9 |
| Testing on real devices, not emulators | 8 |
| Store submission and a staged rollout | 3 |
| A month of fixes after launch | 6 |
| Total | 91 |
At 16,000 rupees a person-day that is about 14.5 lakh, in the middle of the medium band. With three people, a designer front-loaded and two engineers through the build, it runs about fourteen weeks.
Two things are worth reading off that table. The feature you pictured is 20 of 91 days, a little over a fifth; payments and the admin panel together are more. And design at 15 days is 16 percent of the build, which matches the 15 to 25 percent rule in our UI/UX design cost guide. If a quote allocates almost nothing to design, it has not planned the screens that decide whether people trust the app.
The costs that are not in the quote
This is the section we wish every client had read before their first app, wherever they built it.
| Cost | Typical size | When it surprises you |
|---|---|---|
| App store fees | Apple $99/year, Google $25 once | Small, but the review cycles cost calendar time |
| Store commission on digital goods | 15% for most smaller developers, 30% at large revenue | The month your in-app purchases take off |
| Third-party services | A few thousand to a few lakh rupees a year | SMS and WhatsApp messaging, maps, analytics, hosting all meter with growth |
| Maintenance | Commonly budgeted at 15 to 25% of build cost per year | OS updates, library deprecations, the gateway changing its API |
| AI running costs | Per-request, grows with usage | Unlike ordinary features, AI features have a monthly bill |
Two of these deserve a sentence more. Store commission applies to digital goods and subscriptions bought inside the app, not to physical goods or services paid another way, which is why your grocery app pays nothing and your content app pays real percentages. And AI features split into a build cost and a running cost; we published the full arithmetic for the second in what an AI agent costs to run, because it is the line item most 2026 budgets get wrong.
Does the city change the price?
Less than the marketing suggests, and the direction surprises people. Hourly rates in Bangalore, Mumbai and Gurgaon trend 20 to 40 percent above the same seniority in Indore, Ahmedabad, Jaipur or Kochi, because the agencies there carry metro salaries and metro rent. The output gap at equal seniority is far smaller than the price gap, which is why a growing share of Indian agency work has moved to tier-two cities, ours included.
The useful comparison is never city against city; it is team against team at the same question depth. A Bangalore team that asks hard questions in discovery beats a cheap team anywhere that quotes without asking, and the reverse is equally true. Geography is a rent signal, not a quality signal.
The same logic scales internationally, which is why the $15-to-40 band exists at all: the work travels well, and the deciding variable is the team's production discipline, not its time zone. The verification checklist in our guide to hiring an AI development company applies unchanged to app work.
What maintenance actually is, since you will pay for it
The 15-to-25-percent-a-year convention in the table is not a retainer for redesigns; it is the cost of the world changing under a finished app. A typical year of "nothing happened" includes: two OS releases that each deprecate something your app touches, a payment gateway API version sunset, security patches for a handful of libraries, certificate and store-listing renewals, and the one integration partner who changes their webhook format on a Tuesday.
Skipping maintenance does not save the money; it batches it. An app untouched for two years usually needs a multi-week revival before any new feature can ship, because every dependency moved while nobody watched. Budget the percentage, or budget the revival, but budget one of them. The year itemised, with the monthly bands Indian agencies charge, is in our app maintenance cost guide.
How agencies price the work
The same app can be sold to you three ways, and the model decides who carries the risk when the scope turns out to be bigger than anyone thought.
| Model | How you are charged | Who carries the risk | Best when |
|---|---|---|---|
| Fixed price after discovery | One agreed number for an agreed scope | The agency, which is why they will insist on defining scope first | The scope is definable, which covers most first apps |
| Time and materials | Per hour or per person-day against a backlog | You | The scope genuinely cannot be pinned down, or you are rescuing an existing app |
| Dedicated team | Monthly per person | You, but predictably | The roadmap runs for a year and changes every month |
| Fixed price before discovery | One number, quoted from a brief | Nobody, and it will be recovered as change requests | Never |
The last row is the one to watch. A number quoted before anyone has asked you a hard question is not a price, it is a bid to start the conversation, and the gap gets closed later through variations. The honest version of a low quote is a smaller scope, stated plainly.
Our own model is the first: a week of discovery, then a fixed price against a fixed scope, because the discovery is what makes the number hold.
How to read an app development quote
Four checks separate a real quote from an optimistic one, and they take ten minutes.
Look for what is excluded. A quote without testing, deployment, store submission and a warranty period is not lower, it is incomplete. Ask where each of those lives.
Check the payment gateway assumption. "Payment integration" as a single line usually means the happy path. Ask whether declines, refunds and settlement reconciliation are in scope, and watch the answer.
Ask what happens to the price when scope changes. Fixed price after discovery, hourly, and dedicated team are all legitimate models with different risk. What is not legitimate is a fixed price quoted before anyone has asked you a hard question; it will be recovered later as change requests.
Ask who owns the code and the accounts. The store listings, the source repository and every third-party account should be yours from day one. Agencies that keep them are building a switching cost, not a product.
How to spend less without a worse app
- One platform first, or Flutter or React Native to cover both with one codebase; the honest saving is around a third, not half, and the reasoning is in our Flutter vs React Native comparison.
- Cut features, not quality. A five-feature app built well beats fifteen built badly, and the sequencing logic is in how long an MVP takes. If you are still deciding how small the first version should be, our MVP development cost guide prices four sizes of first version and says what each one tests.
- Reuse before you build. Authentication, chat, analytics and payments are solved problems with good services behind them.
- Start integrations' paperwork on day one. Approval delays are free when parallel and expensive when serial.
Questions people ask
What is the hourly rate for app developers in India?
Freelance developers bill roughly 800 to 3,000 rupees an hour depending on seniority and stack. Experienced agency teams price at a blended $15 to $40 an hour, about 1,300 to 3,500 rupees, which covers design, engineering, testing and release rather than one person's time. The same roles cost $80 to $150 an hour in the US and Western Europe.
How much does it cost to hire an app developer in India?
Retained individually, 1 to 2.5 lakh a month. Through an agency as part of a dedicated team, 1.5 to 4 lakh a month per person, which buys the QA, project management and cover that an individual contractor does not include. A team beats a single hire when you need design, engineering and testing at once, which most first builds do; the trade-offs are on our dedicated teams page.
Can you get an app built for 1 lakh?
Something, yes. An app worth putting your name on, almost never. At 16,000 rupees a person-day, a lakh buys about six days, which is not enough to design, build, test and release even a simple app. What a lakh does buy honestly is a clickable prototype you can show ten users, or a landing page with a payment link that tells you whether anyone wants the thing at all. Both are better uses of the money than a rushed app nobody downloads twice.
How much money can an app with 1,000 downloads make?
Downloads alone earn approximately nothing; revenue follows the model. A thousand users on a 500-rupee monthly subscription with decent retention is real money, a thousand ad-supported installs is pocket change. Decide the revenue model before the build, because it changes what you build.
Why do quotes for the same app differ by 5x?
Because they are not quoting the same app. One priced the happy path; another priced declines, refunds, admin tooling and a warranty. Send every vendor the same written scope and the spread collapses, which is itself a useful filter.
Is it cheaper to build an app with AI tools in 2026?
The build has become faster, and good agencies pass that through; it is part of why the table's ranges have held steady while apps have grown more capable. What AI tools do not remove is the expensive part: decisions, integrations, testing and the edges. Our own three-day website rebuild is an honest case study in both halves of that sentence.
Getting a real number
Ranges end where your actual scope begins. We quote a fixed price after a one-week discovery, so the number you approve is the number you pay; what that process looks like is on our mobile app development page.