You invested in building your app, it launched on the stores and it is working. Now comes the question almost nobody answers honestly at quote time: how much does it cost to maintain an app once it is live? This is the number that separates a healthy project from an app abandoned six months after launch.
Most articles repeat the same shallow line: "set aside 15% to 20% of the project value per year". That is correct, but far too generic to plan a real budget. In this guide, we at FWC Tecnologia break down every real cost component, with ranges and contract models, so you know exactly what you will spend each month keeping your software live.
In over 6 years we have built 30+ apps and web systems, in projects ranging from 30 to 120 days, and we still maintain most of them today. This is the most transparent maintenance breakdown you will find - because it comes from a team that pays these bills every month alongside its clients.
In this article
- What software maintenance is (and the 4 types)
- Why every app requires continuous maintenance
- Detailed cost components (table)
- The 15-20% per year rule and why it is simplistic
- Real monthly cost ranges by app size
- Software support contract models
- The cost of NOT maintaining your app
- How FWC handles software support
- Real cases from our portfolio
- Frequently Asked Questions
What software maintenance is
Software maintenance is everything that keeps your app working, secure and relevant after it goes live. It is not "rebuilding" the app - it is taking care of it. Software engineering classifies this work into four types, and understanding the split helps you see where each dollar of the budget goes.
Corrective maintenance
This is fixing bugs and defects that appear with real usage. A button that stops working on a specific phone model, a screen that freezes with too much data, a calculation error. These are failures that only surface when real users exercise the app in conditions no test predicted.
Adaptive maintenance
This is adapting the app to external changes you do not control. New iOS and Android versions, store policy changes, mandatory library updates, changes in third-party APIs (payment gateway, maps, social login). If you do not adapt, the app simply stops working.
Evolutionary maintenance
This is product evolution: new features, usability improvements, performance optimizations. This is the part that generates the most business value - the app grows along with your company. It is usually treated as a separate project or as an hours package inside the support contract.
Preventive maintenance
This is the silent work that avoids problems before they happen: dependency updates, refactoring fragile code, log monitoring, security reviews. It is the part clients see least and the one that saves the most money in the long run.
If you are still planning the initial investment, it helps to first understand how much it costs to develop an app in 2026 - maintenance is always proportional to that starting value.
Why every app requires continuous maintenance
There is a dangerous myth that software "gets finished". It does not. An app is a living organism that depends on dozens of external pieces that change without asking permission. Your app may be perfect today and break tomorrow without you touching a single line of code.
Apple and Google release new operating system versions every year. Each version may deprecate features, require new permissions or change interface behaviors. Apps that do not keep up start showing bugs and may eventually be removed from the stores for being outdated.
On top of that, the stores themselves change the rules often. Apple and Google publish new privacy, security and content policy requirements that force updates even on apps that changed nothing. Ignoring these requirements means having the app blocked on a future submission.
- Operating system: new iOS and Android versions every year require testing and adjustments.
- Store policies: privacy and security rules change and become mandatory.
- Dependencies and libraries: frameworks receive constant security updates.
- Third-party APIs: gateways, maps and login services change versions and deprecate endpoints.
- Security: new vulnerabilities are discovered all the time and need fixing.
Industry research is clear: according to consolidated software engineering data, maintenance consumes 55% to 80% of a software's total cost of ownership over its useful life. In other words, the initial development is usually the smaller part of the total investment.
Detailed cost components
Here is the core of this guide. Instead of a generic percentage, we break maintenance into its real components. Some are fixed costs paid to third parties (stores, infrastructure), others are hours from our engineering team. The ranges below reflect real projects in 2026.
Fixed costs paid to third parties
These are amounts that exist regardless of who maintains the app. They are paid to Apple, Google, cloud providers and external services. You pay even if not a single line of code changes in the month.
| Component | What it is | Cost range (2026) |
|---|---|---|
| Apple Developer Program | Mandatory account to publish on the App Store | US$ 99 per year (annual) |
| Google Play Console | Mandatory account to publish on the Play Store | US$ 25 (one-time fee) |
| Infrastructure / servers | Backend hosting, processing | Scales with usage |
| Database | Data storage and reads | Scales with usage |
| Push notifications | Delivery at scale (Firebase / providers) | Free to mid-range monthly |
| Maps and third-party APIs | Google Maps, geolocation | Usage-based |
| Payment gateway | Per-transaction fee (not a fixed monthly) | ~2% to 5% per transaction |
| Certificates / SSL | Connection security | Free to low annual |
Notice that infrastructure and database scale with usage. An app with 200 users pays cents of cloud cost; the same app with 200,000 active users pays thousands per month. That is why there is no "single value" for maintenance - there is your app, at your stage.
The store fees are public and official. You can confirm them directly on the Apple Developer Program enrollment page (US$ 99 annual) and on the Google Play Console help center (US$ 25, one-time registration fee).
Engineering costs (team hours)
This is the part that truly sustains the app: people taking care of the code. It includes bug fixing, OS updates, security adjustments, support and small evolutions. This is where your choice of partner makes a difference - a team that knows your code solves in hours what a new team would take days to handle.
- Bug fixing: investigating and fixing failures reported by users.
- OS updates: testing and adjusting the app for each new iOS and Android version.
- Security: applying vulnerability patches in libraries and backend.
- Technical support: answering questions, investigating incidents, following the app on the stores.
- Small evolutions: copy adjustments, simple new screens, usability improvements.
Want to know what maintenance would cost for your specific project?
Every app has a different cost profile. Request a quote with our team or get a price estimate in a few minutes.
The 15-20% per year rule and why it is simplistic
The most repeated rule in the market says: set aside 15% to 20% of the development value per year for maintenance. An app that cost the equivalent of US$ 20,000 to build would require US$ 3,000 to US$ 4,000 per year. The rule is not wrong - it is a good starting point.
The problem is that it treats all apps as equal, and they are not. A static content app has a radically different cost profile from a fintech app with a payment gateway, geolocation and thousands of daily transactions. The percentage completely ignores real usage and operational complexity.
Furthermore, the percentage does not capture the time curve. Market data shows maintenance tends to cost 10% to 25% in the first two years and can reach 20% to 40% per year in mature apps, as the software accumulates features and integrations. A fixed number hides this progression. Software cost estimation specialists even point out that most of a software's lifetime cost comes from maintenance, not from the initial development.
That is why we prefer to break the cost down by component, as we did in the previous section. The 15-20% rule works for a quick planning estimate; the component table works for planning a real budget. If you want to understand the cost logic from the start, we recommend our guide on how much it costs to develop an app.
Real monthly cost ranges by app size
To move away from the abstract, we group apps into three sizes. The ranges below add up infrastructure, fees and engineering hours into an approximate monthly value. These are real numbers from 2026 projects - not marketing table promises.
| App size | Characteristics | Estimated monthly cost |
|---|---|---|
| Simple | Content, catalog, schedule app. Little to no integration. Light backend. | Low monthly range |
| Medium | App with login, database, notifications, 1-2 integrations (payment or maps). | Mid monthly range |
| Complex | Marketplace, fintech, logistics. Multiple integrations, high volume, dense business rules. | High monthly range |
These values do not include major evolutions (new modules, full redesigns), which are treated as separate projects. They cover keeping the app live, secure and updated. If you are in the validation stage, you may not even need the full size yet - it is worth understanding how much an MVP costs and how to validate the app idea before taking on maintenance costs of a large product.
One important point: the development timeline also influences the initial maintenance cost, because apps built in a rush accumulate technical debt. To understand this relationship, see our material on how long it takes to develop an app.
Software support contract models
As important as the value is the contracting model. There are three main formats for software support contracts, each suited to a moment in the product's life. At FWC we offer all three and help the client choose what makes sense for their stage.
| Model | How it works | Ideal for |
|---|---|---|
| Fixed monthly fee | Predictable monthly value covering infrastructure, monitoring, fixes and a cap of hours. | Live apps with active users that need stability and budget predictability. |
| Hours package | Prepaid block of hours (e.g. 10h, 20h, 40h) consumed on demand, with usage reports. | Products with variable demand that want flexibility without losing support priority. |
| On demand | One-off engagement, quoted case by case, with no monthly commitment. | Mature, stable apps that only need occasional adjustments. |
Our general recommendation: apps with active users and integration dependencies benefit from the fixed monthly fee, because it guarantees someone is continuously monitoring the product. The on-demand model saves money in the short term but concentrates risk - by the time the problem appears, it has already become an incident. A WhatsApp chatbot for businesses, for instance, is a type of product that usually requires continuous monitoring because it depends on an external API that changes rules frequently.
The cost of NOT maintaining your app
Cutting maintenance looks like savings, but it is usually the most expensive decision in an app's life cycle. The cost of not maintaining does not show up on an invoice - it shows up in lost revenue, damaged reputation and emergency rework. Here is what typically happens to abandoned apps.
- The app breaks with the next OS update: users update their phones and the app stops opening. Ratings plummet.
- Removal from the stores: Apple and Google remove apps that do not meet new requirements or stay outdated for too long.
- Security vulnerabilities: outdated libraries become an entry point for data leaks - with legal risk under data protection laws.
- Broken integrations: the payment gateway changes its API and the app simply stops processing sales.
- Expensive rework: reactivating an app abandoned for a year costs far more than having maintained it - sometimes it equals a rebuild.
In short: maintenance is not an optional cost, it is insurance on the investment you already made. Paying a fixed monthly fee to keep a high-value app live is basic asset protection, not wasteful spending.
How FWC handles software support
At FWC, support is not a standalone service - it is the natural continuation of development. Whoever builds the app is who maintains it, so there is no learning curve nor knowledge handover between teams. This drastically reduces the resolution time of any incident.
Our support process includes log and availability monitoring, preventive dependency updates, testing on each new iOS and Android version, and a direct support channel. We work with a fixed monthly fee or hours package, depending on the client profile, always with a transparent report of what was done.
More than putting out fires, we act preventively. We follow Apple and Google roadmaps, anticipate store changes and warn the client before something breaks. If you are looking for an app development company that is also a long-term partner, that is exactly what we have done for over 6 years.
Real cases from our portfolio
Talking about maintenance in theory is easy. Below we show three projects from our portfolio that we keep in production, each with a different cost profile - precisely to illustrate why the support value varies so much.
Avenue - parking app
Avenue is a parking management app with a payment flow and real-time operation. This type of product requires continuous support: gateway integration, geolocation and constant availability. Any downtime directly affects the client's operation, which puts this app in the active monitoring profile.
Pato Delivery - delivery platform
Pato Delivery is a delivery platform, a classic case of a medium-to-complex app. Delivery combines payment, maps, push notifications and high volume during peak hours. Each of these integrations is a point that needs adaptive maintenance when external providers change something.
Sudati App - industrial application
Sudati App is an industrial application, with robustness and security requirements typical of a corporate environment. Industrial apps tend to have more spaced-out evolution cycles but a high reliability requirement - a profile that fits well with an hours package and a support SLA.
Three apps, three cost profiles. That is why we insist: do not rely on a single percentage. The best path is to discuss your specific case - check out similar projects when planning yours, such as our guide on how to build a marketplace with full costs and structure, which also details the continuous operation of that type of platform.
Ready to plan your app's maintenance with full transparency?
Our team designs a support plan tailored to your product's stage. Request a quote or get a price estimate right now.
Frequently Asked Questions
How much does it cost to maintain an app per month?
It depends on the size. Simple apps fall in a low monthly range, medium apps in a mid range, and complex apps in a high range. The value adds up infrastructure, store fees and the engineering hours of the team that maintains the code. There is no single number - it depends on your app's real usage.
Is the 15% to 20% per year rule correct?
It works as a quick planning estimate, but it is simplistic. It ignores real usage, integration complexity and the cost curve over time, which tends to grow in mature apps. To plan a real budget, prefer the component breakdown we detail in this guide.
What is included in app maintenance?
It includes bug fixing, updates for new iOS and Android versions, security patches, backend and database hosting, store fees, monitoring, technical support and small evolutions. Large new features are usually treated as a separate project from the support contract.
How much do the Apple and Google fees cost?
The Apple Developer Program account costs US$ 99 per year, billed annually. The Google Play Console account costs US$ 25 as a one-time registration fee, with no annual renewal. These values are official and independent of who develops or maintains the app.
Do I need to maintain the app even without adding features?
Yes. Even without changing anything, the app needs adaptive maintenance: new operating system versions, store rule changes and mandatory security updates. Apps that do not keep up with these changes start showing failures and may be removed from the stores.
What is the best support contract model?
For live apps with active users, we recommend a fixed monthly fee, which ensures continuous monitoring and budget predictability. An hours package works well for variable demand, and the on-demand model suits mature, stable apps that only need occasional adjustments.
What happens if I stop maintaining the app?
The app tends to break on the next iOS or Android update, may be removed from the stores for being outdated, and becomes vulnerable to security failures with legal risk under data protection laws. Reactivating an abandoned app usually costs far more than maintaining it continuously.
Does FWC maintain apps it did not develop?
Yes, we assess case by case. We perform a technical analysis of the existing code and infrastructure before taking over support, to understand the project's state and propose the right contract model. Request a quote and we will analyze the viability of your specific app.