Services

iOS App Maintenance

Every September Apple ships a major iOS release, and usually by the following spring App Store uploads have to be built with its SDK. Miss that deadline and you can't ship even a bug fix. We keep your app current, compliant, and working for your users, from a rolling monthly retainer starting at £675/month.

50+ apps shipped since 2017

Why does an iOS app need ongoing maintenance?

Apple ships a major iOS release every September. Each one deprecates APIs, adds Privacy Manifest requirements, and updates App Store submission rules. Apple's annual SDK deadline is a hard cutoff, not a guideline. Since 28 April 2026, every build uploaded to App Store Connect has had to use the Xcode 26 SDK or later, and anything submitted without it is rejected automatically. The deadline moves every year. iOS 27 shipped on 14 September 2026, and as of 12 November 2026 Apple hadn't announced when the Xcode 27 SDK becomes mandatory; in 2023, 2024 and 2026 the equivalent deadline fell in late April. Apple has raised the floor too: since 9 September 2026, iOS apps uploaded to App Store Connect must target iOS 13 or later. There's no grace period, so an app that misses a cycle can't ship even a critical bug fix until it's compliant.

Apps that go unmaintained fall behind, and some get pulled. Apple sets the process out plainly: an app with no update in three years and near-zero downloads over a rolling 12-month period gets a notice in App Store Connect and 90 days to submit an update before removal, and an app that crashes on launch is removed straight away with no notice at all. Many unmaintained apps face a real remediation effort to get compliant, not a routine SDK bump. Privacy Manifest problems are a common cause, and in our experience they usually come from third-party SDK code the developer never wrote.

Getting started

Most iOS maintenance clients are in one of three situations: a developer is leaving, they've received an App Store rejection or compliance warning, or an app hasn't been actively maintained in over a year. All three are straightforward to handle. We start with a code review: Xcode SDK compliance status, Privacy Manifest completeness, dependency health across Swift Package Manager and CocoaPods (its central repository stops accepting new versions on 2 December 2026), current crash data, and any Swift deprecation warnings heading towards build errors. We document everything and scope any remediation separately before the retainer begins. Onboarding takes 3 to 5 working days. From £675/month, 3-month minimum.

If you need broader maintenance covering Android alongside iOS, our cross-platform App Care retainer covers both under one agreement.

Written by Gareth Reese, Founder and CTO of Foresight Mobile. Gareth oversees App Care engagements and has personally managed iOS maintenance transitions from departing developers, App Store compliance recoveries, and legacy Objective-C codebase modernisation projects.

How The App Gameplan works

A four-week plan with clear deliverables and a fixed price of £3,500, credited against your first development sprint.

Total client time commitment: 5-7 hours across 4 weeks

Week 1

Discovery Deep-Dive

We meet with your key stakeholders to understand your business goals, user needs, and technical constraints. You'll share any existing research, designs, or documentation you have.

Week 2

Technical Analysis

Our engineering team assesses the technical feasibility, identifies integration points with your existing systems, and evaluates architecture options.

We determine whether Flutter, native development, or another approach makes the most sense for your specific requirements.

Week 3

Prototype and Roadmap

We create clickable prototypes so you can experience your app before it's built. You'll test navigation flows, validate the user experience, and gather feedback from stakeholders.

Alongside this, we prioritise features based on business value and technical complexity, mapping out a phased delivery plan with a detailed cost estimate.

Week 4

Gameplan Delivery

You receive your complete Gameplan pack, plus a presentation walkthrough with Q&A. Your team walks away with everything needed to make a confident decision.

What your iOS App Care retainer covers

A named iOS team who stays ahead of Apple's compliance requirements, monitors your app's performance with MetricKit, and handles the App Store review process so you don't have to.

Icon

Offshore iOS Team Takeover

Taking over an iOS app from an offshore team or a departing developer is one of the most common situations we handle. Apps in this situation typically have suppressed deprecation warnings that are now approaching hard-error status, Privacy Manifests that were either never created or cover only partial data flows, and dependency trees that haven't been touched since the initial build.

We start with a code review covering: Xcode SDK compliance (which SDK version the app targets vs the current requirement), Privacy Manifest completeness, Swift Package Manager and CocoaPods dependency health (CocoaPods' central repository stops accepting new versions on 2 December 2026, so we flag any pods that won't receive future updates), current crash data if MetricKit or Crashlytics is already configured, and any deprecated APIs that are on track to become build failures in the next Xcode release.

