What is included in app maintenance cost in India?
App maintenance cost in India covers everything you pay after launch to keep the app installable, working and accepted by Google Play and the App Store. It splits cleanly into two budgets: people (developer hours) and platforms (servers, services and store accounts).
The people budget pays for compliance updates, library upgrades, crash fixes, small changes, security patches and releases. The platform budget pays for your hosting or Firebase usage, SMS for OTP, maps or other paid APIs, email delivery, domain and SSL, and the Apple Developer Program renewal. The first budget is what a developer quotes; the second is what your cloud and service providers bill, and it grows with users rather than with features.
Most confusion about app maintenance cost in India comes from quotes that mix the two. A developer might say “maintenance included” and mean only bug fixes, leaving you to discover later that the server bill, the Play target-API rebuild and the iOS SDK update were never part of it. Another quote might bundle hosting inside a monthly fee, so you cannot tell how much is labour and how much is infrastructure.
We keep them apart on purpose. Running costs go to accounts you own, so the invoices come to you directly. Our maintenance plan, from ₹8,000/mo after 2 free months, is only the labour, with a written list of what it includes.
- People: platform updates, SDK upgrades, crash fixes, minor changes, security, release management.
- Platforms: server or Firebase, database, OTP SMS, maps, email, domain and SSL, Apple renewal.
- Occasional: new features, redesigns and integrations, quoted separately like a mini project.
Does the 15–20% of build cost rule work for app maintenance cost in India?
The rule that yearly maintenance costs 15–20% of the original build is a reasonable sanity check, but it is a rough average, not a price. Use it to spot a quote that is wildly off, then build your real budget line by line.
The rule works best for a mid-sized app with a normal backend and a steady but modest feature roadmap. It breaks down at both ends. A simple catalogue or booking app with few integrations may need much less labour in a year, because only the platform updates and the occasional crash fix are unavoidable. A delivery, fintech or marketplace app with payment SDKs, live tracking, several user roles and weekly change requests can easily need more, because each integration adds its own update cycle.
The rule also ignores running costs completely. An app with heavy image uploads or real-time chat can have a server bill larger than the labour, while a lightweight app on Firebase’s Spark plan may pay almost nothing to Google.
So when you plan app maintenance cost in India, take your own build invoice, apply 15% and 20% to it, and hold those two figures aside. Then estimate each line in the table further down this page. If your line-by-line total lands inside the band, good. If it lands far above, you probably have a heavy backend or many SDKs. Far below, and someone has likely left out the yearly platform updates.
Why does an Android app need an update every year on Google Play?
Because Google Play raises its target API level requirement every year, and an app that falls behind cannot publish updates and eventually disappears for users on newer phones. This one rule guarantees at least one paid update per year, whatever else changes.
According to Google’s Android developer documentation, from 31 August 2026 new apps and app updates must target Android 16 (API level 36). Existing apps must target at least Android 15 (API level 35) to remain available to new users on devices running newer Android versions than the app targets. Google offers an extension to 1 November 2026 for developers who request it through Play Console.
Raising the target level is rarely just a number change. Each Android version tightens rules on background work, notifications, photo and media permissions, exact alarms and edge-to-edge layouts. The developer has to update the build tools, upgrade libraries that are not yet compatible, fix the screens that break, and test on a range of devices. For a Flutter or React Native app, the framework itself usually needs upgrading first.
This is the single most forgotten line in app maintenance cost in India. Businesses that paid for a build and nothing else often find out in September, when their developer has moved on and Play Console refuses the next upload. If that has already happened to you, our page on an app rejected by Google Play walks through the recovery.
What does Apple require before you can ship an iOS update?
Apple requires every upload to App Store Connect to be built with a recent Xcode and SDK, so an iOS app also needs a yearly rebuild even if nothing in it has changed. Miss the window and your next bug fix simply cannot be submitted.
Apple’s developer news page states that from 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK (or the matching iPadOS, tvOS, visionOS or watchOS SDK). From 9 September 2026, iOS and iPadOS apps must also target iOS 13 or later. Apple typically announces the next Xcode requirement months ahead, and it tends to bite each spring.
A new Xcode brings new compiler warnings, deprecated APIs and sometimes layout changes on the latest iPhones. Cross-platform apps need their Flutter or React Native version and every native plugin to support the new toolchain before the build even succeeds. Then comes review: Apple checks the privacy manifest, the account deletion option if you offer sign-up, and whether the screenshots still match the app.
Two more iOS lines belong in your budget. The Apple Developer Program costs US$99 a year, and if it lapses your app is removed from sale until it is renewed. And a Mac with current Xcode is needed for every build, which is one reason businesses keep an iOS developer on a maintenance plan rather than calling someone new each year.
Server, Firebase and API bills: the running side of app maintenance cost in India
Running costs are what your app spends on infrastructure every month, and they scale with users and data, not with developer effort. They are often the fastest-growing part of app maintenance cost in India once an app catches on.
Firebase is a common backend for small apps. Google’s Firebase pricing page lists two plans: Spark, a no-cost plan with usage limits and no card required, and Blaze, pay as you go. Several Firebase products, including Crashlytics, Cloud Messaging for push notifications, Google Analytics and Performance Monitoring, are listed as no-cost on both plans. What you pay for on Blaze is mainly database reads and writes, storage, bandwidth and cloud functions.
Apps on their own server, for example a Node.js or Laravel API on AWS or a VPS, pay for the machine, the database, backups and bandwidth. Then come the third-party meters: OTP SMS for login, Google Maps calls for address pickers and tracking, transactional email, WhatsApp notifications, image or video storage, and any AI features that call a model per request.
Three habits keep this line of app maintenance cost in India under control. Set budget alerts in your cloud console so a runaway query cannot quietly run up a bill. Review which calls happen on every screen open, because a map or a database listener loaded unnecessarily can cost more than the rest of the app together. And keep every account in your own name and card, so you see the bill as it grows. We set these up during the Firebase build and check them as part of maintenance.
How much of app maintenance cost in India goes on crash and bug fixing?
In a stable app, fixing crashes is a small, steady slice of the yearly budget; in a neglected one it becomes the biggest line, because every unfixed crash drags ratings down and every bad rating costs installs.
Crash work has three steps. First, visibility: Firebase Crashlytics (no-cost) and Android vitals in Play Console show which devices, Android versions and app versions are crashing or freezing (ANRs). Second, triage: a crash affecting a popular budget phone model matters far more than one on an old tablet. Third, the fix and a staged rollout, so a bad fix reaches a small share of users first.
Google Play also uses vitals when deciding how prominently to show apps, and an app with high crash or ANR rates can be shown less or carry a warning on its store listing. So crash fixing is not only about happiness; it protects the installs you paid marketing money to earn.
On our plans, crash review is scheduled, not left to whoever notices. We look at the dashboards, list the top issues on WhatsApp with a plain-language note on who they affect, and fix them inside the plan when they are genuine bugs. If a “crash” turns out to be a feature request in disguise, for instance a flow that never supported a certain phone size, we quote it separately so you can decide.
Store accounts, renewals and the small recurring fees
The store fees are the smallest part of app maintenance cost in India, but losing an account is the most expensive mistake, so treat these lines carefully.
Google Play charges a one-time US$25 registration fee for a developer account, with no yearly renewal. Apple charges US$99 a year for the Apple Developer Program. Organisations need a D-U-N-S number to enrol with Apple as a business, and Google now asks developer accounts for identity and, for organisations, business verification, so keep your registration documents handy.
The recurring risks hide around these accounts rather than in the fees. If the account was opened in the developer’s name, you cannot update the app when that person disappears; transferring an app between Play accounts is possible but slow. If the Apple renewal card expires, your app leaves the App Store until you pay. If Play’s policy emails go to a developer’s inbox you never see, a warning can turn into a suspension without you knowing. Our guide to a suspended Google Play app covers that route in detail.
We ask every client to open both store accounts in their own business name and add us as users with limited roles. It costs nothing extra, and it means maintenance can change hands without drama.
Monthly retainer or hourly fixes: which lowers app maintenance cost in India?
A monthly retainer is cheaper for apps that change often or earn money daily; per-task fixes are cheaper for simple apps that rarely change. The deciding factor is how costly a week of downtime would be for you.
With a retainer, you pay a predictable monthly amount and the developer keeps the app’s context in their head: which SDK is due for an upgrade, which screen is fragile, how the backend is wired. Platform deadlines get planned. Small changes get done without a new negotiation each time. The cost is paying in months when nothing happens.
With per-task fixes, you pay only when something breaks or you need a change. That works when the app is small, you have few users and the business can live with a slow response. The hidden cost is ramp-up: each time, the developer has to re-learn the code, and the yearly Android and iOS updates often become rushed jobs close to the deadline.
- Choose a retainer when the app takes payments or bookings, has more than one user role, or depends on three or more third-party SDKs.
- Choose per-task quotes when the app is internal, informational or rarely updated, and a slow fix would not lose you money.
- Mix both by keeping a retainer for platform updates and monitoring, and quoting larger features separately.
Our maintenance plans start from ₹8,000/mo after the 2 free months; one-off fixes are quoted before any work starts, and terms sit in your written quote alongside our terms of service.
How to estimate the app maintenance cost in India for your own app
Estimate from the bottom up: count platforms, integrations and change requests, then add running costs from your actual cloud bills. It takes about an hour and gives a far better figure than any percentage.
Work through these steps with your app open on one side and your bills on the other.
- Count platforms. Android only, iOS only, or both. Each adds its own yearly compliance update and store review.
- List every SDK. Payments, maps, login, analytics, push, chat, video. Each one deprecates versions on its own schedule.
- Check the backend. Firebase, your own API, or both; and whether there is an admin panel that also needs updates.
- Estimate change requests. How many small changes did you ask for in the last three months? Multiply for the year.
- Pull running costs. Take three months of cloud, SMS, maps and email invoices; average them; allow for growth.
- Add fixed fees. Apple’s US$99 renewal, domain and SSL if paid separately.
- Add a buffer. One unplanned issue a year, such as a policy change or an SDK shutting down, is normal.
Send us that list on WhatsApp and we return an itemised maintenance quote in about two working days. If you are still choosing a stack, our Flutter app cost guide explains how framework choice affects upkeep.
Which technical choices make an app cheaper to maintain?
Fewer dependencies, one shared codebase and a well-documented backend make an app cheaper to maintain; many plugins, abandoned libraries and a backend only one person understands make it expensive.
Cross-platform frameworks such as Flutter and React Native let one codebase serve Android and iOS, so most fixes are made once. The trade-off is that the framework itself must be upgraded regularly, and plugins that wrap native code sometimes lag behind new Android and iOS versions. Picking plugins with active maintainers at build time saves real money later. Our pages on React Native app cost and native vs hybrid apps go deeper on that trade-off.
On the backend, managed services like Firebase remove server patching but tie you to their pricing model. A small API on your own cloud gives more control and predictable costs at scale but needs operating system and runtime updates. Either way, a README that explains how to deploy, where the secrets live and how to restore a backup is worth more than any clever architecture.
Automated tests on the risky flows, such as login, checkout and booking, cut the time each upgrade takes, because the developer is not clicking through every screen by hand. And a CI pipeline that builds both platforms from the repository means anyone you hire later can ship a release without first rebuilding your whole setup.
India-specific factors that push app upkeep up or down
Indian apps carry a few maintenance lines that global guides skip: a very wide range of budget Android phones, UPI payment flows, SMS OTP delivery and, often, Hindi or regional-language content.
Device range matters most for app maintenance cost in India. Your users may be on phones with limited RAM, older Android versions and aggressive battery savers from different manufacturers that kill background tasks. Each Android upgrade can change behaviour on some of these phones and not others, so testing on a few popular budget models is part of real maintenance, not a luxury.
Payment flows need attention whenever the payment provider changes its SDK or UPI intent handling, and when NPCI or your bank updates rules on mandates and refunds. Login by SMS OTP depends on DLT-registered templates with your telecom operator, and a template rejection can stop logins overnight. If your app sends WhatsApp alerts, Meta’s template rules and pricing also move; our WhatsApp chatbot price guide explains that meter.
Language adds content upkeep: every new screen needs its Hindi or regional strings, and missing translations show up as English fallbacks that look broken to users. Finally, India’s Digital Personal Data Protection Act, 2023 makes it sensible to review what personal data the app collects and how users can ask for deletion; we build those controls, and your own adviser confirms the legal side.
Who should own the code, keys and accounts during maintenance?
You should. The business that pays for the app should hold the source code repository, the store accounts, the cloud accounts and the signing keys, with developers added as users who can be removed.
The Android signing key deserves special mention. With Play App Signing, Google holds the app signing key and your team holds an upload key; if the upload key is lost, you can ask Google to reset it. Older apps not enrolled in Play App Signing depend entirely on a keystore file, and losing it means you can never update that listing again. Checking where the keystore lives is one of the first things we do when taking over an app.
For iOS, certificates and provisioning profiles live in your Apple Developer account, so as long as you own the account, any developer you add can generate new ones. Push notification keys, Firebase service accounts and third-party API keys should all sit in your accounts too.
At the start of any maintenance plan we share a simple access register: every account, who owns it, who has access and when that access was last reviewed. If you ever move on, the handover is a list to walk through, not a treasure hunt. If a previous developer has vanished with some of these, read what to do when a developer leaves midway.
Red flags in an app maintenance quote
The biggest red flag is a quote that does not mention Google Play’s target API update or Apple’s Xcode requirement, because those two are the only jobs guaranteed to happen every year.
Watch for these as well when comparing quotes for app maintenance cost in India. Different developers price app maintenance cost in India very differently, and quotes vary widely; the useful question is what each one actually includes.
- “Unlimited changes” with no definition of a change. It usually ends in arguments about what counts.
- Hosting bundled into the fee with no separate figure, so you cannot compare or move providers.
- Store or cloud accounts in the developer’s name, which makes leaving them expensive.
- No mention of monitoring: if nobody reviews crash reports, bugs are found by your customers.
- A year paid upfront with no written list of what the year includes.
- No response channel for urgent problems, or one that only works on weekdays.
- Vague exclusions such as “major changes excluded” without examples.
If you want a structured way to interview developers before signing, our list of questions to ask an app developer works just as well for maintenance as for a new build.
What happens if you stop maintaining an app?
Nothing, for a few months; then the app slowly stops being installable for new users, updates are blocked by the stores, and the next fix becomes a small rebuild. Skipping maintenance does not save the money, it postpones and enlarges the bill.
On Android, once your target API falls below Google Play’s floor for existing apps, users on newer Android versions stop seeing your app in search. Because most new phones sold ship with recent Android versions, your pool of possible new users shrinks every month. On iOS, the app keeps working for current users for a while, but any change, even a one-line fix, now needs the latest Xcode, every plugin updated and a fresh review.
Meanwhile SDKs expire. Payment providers retire old API versions, login providers change requirements, map and push services deprecate endpoints. Each one on its own is a small fix; five of them discovered at once, in an app nobody has touched for two years, can approach the effort of the original build.
If budget is tight, the minimum sensible plan is one planned update window per platform per year, crash monitoring left switched on, and all accounts in your name. That keeps the app shippable while you decide what comes next.
Store ranking, reviews and search visibility after launch
Maintenance also keeps your app findable: regular updates, low crash rates and answered reviews all feed into how the Play Store and App Store present your listing, and how people discover you on Google and AI assistants.
Store listings need the same care as a website. Keywords in the title and short description, current screenshots, answered reviews and honest release notes help both ranking and conversion. Our page on how to rank an app on the Play Store covers the store side in depth.
Outside the stores, many users search on Google or ask an AI assistant for “an app for X in my city”. A simple website or landing page for the app, with clear descriptions, an FAQ and structured data, gives search engines and AI tools a page they can read and cite, which a store listing alone rarely achieves. We can build that page from ₹10,000 and keep it updated alongside the app.
Performance matters on both sides. A bloated app with a large download size gets fewer installs on budget phones and limited data plans, so trimming unused libraries and compressing images during maintenance also improves your install rate.
Worked example: estimating app maintenance cost in India for a coaching app
Here is a hypothetical case to show the method, not a real client. Say a coaching institute in Indore has a Flutter app on Android and iOS: students log in with OTP, watch recorded lectures, take tests and pay fees by UPI. There is a small admin panel for teachers.
Counting platforms gives two, so two yearly compliance updates: the Play target-API change before August and the Xcode rebuild each spring. The SDK list includes the payment SDK, a video player, Firebase Auth, Crashlytics and Cloud Messaging, so roughly five to watch. Change requests over the last quarter averaged two small ones a month, such as a new batch timetable screen and a test result format.
Running costs come from video storage and bandwidth, which will be the largest line once students watch in bulk before exams; OTP SMS on login; and a modest Firestore bill. The institute would pull three months of these invoices to average them and would set a budget alert for exam months.
On that profile, a maintenance plan from ₹8,000/mo after the 2 free months covers the compliance updates, SDK upgrades, crash review and the two monthly changes. A new live-class module would be quoted separately. The institute keeps the Play and Apple accounts, the Firebase project and the video storage bill in its own name. For a similar, larger build, see education app development cost.
App maintenance across India
Maintenance is fully remote, so the app maintenance cost in India is the same whether your business sits in a metro or a smaller city. We work over WhatsApp, video calls and shared dashboards, in English or Hindi, and every account stays with you.
The same remote setup serves app owners in Bengaluru, Pune, Indore, Jaipur, Kochi, Lucknow, Surat, Coimbatore, Guwahati and Chandigarh. The kinds of apps differ by city: ordering and dealer apps in trading hubs, coaching and exam-prep apps in education centres, booking apps in tourist towns. The maintenance jobs underneath are the same everywhere.
Payments are by UPI or bank transfer, invoiced from India; international app owners pay in USD by Wise, bank wire or PayPal, from US$120/mo for a plan. Before any money moves, you get the itemised quote in writing.