App Maintenance After Launch: OS Updates, SDKs, Certificates, Budget
Short answer
A published app needs regular maintenance even when no features change. Apple and Google ship new OS versions every year, raise minimum SDK and target API requirements and update store policies, while certificates, keys and memberships expire. A recurring maintenance budget and a fixed calendar let you ship updates before deadlines instead of after an app is hidden or an upload is blocked.
Why apps decay without any code changes
An app that worked perfectly at launch can break a year later without anyone touching it. New OS versions change permission dialogs, background execution limits and UI behavior. Third-party SDKs drop support for old versions. The stores tighten requirements for every new upload, so even an urgent bug fix can be blocked because the toolchain is outdated. Maintenance is the work that keeps the app shippable at any moment.
The yearly cycle
| Event | What it means for you |
|---|---|
| Apple's major iOS release (previewed at WWDC, released in autumn) | Test on the betas over the summer, fix layout, permission and deprecation issues before users update. |
| Apple's minimum SDK requirement | Some months after a major release, uploads must be built with a recent Xcode and SDK. Old projects need a toolchain upgrade first. |
| Android's major release | Most behavior changes apply once your app targets the new API level, so test against it early. |
| Google Play target API level | Google raises the required target API level every year. Updates must meet it, and apps that fall too far behind may no longer be offered to new users on newer devices. |
| Store policy updates | Apple revises its guidelines regularly, Google announces policy changes with grace periods. Both can require changes to listings, privacy declarations or features. |
Things that expire
- Apple Developer Program membership: renews annually. If it lapses, your apps are removed from sale.
- Apple certificates and provisioning profiles: distribution certificates and profiles expire. Live apps keep working, but you cannot sign new builds until you renew. See our guide to iOS code signing.
- Push notification credentials: certificate-based APNs authentication expires yearly. Token-based authentication keys do not, which is why most teams switch to them.
- Android upload key: with Play App Signing, Google holds the app signing key and a lost upload key can be reset – but keep the keystore and passwords backed up anyway.
- Agreements: updated developer agreements in App Store Connect or Play Console must be accepted before new uploads go through.
- Everything around the app: domains, TLS certificates, API keys and backend services the app depends on.
SDK and dependency updates
Treat third-party SDKs as part of the app's lifecycle. Google deprecates older Play Billing Library versions on a schedule, Apple requires privacy manifests for commonly used SDKs, and frameworks like Flutter or React Native need periodic upgrades that are easier in small steps than in one big jump. Each change can also affect your App Store privacy labels and the Google Play data safety form, which must stay accurate.
A practical rhythm: check dependencies and security advisories monthly, run the full build in CI at least once a month even without releases, and keep crash monitoring active so OS-specific problems show up early.
Planning the budget
- Fixed costs: store memberships, CI minutes, monitoring and other tooling.
- Planned yearly work: the iOS adaptation window and the Android target API update. Reserve capacity before autumn, when demand for developers is highest.
- Continuous work: dependency and security updates, small fixes, store policy follow-ups.
- Reserve: for rejections, sudden policy changes or a framework upgrade that turns out larger than expected.
Name one person who owns the calendar of expiry dates. And if an app is no longer worth maintaining, retire it deliberately instead of letting it decay in the store.
How jocapps helps
apprat.io fits ongoing maintenance well: AI-assisted development plus a monthly budget of human developer hours to build and maintain iOS and Android apps. appsubmitter.io sets up CI/CD and signing and handles submissions in your own developer accounts. For larger products, OnlineAppCreator offers long-term SLAs from an ISO-certified team in Germany. More on our prototype-to-production service, or book a free 30-minute call via the meeting planner.
Frequently asked questions
Do I have to update my app every year?
In practice, yes. Google raises the required target API level every year and Apple periodically raises the minimum SDK for uploads, so an app that is never updated eventually cannot ship fixes and may lose visibility.
What happens when my Apple distribution certificate expires?
Apps already live in the App Store keep working. You simply cannot sign and upload new builds until you create a new certificate and matching profiles.
When should we test against new iOS versions?
As soon as the developer betas are available after Apple's announcement. That leaves the summer to fix issues before most users update in autumn.
Guides on this topic
Related solutions
- App Store and Google PlayApp Store and Google Play Screenshots, Videos and Metadata Done Right
- App Store and Google PlayRejected Under Apple Guideline 4.3 Spam? Causes, Replies and Fixes
- App Store and Google PlayFixing an Apple Guideline 5.1.1 Data Collection and Privacy Rejection
- App Store and Google PlayReleasing a FlutterFlow App to the App Store and Google Play
Talk to us about your project
Honest advice on your idea, prototype or app.
- 30 minutes
- Free
- No obligation