We document everything we find. If there's remediation work needed (and there usually is), we scope it separately so you know what it costs before committing. Onboarding takes three to five days from when we have App Store Connect access and a copy of the codebase. We support apps written in Swift, Objective-C, and mixed Swift/Objective-C codebases.

Swift and Objective-C Support • Structured Code Review • Privacy Manifest Audit • 3–5 Day Onboarding • App Store Connect Access Management

Icon

TestFlight Beta Management

Every maintenance release we ship goes through TestFlight before it hits the App Store. For annual iOS compatibility updates, we use the developer beta programme to test against pre-release iOS builds from June, giving us three months to identify and fix any regressions before they affect live users. For feature releases and bug fix batches, we use an internal TestFlight group with your team before widening to a broader beta pool.

TestFlight beta management is also the right approach for App Store compliance migrations. When we make Privacy Manifest changes, Swift concurrency updates, or SDK swaps, testing through TestFlight lets us validate the changes in a production-equivalent environment before the App Store review clock starts. App Store submissions that fail review cost time; TestFlight validation catches issues before that point.

We also manage the App Store Connect configuration: app versions, release notes, phased rollout settings, and build expiry dates. When a TestFlight build is ready for App Store submission, the metadata is already prepared.

Developer Beta Testing • iOS June Beta Programme • Phased Rollout Management • App Store Connect Configuration • Pre-Submission Validation

Icon

MetricKit Performance Monitoring

MetricKit is Apple's native framework for collecting performance and diagnostic data directly from production devices, and it captures signals that third-party tools miss. While Firebase Crashlytics captures crashes, MetricKit also reports hang rates (how often the app freezes for more than 250ms), disk writes per day, CPU usage, and battery impact. These are the same measures Xcode Organizer reports for your app.

We configure MetricKit in every iOS app we maintain, set up automated alerts for threshold breaches, and review the diagnostic payloads after each iOS release. New iOS versions often change energy accounting or introduce new hang conditions in previously stable code, and MetricKit is where we see that first, before it shows up in App Store reviews.

Critical issues include a crash on launch on current iPhones, an App Store rejection blocking a live release and a critical security vulnerability. On Standard and Premium, we respond to a critical (Severity 1) issue within 2 business hours and aim to fix it within one business day, not counting app store review time. Business hours are 9:00 to 17:30 UK time, Monday to Friday, excluding UK public holidays. Essentials is best efforts, and no plan includes out-of-hours cover. Monthly health reports include MetricKit trend data, any hang or crash patterns, what we investigated, and what we fixed.

MetricKit Integration • Hang Rate Monitoring • Energy Impact Tracking • Severity 1 SLA on Standard and Premium • Monthly Health Reports

Icon

Swift and SwiftUI Modernisation

Concurrency warnings in older Swift code become hard errors once a project switches to the Swift 6 language mode. The most common pattern is UIKit-era code touching shared mutable state across threads without actor isolation. The longer these are deferred, the more disruptive the fix, so we address them incrementally during the maintenance retainer before they become blocking issues.

For apps with significant UIKit codebases, we use a hybrid architecture approach: SwiftUI for new features, incremental migration of high-traffic UIKit screens. In our experience SwiftUI screens need noticeably less code than their UIKit equivalents, and that's where the maintenance saving shows up: fewer lines to touch means updates ship faster and with fewer regressions. Swift 6.2's opt-in Approachable Concurrency has made this migration less painful too, since new code is main-actor-isolated by default rather than forcing a full concurrency audit up front.

The "Liquid Glass" design update in iOS 26 is a concrete example of why incremental modernisation matters. System components update automatically on recompile. Custom UIKit views often don't: navigation bars appear transparent, custom buttons clash with the new translucency. Apps that have already moved high-impact screens to SwiftUI handle this with minimal effort. Apps that haven't face a full custom view audit.

Swift 6 Concurrency • Actor Isolation • UIKit-to-SwiftUI Migration • Liquid Glass Compatibility • Incremental Approach

Icon

App Store Compliance

