Should you require the new iOS? A five-question checklist before you touch the deployment target

Every September, a team member asks whether to require the new iOS version. It may seem like a minor task, but raising the minimum operating system (OS) can unintentionally remove paying users from your app. Raising the OS minimum is just one of a few decisions that can quietly remove users, and this decision is often made in a brief conversation. To help slow down such conversations, APPDOOK uses a checklist that addresses five key questions:

1. Can every affected user genuinely update? People often overlook the fact that the user who hasn't tapped 'Update' might exist, but this isn't the main concern. The real issue lies with hardware. iOS 27, released on September 14, works on the iPhone 15 Pro and Pro Max, iPhone 16 lineup and beyond, iPhone Air, and iPhone Duo. Devices older than the iPhone 16 are excluded.

This means users who purchased non-Pro iPhones within the past two years will be left out. For them, a higher deployment target isn't a gentle reminder to update their device; it's a demand to buy a new phone. Most won't comply, and they won't express their dissatisfaction through emails or complaints. They'll simply stop receiving updates or finding your app in the App Store.

2. Is the API you're eager to use critical, or merely convenient? Usually, the reasoning behind raising the OS target is due to a specific API. Take a moment to assess whether it's a convenient feature or a crucial one. If it's just convenient, you can check for the availability of the newer OS with a few lines of code: if #available (iOS 27, *) { useNewAPI() } else { useExistingPath() } However, if it's a load-bearing API, you'll need a well-designed fallback plan, regardless of the OS version.

A feature that disappears silently on older devices doesn't save any work; it turns into support tickets instead.

3. Are you confused between building with the new SDK and requiring the new OS? Many misunderstand these two separate decisions. Building against the newest SDK is straightforward and you should do it right away. It gives you access to new APIs and allows you to catch deprecation warnings early. Requiring the newest OS, on the other hand, is costly and can affect a significant portion of your user base, as explained in the previous points. You can proceed with building against the latest SDK without needing to require the newest OS.

4. Do you have your own data? Industry averages regarding OS adoption are interesting, but they don't directly apply to your users. Before discussing this decision, gather your own OS version split from your analytics or App Store Connect. Once you have your own data, you can determine whether cutting off a certain percentage of your active users is justified or not.

5. Is this a genuine exception? There are instances where raising the new OS version is acceptable: launching a brand-new app with no installed base, an internal tool on managed devices, where you are aware of the exact hardware in your fleet. These are rare cases compared to the number of times this question gets asked. Keep in mind that other situations exist where requiring the newest OS is not a good idea.

As a general rule, maintain the current deployment target and adopt new APIs using availability checks. Build and test your app against the new SDK now. Bring your own OS version numbers to the discussion. Finally, reschedule the question to discuss the issue again in about a year once the current hardware generation has spread.