What App Maintenance Covers, and What Happens to an App Without It

Codixus Team14/11/2026
What App Maintenance Covers, and What Happens to an App Without It

Launch day feels like the end of the project. The app is approved, people download it, and the team moves on. For a while nothing happens, and that quiet is misleading. A live app sits on two platforms that keep changing, and it does not change with them unless someone does the work.


An unmaintained app rarely fails on a dramatic day. It fails on the day you need a release: a price change before a campaign, a fix for a login that a provider changed, a new legal text. That is when you learn how far the project has drifted. This post first lists what drifts, with the dates the stores have published, and then what a maintenance routine is made of.


What happens to an app nobody maintains


It loses new users on Android


Google Play ties availability to the Android level an app targets. Since August 31, 2026, an existing app has to target at least Android 15, API level 35, to stay available to new users on devices that run a newer Android version than the app targets. Below that, new users only find it on devices that run an Android version at or below the level it targets, while people who already installed it keep it. New phones are exactly where new users stop finding it.


Its next update stops being a small job


An update has to meet today's bar, not the bar of the last release. On Google Play an update must target API level 36. On the App Store an upload must be built with Xcode 26 or later since April 28, 2026. And from February 1, 2027, Google Play will not accept updates that do not support 16 KB memory pages from apps targeting Android 15 or higher. A project that skipped a year has to catch up on all of that before a one-line fix can ship. We describe that catch-up in getting an outdated Expo app back on the stores.


Apple may ask you to update or leave


Apple runs a standing process it calls App Store Improvements. Developers whose apps have not been updated within the last three years and fail a minimal download threshold get a notice, and then 90 days to submit an update before the app is removed from the store. Apps that crash on launch are removed immediately.


Accounts and certificates expire quietly


If the Apple Developer Program membership lapses, the apps are no longer available for download. If the push notification certificate expires, Apple's wording is short: you can no longer send push notifications to your app. Neither of these announces itself inside the app. Someone has to own the renewal dates.


What a maintenance routine is made of


Maintenance is not a retainer for unknown work. It is a short list of recurring jobs, and each one prevents one of the failures above.


A release on a schedule


The most useful habit is to ship a release regularly even when there is little to ship. A release exercises the whole chain: the build tools, the signing certificates, the store forms, the review. A chain that ran last month runs this month. A chain that last ran a year and a half ago is where the surprises are.


Staying close to the current SDK


For several years Expo shipped three major SDK versions a year, and in 2026 its team said it is exploring a faster cadence that follows React Native's releases. Its upgrade guide recommends moving one version at a time. Put those together and the arithmetic is simple: one version behind is a small, routine upgrade, and five versions behind is five upgrades in a row. We explain how the versions, builds and over-the-air updates fit together in our guide to production apps with Expo.


A store calendar


Both stores publish their deadlines in advance. Apple keeps a page of upcoming requirements, and Google documents the target API level dates. The work is to write those dates into a calendar when they are announced and to make the change in a normal release, well before the deadline, when nothing is urgent.


A weekly look at crashes


New phone models and new operating system versions arrive whether you release or not, and a screen that worked can start crashing on them. A weekly look at the crash reports, and a fix for the most frequent crash, keeps that from building up. Remember that Apple removes apps that crash on launch without the 90-day window.


Privacy forms that still match the app


Every package you add or update can change what the app collects. Apple requires the app privacy details for updates as well as new apps, and they cover third-party code. Google's Data safety form asks which data types the app collects and shares. Both are declarations in your name, so they should be re-read whenever the package list changes.


A written record


The last piece is a short monthly note: which version is live, the crash rate, the review rating, which store deadlines are coming. It takes one page. Its value shows a year later, when someone new has to understand the app's history in ten minutes.


What maintenance is not


It helps to draw the line, because the word gets stretched. These are different jobs with different budgets.


  • Large new features and redesigns
  • Rewriting the backend
  • Running ads and ad budgets
  • Round-the-clock on-call duty
  • Fees charged by Apple, Google and third-party services

Doing it yourself


None of this needs an outside company. It needs an owner and a calendar. If you have a developer on the team, the routine is a small one as long as it is actually done every month:


  • Ship one release a month on both stores
  • Stay at most one major SDK version behind the current one
  • Keep the store deadlines and the renewal dates in one calendar
  • Read the crash reports every week
  • Re-read the privacy forms when the package list changes

Where this breaks down is ownership. The developer who built the app leaves, or the agency moves on to its next client, and the routine stops without anyone deciding to stop it.


FAQ


How often does a live app need an update?


No store rule sets a monthly schedule. The limits the stores publish are slower: Google Play's target API level requirement, and Apple's review of apps that have not been updated in three years and have very few downloads. In practice the question is how long a build chain can sit unused before it stops working, and a monthly release keeps you from finding that out the hard way.


What does skipping maintenance for a year cost?


It turns the next small change into an upgrade. Expo shipped three major SDK versions a year for several years and four in 2026 (SDK 55 to 58), so an Expo app left alone for the past year is about four major versions behind. Expo recommends upgrading one version at a time. The store requirements for the target API level and for Xcode may also have moved in that year.


Is app maintenance the same as hosting or support?


No. Hosting keeps your servers running and support answers your users. Maintenance keeps the app itself releasable: current build tools, valid certificates, store forms that match the app, and a release that goes out on a schedule.


Does maintenance guarantee that the app stays on the stores?


No. Apple and Google decide what stays on their stores, and their rules change. Maintenance removes the known reasons an app falls behind or gets rejected, and it means a rule change is handled in a normal release instead of an emergency.


If you want someone to own the routine


We offer this as app maintenance for Expo and React Native apps: monthly plans for app owners, built around a release every month on both stores, store compliance tracked on a calendar, a weekly crash check and a one-page monthly report. The code and the accounts stay yours, and every submission goes out with your written approval. A plan runs for at least three months, then continues month to month and ends with 30 days' notice.


Sources



We do not take on a monthly commitment before we know the code, so a plan starts after a Health Check or a Store-Ready Sprint. To start, send us the name of your app and its store link and mention app maintenance. We answer in writing whether the app fits a monthly plan.

EXPLORE MORE

Looking for more insights? Check out our other blog posts and resources.

Message us on WhatsApp