App Store policy changes arrive continuously, and the rejection consequences range from a blocked update to permanent removal. Privacy Manifests (the PrivacyInfo.xcprivacy file) are now mandatory for every app. The NSPrivacyAccessedAPITypes declarations must accurately reflect every sensitive system call in your code and in every third-party SDK you integrate. In our experience, most Privacy Manifest rejections trace back to third-party SDK code rather than the app's own.

We maintain your Privacy Manifest as a live document, updating it whenever your dependency tree changes. When a third-party SDK ships a new version with different data practices, we review the privacy impact before updating, not after a rejection. We also manage the App Tracking Transparency (ATT) prompt implementation and the App Store's data practices declarations, which must match your actual data flows.

For rejections that do happen (performance problems like crashes on launch are historically the largest category, with spam and low-value detection close behind), we handle the response to Apple's review team, implement the required change, and resubmit. Most rejections have a known resolution; the challenge is handling the review team communication efficiently, which we've done enough times to know the fastest path.

Privacy Manifests • NSPrivacyAccessedAPITypes • ATT Compliance • Rejection Management • Data Practices Declarations

Icon

Annual iOS Updates and Apple's SDK Deadline

Apple's annual iOS release cycle isn't optional. Each major version brings API deprecations, new permission requirements, App Store submission rules and, in the iOS 26 cycle, a significant UI overhaul with the "Liquid Glass" design language that causes visual regressions in custom components. Apps that aren't actively maintained fall behind this cycle, and the gap compounds: each skipped year adds more deprecated APIs, more manifest requirements, and more SwiftUI migration debt.

We test your app on the iOS developer beta from June each year, identify breaking changes and regressions, and have compatibility updates ready before the September public release. For the iOS 27 cycle that means testing on iOS 27, preparing for the Xcode 27 SDK requirement once Apple sets its date, and checking custom views and navigation components under Liquid Glass.

The Xcode 26 SDK requirement has been a hard cutoff since 28 April 2026: an app that isn't built with it can't submit any update at all. Apple raises the requirement every year, and in recent years the new deadline has fallen in late April, so we expect the Xcode 27 SDK requirement around April 2027. We track each deadline and ensure you're never in a position where a critical bug fix can't be shipped because a compliance migration wasn't done.

Annual SDK Migration • Liquid Glass UI Testing • June Beta Testing • No Submission Blocks

Do you support Objective-C iOS apps?

Yes. We maintain apps written in Objective-C, Swift, and mixed Swift/Objective-C codebases. Objective-C is still supported by Apple and remains the foundation of many long-running iOS apps, particularly those built before 2014–2016 that haven't been fully migrated.

Objective-C apps face specific maintenance considerations: the language isn't getting new features, which means any Swift-era APIs eventually need bridging headers or wrapper code; some modern SDKs have reduced or eliminated their Objective-C support; and Privacy Manifest requirements apply equally regardless of language. None of these are blockers, but they're worth knowing about when scoping maintenance work.

If an Objective-C app would benefit from incremental Swift migration (and many do, particularly if new feature development is planned), we can include that as part of the maintenance retainer, prioritising the areas of the codebase that are touched most frequently.

Can you maintain an iOS app built by another developer?

Yes. Taking over iOS apps from other developers, agencies, and offshore teams is one of the most common situations we handle. We support apps in Swift, Objective-C, and mixed Swift/Objective-C codebases, and we work with both Swift Package Manager and CocoaPods dependency management, though CocoaPods' central repository stops accepting new library versions on 2 December 2026, so part of a takeover is often planning a move to SPM where it makes sense.

We start every takeover with a structured code review covering Xcode SDK compliance status, Privacy Manifest completeness, dependency health, current crash data, and Swift deprecation warnings that are on track to become hard errors. We document everything we find and scope any remediation work separately before committing to the retainer.

Onboarding takes three to five working days from when we have App Store Connect access and a copy of the codebase. After that, the rolling monthly retainer begins. The three-month initial period exists to make the onboarding investment worthwhile for both parties.

What happens if my iOS app gets rejected from the App Store?

App Store rejections fall into a few common categories: performance issues like crashes on launch or incomplete submissions (historically the largest single category), privacy and compliance violations including Privacy Manifest problems, and policy violations related to in-app purchases or data handling. The App Store review team typically provides a rejection reason with a guideline reference.

