The build quote is the number everyone negotiates. The maintenance bill is the one that decides whether the app is still alive in three years. Apple and Google change their rules every year, your dependencies move on, and your SaaS bills grow with your users. None of that stops because version one shipped.
Here's what app maintenance actually costs in 2026, line by line, and how to keep it down.
The rule of thumb: 15–25% a year
The most common planning figure is 15–25% of the original build cost per year for engineering maintenance. RapidNative's 2026 cost model uses that range for OS upgrades and SDK migrations, and notes year one can reach 50% as real users find the bugs testing missed. Other industry estimates run as high as 20–40% when they count ongoing improvements as well.
| Original build cost | Engineering maintenance per year (15–25%) |
|---|---|
| $30,000 | $4,500–$7,500 |
| $60,000 | $9,000–$15,000 |
| $120,000 | $18,000–$30,000 |
| $250,000 | $37,500–$62,500 |
Infrastructure is on top of that, and it doesn't scale with build cost. It scales with users.
What you're actually paying for
1. OS and SDK upgrades
This is the part founders forget, and it isn't optional.
- iOS: each fall brings a new SDK, and Apple has been requiring new submissions to use it by the following spring. iOS 27 is a good example: apps built with its SDK must adopt the UIKit scene lifecycle or they fail to launch.
- Android: Google Play raises the target API level every year. Since August 31, 2026, new apps and updates must target API 36, which enforces edge-to-edge layouts. API 37 is next.
- Framework: Expo ships several SDK releases a year (SDK 58 notes). Staying within a release or two of current keeps each upgrade small.
2. Store compliance
Store rules change outside the SDK cycle too: privacy declarations, account deletion, data safety forms, payment rules and review guideline updates. Expect a few hours each time something changes, more if an update gets rejected.
Fixed costs:
- Apple Developer Program: $99 a year
- Google Play Console: $25 one-time
- Store commission: 15–30% of in-app purchase revenue
3. Dependencies and security patches
A typical React Native app has hundreds of transitive npm dependencies. Libraries release breaking changes, get deprecated or publish security fixes. Updating regularly is cheap. Updating once every two years is a project.
4. Bugs and crashes
New OS versions, new devices like foldables and resizable iPhone windows, and new user behavior all surface bugs. Crash reporting tells you which ones matter. Budget a small, steady amount of developer time for this rather than waiting for an emergency.
5. Infrastructure and SaaS
These grow with usage, regardless of who built the app:
| Service | Typical monthly cost |
|---|---|
| Hosting | $25–$200 |
| Database | $25–$250 |
| Authentication | $25–$240 |
| Push notifications | $50–$200 |
| Analytics and crash reporting | $50–$300 |
| $30–$100 | |
| CDN and storage | $20–$100 |
| Total | $225–$1,390 a month |
That's $2,700–$16,680 a year. AI features add model API costs on top, and those scale per request.
6. Monitoring and on-call
Someone needs to notice when sign-ups stop working at 2 a.m. That can be as simple as alerts on crash rates and error spikes going to a developer on retainer, but it has to be someone's job.
A sample yearly budget
For a $60,000 React Native app with a few thousand active users:
| Item | Yearly cost |
|---|---|
| Engineering maintenance (15–25%) | $9,000–$15,000 |
| SaaS and infrastructure | $2,700–$16,680 |
| Apple Developer Program | $99 |
| Total before store commission | ~$11,800–$31,800 |
New features aren't in that number. Most teams budget them separately, as a monthly retainer or project by project.
Ways to pay for maintenance
- Monthly retainer: a fixed block of hours each month. Predictable, and the developer stays familiar with your code. Best for most live apps.
- Pay as you go: hourly when something comes up. Cheaper in quiet years, and expensive when a deadline lands and you're onboarding someone new to the codebase under pressure.
- In-house developer: makes sense once maintenance plus feature work fills most of a full-time role.
How to keep maintenance costs down
- Use one codebase. React Native serves iOS and Android from the same code, so most fixes and upgrades happen once. See our React Native vs Flutter comparison if you're still choosing.
- Stay on Expo's managed path. Continuous Native Generation regenerates the native projects on upgrade instead of making you hand-merge Xcode and Gradle changes.
- Upgrade often, in small steps. Two small upgrades a year cost far less than one forced migration every two years.
- Ship fixes over the air. EAS Update pushes JavaScript fixes in minutes without waiting for app review.
- Keep native dependencies few. Every library with native code is something that can break on the next iOS or Android release. Prefer first-party Expo modules where they exist.
- Add crash reporting and a few end-to-end tests. They turn "users say it's broken" into a specific, fast fix.
- Start from a clean foundation. Our Expo templates start you on a modern Expo setup with typed code and consistent structure, which keeps every later upgrade smaller.
The bottom line
Budget for maintenance from day one, at 15–25% of the build per year plus infrastructure, and treat yearly SDK deadlines as fixed dates on your roadmap. If you're comparing build options, include three years of maintenance in every quote. Our 3-year cost breakdown of hiring a developer vs an AI app builder does exactly that.