Most app budgets treat launch as the finish line. It is closer to the start of an ongoing commitment, because an app does not sit still on a phone: the operating system underneath it changes every year, the services it talks to retire old versions, and the two companies who control distribution both enforce rules that quietly punish apps which fall behind.
App maintenance in Dubai starts from around AED 500 a month for a simple app, or you can budget 15 to 25 percent of the original build cost each year. This guide covers what maintenance actually includes, the specific Apple and Google rules that make it non-optional, what happens if you skip it, and the running costs people forget.
We maintain apps for UAE businesses from our Dubai and Bengaluru teams [7], so this is the version of the conversation we have when a client asks why the spending did not stop at launch.
Why apps genuinely need maintenance
Apps need maintenance because Apple and Google change their platforms and their store rules every year, and both enforce requirements that break or hide apps which fall behind. This is the part worth understanding, because it is not a sales argument. It is how the two app stores work.
Apple requires new submissions to be built against a recent SDK. Apple releases a major iOS version annually and requires apps submitted or updated to use a recent SDK version, which moves each year [3]. Older interfaces get deprecated, so an app built years ago and never touched will increasingly misbehave on current devices.
Apple can remove apps that go stale. Apple runs a review process for apps that have not been updated in three years and attract very few downloads. Flagged developers get a window, currently up to 90 days, to submit an update before the app is removed from the store [4]. A single meaningful update resets that clock.
Google Play requires a recent target API level. Google requires apps to target a recent Android API level, and that required level rises annually. Apps that fall behind remain installed for existing users but stop being available to new users on newer Android devices [6]. The app is not deleted, it simply becomes invisible to anyone new, which commercially amounts to the same thing.
Add to that the third parties: payment gateways, maps, analytics, and authentication SDKs all retire old versions, and when they do, features stop working. None of this is dramatic on any given day. Over a year of neglect it compounds into an app that crashes for some users, cannot be updated easily, and is no longer discoverable.
What does app maintenance cover?
App maintenance keeps an existing app working as operating systems, store rules, and third-party services change. It does not include new features.
- OS compatibility. Testing and fixing against new iOS and Android releases.
- SDK and library updates. Keeping dependencies current, which is also security work.
- API and backend changes. When the services the app talks to change, the app has to follow.
- Security patching of the app and its backend, which matters legally too if the app holds personal data [8].
- Crash monitoring and bug fixes, so you learn about problems from data rather than reviews.
- Store compliance and resubmission when Apple or Google change requirements.
- Performance monitoring and small tweaks.
- Backend and hosting upkeep, if the app has a server side, which most do.
What it is not is new features. Those are priced separately, and conflating the two is a common cause of dispute, so agree in writing which is which.
What does mobile app maintenance cost in Dubai?
Mobile app maintenance in Dubai starts from around AED 500 a month for a simple app, or you can budget 15 to 25 percent of the original build cost each year. Two ways to budget, and they should agree with each other.
| Item | Cost |
|---|---|
| Simple app, single platform, light usage | From around AED 500 a month |
| Complex app, two platforms, live backend, integrations | Into the low thousands a month |
| Rule-of-thumb annual budget | 15 to 25 percent of the original build cost |
| Apple Developer Program | Currently 99 US dollars a year [1] |
| Google Play developer account | 25 US dollars, one-time [5] |
| Backend hosting | Usage-based, scales with traffic |
The percentage rule and the monthly figure should reconcile. Our mobile app development cost guide puts a mid-complexity build from around AED 40,000, so 15 to 25 percent of a AED 60,000 app is roughly AED 9,000 to 15,000 a year, which is about AED 750 to 1,250 a month. That is the same territory as the retainer figures above.
For comparison, our website maintenance guide starts from around AED 150 a month. Apps cost more for concrete reasons: potentially two codebases, mandatory store review to ship anything at all, annual platform requirements enforced by Apple and Google, and usually a live backend. Final pricing depends on the app and is confirmed after a short review. Services carry the standard 5 percent VAT [9].
Retainer, hourly, or annual contract: which model fits?
Most app maintenance in the UAE is sold one of three ways, and the difference matters more than the headline price. A monthly retainer buys attention. Hourly work buys reactions. An annual maintenance contract is usually the same retainer with different billing.
The monthly retainer. A fixed fee, from around AED 500 a month at the simple end, covering the compatibility, patching, monitoring, and bug-fix work listed above. This is the model that fits any app with real users, because most of the work is proactive. Nobody tells you in advance that a dependency is about to be retired or that the target API level has moved. Somebody has to be watching.
Hourly or pay-as-you-go. Cheaper on paper and genuinely fine for an internal tool used by a handful of staff. The problem for a customer-facing app is that between calls, nobody is reading the crash reports and nobody is tracking the annual Apple and Google requirement cycle. So problems do not arrive as maintenance. They arrive as emergencies, usually at the worst moment, and emergency work costs more per hour and takes longer because the backlog has piled up.
The annual maintenance contract. Often written as AMC in this market, and it is worth saying plainly that an AMC and a retainer are the same service. The difference is that you commit for a year, usually for a slightly better rate and a clearer scope. If a proposal uses one word and your last one used the other, you are comparing the same thing.
How to compare two quotes. Price alone tells you very little. The question that moves the real cost most is whether store resubmission and dependency updates sit inside the fee or get billed on top, because that answer alone can double a cheap-looking retainer. The rest of what to pin down is in the agreement checklist further down this page.
Which model for which app. Retainer for anything with real users, hourly only for a low-stakes internal tool. Whichever you are quoted, sanity-check it against the 15 to 25 percent of build cost a year rule, and if a quote comes in far below that, look closely at what has been left out.
The costs people forget
Beyond the retainer, three costs catch people out: the platform fees, the backend, and monitoring.
The platform fees. Small but mandatory. The Apple Developer Program renews annually, and if the membership lapses your apps stop being available on the store [1], which is an entirely avoidable outage. Put the renewal on a calendar.
The backend. It is common to budget for the app and forget the server it talks to. Hosting is usage-based, so it scales with your success, and the surprises usually come from architectures that move a lot of data rather than from user numbers alone. Our cloud migration guide covers the cost drivers.
Crash monitoring. Usually free or cheap, and the highest-value monitoring you can add. Without it you find out about crashes from your rating.
Who should own the accounts?
Your own legal entity, on both stores. Apple requires organisations to enrol with a D-U-N-S number registered to the legal entity [2], so the account genuinely belongs to a company, and the question is only which company.
If your developer's entity holds it, your app is published under their name. Should that relationship end badly, you can lose the ability to update, price, or remove your own app, and you lose its accumulated reviews and ranking if you have to republish. The same goes for the code repository: it should be in your name with the developer given access. This costs nothing to set up correctly at the start and is close to unrecoverable later. Our guide to choosing an app development company covers the wider ownership checklist.
What should be in a maintenance agreement?
Get these in writing before you sign:
- What is covered: compatibility, patching, bug fixes, store submissions.
- Response times, with critical issues distinguished from minor ones.
- How much is included, as hours or releases per month.
- What counts as a new feature, and how those are quoted.
- Who holds the developer accounts and the repository. You.
- Reporting, monthly or quarterly, on what was actually done.
A retainer with no reporting and no defined scope is where money leaks, because neither side can point to what was promised.
Real client stories
These are real situations from apps we have taken over.
The app that stopped working on new phones. A client's app had not been updated in over two years and had started crashing on launch for users on the latest iOS. The build was against an SDK several versions behind and two of its SDKs had been retired by their providers. Bringing it back to a shippable state took far longer than two years of steady maintenance would have. Nothing had gone wrong dramatically; it had simply been left.
The renewal nobody owned. A business discovered their app had vanished from the App Store. The Apple Developer Program membership had lapsed because the renewal email went to a former employee's address. The app was restored, but it was down for days during a campaign they had already paid to promote. The fix was a calendar reminder and an account in the company's own name.
The invisible Android app. A client could not understand why Android installs had dried up while iOS was steady. Their app had fallen behind Google Play's target API level requirement, so it was still working for existing users but was no longer being offered to new ones on current devices. Existing users had masked the problem for months. One compatibility update restored distribution.
Taking over an app from a previous developer
Yes, a new provider can maintain an app they did not build, and it is one of the most common ways a maintenance engagement starts. The question is not whether it is possible, it is what the handover needs and what the first month looks like.
What you need to hand over. Access to the code repository, including its history. The Apple and Google developer accounts, which should already be in your company's name for the reasons above. Backend and hosting credentials, plus any database access. Third-party service accounts: payment gateway, maps, analytics, push notifications. Whatever documentation exists, even if it is thin.
When some of that is missing. It happens often, and most of it is recoverable. Store accounts can be transferred or, at worst, the app republished under your own account, though republishing loses the existing reviews and ranking, which is a real cost. Hosting and service accounts can usually be recreated. The one genuinely serious gap is the source code. If nobody has it, the app cannot be updated at all, only rebuilt. That is worth checking today rather than on the day you need a fix.
The takeover review. Before quoting a retainer, a new maintainer should check three things. Does the app still build at all on current tooling. How far has it drifted from the current SDK and target API level requirements. Which of its dependencies are retired, unsupported, or carrying known vulnerabilities. That review is short, and it is what turns a guess into a number.
Catch-up work is priced separately. This is the part people are surprised by, and it is not a trick. An app left alone for two or three years usually needs a one-time compatibility project before steady maintenance makes any sense. You cannot maintain something that does not currently build. So it gets scoped and quoted on its own, then the retainer starts afterwards. The catch-up is almost always more expensive than the years of steady upkeep would have been, which is the whole argument for the retainer.
When retiring the app is the better answer. Sometimes the honest advice is not to revive it. If the app has few active users, no clear commercial job, and the catch-up cost is significant, a deliberate retirement beats paying to bring back something nobody needed. We would rather say that early than bill for it.
How SKIMBOX handles app maintenance
We keep apps current against Apple and Google's annual requirements rather than waiting for something to break, set up crash monitoring from day one so problems surface as data rather than reviews, patch dependencies as security work rather than optional housekeeping, and report monthly on what was actually done. We insist your business holds the developer accounts and the code repository, and we separate maintenance from new features in writing so nobody argues about it later.
Maintenance starts from around AED 500 a month for a simple app, or budget 15 to 25 percent of the original build cost a year.
See our app development services and product engineering services, or contact us for a review of your app's current state.
For related reading, see our guides on mobile app development cost in Dubai, website maintenance and AMC packages, and choosing an app development company in Dubai.
References
[1] Apple Developer - Apple Developer Program enrollment and annual fee. developer.apple.com/programs/enroll/
[2] Apple Developer - D-U-N-S Number requirement for organisation enrollment. developer.apple.com/help/account/membership/D-U-N-S
[3] Apple Developer - Upcoming SDK requirements for app submissions. developer.apple.com/news/upcoming-requirements/
[4] Apple Developer - App Store Improvements process for apps not recently updated. developer.apple.com/support/app-store-improvements/
[5] Google Play Console Help - Developer account registration fee. support.google.com/googleplay/android-developer/answer/6112435
[6] Google Play Console Help - Target API level requirements for Google Play apps. support.google.com/googleplay/android-developer/answer/11926878
[7] SKIMBOX - Internal experience maintaining apps for UAE businesses, 2026. skimbox.co
[8] U.AE Official UAE Government Portal - Data protection laws, Federal Decree-Law No. 45 of 2021. u.ae/en/about-the-uae/digital-uae/data/data-protection-laws
[9] Federal Tax Authority, UAE - Value Added Tax. tax.gov.ae/en/taxes/vat.aspx