For clients on a maintenance retainer, we handle the rejection process: we review the rejection reason, identify the root cause (which isn't always the stated guideline: sometimes the stated reason is a symptom of a deeper issue), implement the fix, test it through TestFlight, and resubmit. For most common rejection types we have established resolution playbooks.

For apps not yet on a retainer that have received an unexpected rejection, we offer a one-off triage and resolution service. If the rejection reveals underlying compliance work that needs addressing, we can scope that separately before you commit to a retainer.

What is a Privacy Manifest and does my iOS app need one?

A Privacy Manifest (PrivacyInfo.xcprivacy) is a structured file that declares your app's data collection practices, specifically which "Required Reason APIs" your app accesses and why. Required Reason APIs are system APIs that access sensitive data like file timestamps, system boot time, disk space, and user defaults. Apple introduced mandatory Privacy Manifests in iOS 17 and has been progressively enforcing them in App Store submissions since 2024.

Yes, all iOS apps need a Privacy Manifest. The complexity is that the declarations must cover not just your own code but every third-party SDK you integrate. If you use Firebase, a payment SDK, an analytics library, or any other third-party framework that accesses Required Reason APIs, their privacy practices must be reflected in your manifest. In our experience, most Privacy Manifest rejections trace back to third-party SDK code rather than the app's own.

We treat Privacy Manifests as a living document in every iOS retainer. When your dependencies change, we review the privacy impact and update the manifest before you submit an update. This prevents rejections from appearing as surprises during a time-sensitive release.

What is the App Store Xcode SDK compliance deadline?

Apple sets an annual deadline requiring all App Store submissions and updates to be built with the current Xcode SDK. Since 28 April 2026, that has meant the Xcode 26 SDK or later: any update uploaded without it is rejected automatically. The deadline recurs every year. iOS 27 shipped in September 2026; as of 12 November 2026 Apple hadn't announced the Xcode 27 SDK date, but it set the equivalent deadline in late April in 2023, 2024 and 2026, so expect it around April 2027. Separately, since 9 September 2026 iOS apps uploaded to App Store Connect must target iOS 13 or later.

The rule itself is simple: the app must be built with Xcode 26 or later using the iOS 26 SDK. The work comes from what a new SDK changes. Building with the iOS 26 SDK brings in the Liquid Glass design, so custom UI can look wrong until it's fixed. Old third-party libraries may not build with the new Xcode. An app that adds one of the commonly used SDKs on Apple's list must include that SDK's privacy manifest, and its signature if it's a binary dependency. None of this needs Swift 6's language mode, which stays optional.

If your app hasn't been actively maintained, this deadline may represent a significant sprint of remediation work rather than a routine SDK bump. We assess the scope of work for any app as part of the onboarding code review.

How much does iOS app maintenance cost in the UK?

iOS app maintenance in the UK typically costs between £675 and £1,495 per month on a retainer. Our App Care retainers start at £675 a month on the Essentials plan, covering both iOS and Android if you have both.

There are three plans. Essentials (£675 a month) covers OS and SDK updates, App Store compliance and crash monitoring. Standard (£995) adds a regular engineer check-in and a priority SLA. Premium is £1,495 a month. Premium adds emergency incident response (priority handling in business hours, best efforts outside them), quarterly architecture reviews and penetration testing. Every plan includes a monthly health report, and apps with several products or unusual complexity get custom pricing.

A fixed retainer is easier to budget for than ad-hoc billing, because Apple's yearly SDK deadline creates work whether or not anything else has changed.

What does iOS app maintenance include?

iOS app maintenance covers the ongoing technical work needed to keep a live App Store app functional, compliant, and performing well. At minimum this includes: annual Xcode SDK compatibility updates (to meet Apple's spring submission deadlines), Privacy Manifest maintenance (PrivacyInfo.xcprivacy and NSPrivacyAccessedAPITypes declarations), security patches and dependency updates, App Store compliance monitoring, and crash/hang monitoring.

A full maintenance retainer typically also includes: MetricKit performance monitoring with monthly health reports, TestFlight beta management for release testing, App Store Connect management (build submissions, release notes, review response), incremental Swift and SwiftUI modernisation, and a shared Slack channel with a named iOS engineer.

Some retainers cover feature development alongside maintenance. This is useful when you want the same team that knows the codebase to build new features, because it removes handover friction and ensures maintenance work and feature work don't conflict.

How often does an iOS app need maintenance?

At a minimum, every iOS app needs maintenance once a year: in September when Apple releases a major iOS update, and in spring when the new Xcode SDK compliance deadline hits. In practice, active maintenance work happens monthly: dependency updates, security patches, Privacy Manifest updates when third-party SDKs change, and any bug fixes that surface from crash monitoring.

The volume of work varies by how mature and actively developed the app is. A stable app with a small dependency tree and no legacy UIKit debt needs only a few hours of maintenance work a month. An app with a large dependency tree, heavy third-party SDK use and ongoing feature development needs several times that once you include regression testing and documentation.

Apps that haven't been maintained for over a year typically need a one-off remediation sprint before moving to a regular retainer, to bring the SDK compliance, Privacy Manifests, and Swift deprecations up to current standards. We assess this as part of the onboarding code review.

App Care Onboarding

How App Care Onboarding Works

Your app is live. Now it needs a team.

You've got a working app and nobody reliable to look after it. Maybe your developer handed in their notice. Maybe the offshore team stopped responding. Maybe the freelancer who built it has gone quiet at the worst possible time.

App Care onboarding gets you from that situation to a UK-based team who knows your codebase inside out, with a shared Slack channel and agreed response times. Onboarding takes 3 to 5 working days. The fee is typically £500 to £1,000 depending on complexity, and we waive it, with your first month included, if we've just rescued your app or taken it from no-code to production. After that, App Care starts at £675 a month for both iOS and Android, with a three-month minimum and then rolling monthly.

Get in Touch  
Brain icon for explore and refine concept in App development

Initial Call and Codebase Access

You describe the app; we ask the right questions and get access to what we need.

We start with a short call to understand what your app does, what platforms it runs on, and what the handover situation looks like. Then we request access to the repository (GitHub, GitLab, or Bitbucket), your App Store Connect and Google Play accounts, and any backend infrastructure. If a departing developer is still available, we'll use some of that time to fill in gaps. If not, we work from the code.

Rocket icon for manage and deliver product in App development

Code Review and Documentation

You get a plain-English written report on exactly what you've got, including anything that needs immediate attention.

We review the architecture, third-party dependencies, security posture, and anything that looks fragile. If there's technical debt that needs fixing before we can support the app properly, we scope that separately so you know what it'll cost. We also build internal documentation covering how the app is structured, where the critical logic lives, and how deployments work.

Graph icon for business growth in app development

Monitoring and Pipeline Setup

Crashes and performance problems get caught before your users report them.

We add Firebase Crashlytics and Sentry for crash reporting, and set up CI/CD pipelines so releases don't depend on one developer's laptop. Test builds go out through TestFlight on iOS and Google Play's internal testing track on Android.

Graph icon for business growth in app development

Rolling Monthly Retainer

From this point, you have a named UK team on Slack who knows your app and is responsible for keeping it healthy.

Your retainer covers OS updates, security patches, App Store compliance, crash investigation, and proactive monitoring. Feature work is scoped and priced separately so you always know what you're paying for. The initial commitment is three months, then rolling monthly with no long-term lock-in. You stay because the service is good, not because you're contractually stuck.

Why Work With Us?

Your app, your way. Here's how we make it happen

What our clients say

Wildgoose engaged Foresight Mobile for ongoing iOS and Android app support and modernisation

Facebook - Elements Webflow Library - BRIX Templates

"The difference was immediate"

Before Foresight came on board, we had crash reporting installed but it wasn't telling us anything useful. We knew the app had issues but couldn't see where they were coming from. Within weeks of the engagement starting, we had a proper picture of what was happening in production and could start working through the backlog. The difference was immediate.

Ross Greenhalf
Testimonials

What our clients think

Get in Touch  

“They’re more thoughtful than any other development team I’ve worked with..... I’m not sure what they could improve."

Mark Bryk
CTO, Prax

"The team has delivered exactly what we asked for but is able to use their own skill and judgment to make improvements"

Frederick Drapkin
CEO and Founder, Tenner

"Foresight Mobile effectively and promptly met our needs. They were a candid, reliable, and collaborative partner."

Fumbi Kolawole
Our Work

Some of our iOS App Care clients

Graph Icon - Agency X Webflow Template

Email List Growth

Lorem ipsum dolor sit amet, consectetur adipiscing elit. At sedcon vestibulum ac diam. Enim praesent cras bibendum elit id condimentum etiam.

Latest Articles

All Articles