Choosing a Minimum iOS Version: Subscriber Data vs. Shipping Speed
Raising an app's minimum iOS version is a trade, not a free upgrade. The upside is one design system, fewer test devices, and faster shipping. The cost is every new customer on an older OS you can no longer acquire, plus existing users frozen at their last compatible build. This guide lays out the evidence, the trade-offs, and a repeatable way to run the numbers on your own app.
What the subscriber data actually shows
A published subscription-platform analysis found that roughly 88% of paid subscribers who opened an app in the last 90 days were on iOS 26. That leaves iOS 18 at about 9.4% of subscribers and 9.6% of revenue. New transactions follow a similar pattern, with 85% occurring on iOS 26.
Those figures are platform-wide averages, and they include very large apps that pull the mix toward the broadest possible audience. A smaller or more specialized app can land well above that average. One indie weather app, Weather Up, saw roughly 94% of paying users active in the past 90 days on iOS 26.
Apple's own adoption reporting before WWDC put iOS 26 on 79% of all iPhones and 86% of iPhones introduced in the last four years. The subscriber numbers run higher than device adoption because people who pay tend to be on newer hardware.
The two costs of raising the floor
Raising the minimum OS affects two groups. People already on an older version retain the app, yet their updates end at the last build that supported their OS. People on an older version who have not installed yet cannot download it at all.
The second cost is the one that compounds. Every new customer you cannot acquire is a customer you never had the chance to convert. That is why the decision should be driven by new-user and new-purchase mix, not only by the installed base of current subscribers.
A conservative benchmark comes from David Smith, who found that requiring the latest OS nine months into the iOS 18 cycle would have cut about 9% of Widgetsmith's new downloads. His threshold: wait until older versions fall to roughly 1% of new downloads. A more aggressive line is under 10% of new paying users, provided the velocity gain is real.
Why some teams cut early
Three forces push the minimum version up faster than raw adoption would suggest.
First, since April 28, every App Store submission must be built with the iOS 26 SDK. An app that still supports iOS 18 renders Liquid Glass for iOS 26 users while maintaining a second design system for everyone else, which means shipping and QA-ing two visual languages in one binary.
Second, iOS 27 runs on the same devices as iOS 26 (iPhone 11 and newer). Requiring iOS 26 does not strand anyone whose hardware could go further; the excluded group is on 2018-or-older iPhones.
Third, the cost shrinks every month. iOS 18 was down to about 10% of active devices by the end of June, per TelemetryDeck. A minimum that costs a little today costs less in the fall and almost nothing by next spring.
There is also a practical testing problem. If nobody on the team owns a device running the older OS, support can only be validated in a simulator, which is a quiet risk when the people on that OS are paying you.
When cutting older versions is the wrong call
Some apps should not take this trade at all.
- Audiences skewed toward older devices. Kids apps are the clearest case, since parents hand down old phones and buy used ones. Games with older demographics fit here too.
- Freemium apps that depend on reach. Free users skew toward older OS versions. If a large free tier feeds a small paid one, cutting old versions taxes the top of the funnel hardest.
- Apps people need rather than want. If the app touches health, safety, or money, telling users to buy a newer phone is not an acceptable answer.
Where a company sits on this spectrum tends to mirror how it makes money. WhatsApp, for instance, still runs on iOS 15.1 from 2021 because its product is reach. Airbnb and Gmail, by contrast, already ask for iOS 18. Each is a coherent choice for a different objective, not a right-versus-wrong split.
One useful nuance: OS version is a proxy for device age, and device age is a proxy for purchase intent. The current price of the device may be a sharper signal than the OS version itself.
The case for keeping backward compatibility
The strongest counterargument is that backward compatibility is often cheap. With availability checks and modern AI coding tools, supporting several older versions can be close to no work for some app types. If old-version support costs almost nothing, keep it.
But "almost nothing" deserves scrutiny. Maintaining two design systems carries real overhead, and so does a device matrix you cannot test on hardware. And the position that an app is better available and possibly buggy than unavailable is harder to defend when the person hitting the bug is a paying subscriber.
The right answer depends on what the app actually does and how much the older OS constrains the experience.
How to run the numbers on your own app
Do not inherit last year's minimum by default, and do not inherit someone else's. Check four things in your own subscription data.
- New users by OS version. In your subscription analytics tool, open the Customers tab, click "New audience", filter "First seen" to the last 90 days, export all, and analyze the result. For Weather Up, 83% of new users in the past 90 days were on iOS 26 or newer.
- New purchases by OS version. In the Customers tab, select "New audience", filter "First purchase date" to the last 90 days, export, and analyze. For Weather Up, 85% of new purchases were on iOS 26 or newer.
- Active subscribers by last seen OS version. In the Customers tab, select "Active subscribers", export, and analyze. For Weather Up, 94% of active subscribers were on iOS 26 or newer, and 8.5% were already on the iOS 27 beta.
- What the floor buys you. If requiring iOS 26 leaves your shipping scope and release pace unchanged, there is nothing to weigh. The payoff shows up when the UI depends heavily on Liquid Glass, or when the app is built on frameworks that exist only in iOS 26 and later — there the extra speed is concrete.
A worked example: Weather Up's data showed a potential loss of about 15% of new purchases, more than expected. Two factors tipped the decision anyway. A 4.0 update fully embracing Liquid Glass would have to be dragged through a second older design system, and the past 90 days of traffic came mostly from App Store search and featuring, which reach the broadest and least bleeding-edge audience. A launch alongside iOS 27 in the fall should skew new downloads back toward early adopters, closer to the 94% of active subscribers.
Your new-payer mix is not a fixed property of your app; it follows your traffic. Pick your line on purpose and treat it as a line, not a law.
A decision checklist
Before changing your minimum iOS version, answer these questions.
- What share of new users in the last 90 days are on the older OS?
- What share of new purchases in the last 90 days are on the older OS?
- What share of active subscribers are on the older OS?
- Does the older OS force a second design system or a second set of framework code paths?
- Can the team test on real devices running the older OS?
- Does the app serve an audience that depends on older hardware (kids, older demographics, health, safety, money)?
- Is the app freemium with a large free tier that needs reach?
- What would the velocity gain actually be, in features shipped or weeks saved?
If the older OS share of new purchases is small and the velocity gain is real, cutting is defensible. If either condition fails, keep supporting it.
Frequently asked questions
What share of paying subscribers are on iOS 26?
A published subscription-platform analysis found that about 88% of paid subscribers who opened an app in the last 90 days were on iOS 26. iOS 18 still accounted for 9.4% of subscribers and 9.6% of revenue, and 85% of new transactions happened on iOS 26. Individual apps vary; one indie weather app saw roughly 94% of active paying users on iOS 26.
What happens to existing users when I raise the minimum iOS version?
Existing users on older versions keep the app but are frozen at the last compatible update. New users on older versions cannot download the app at all. The second effect is the larger cost, because every new customer you cannot acquire is gone permanently.
Does requiring iOS 26 strand users on hardware that could run newer versions?
No. iOS 27 runs on the same devices as iOS 26, iPhone 11 and newer. Requiring iOS 26 only excludes users on 2018-or-older iPhones.
Which apps should keep supporting older iOS versions?
Apps whose audience skews toward older devices (kids apps, games with older demographics), freemium apps that depend on a large free tier for reach, and apps people depend on for health, safety, or money. If backward compatibility costs almost nothing for your app type, keeping it is reasonable.
How do I check my own app's OS mix?
In your subscription analytics tool's Customers tab, create a "New audience" filtered by "First seen" (last 90 days) for new users, or by "First purchase date" (last 90 days) for new purchases, then export and analyze. For active subscribers, select "Active subscribers" and export. Compare the share on your candidate minimum OS against the velocity gain you expect.