3 ms·
Don't look at it as "not supporting an 8-year-old device" which can't get the update; look at it through the lens of "not supporting an OS which had its initial
by verandaguy 2y ago
Don't look at it as "not supporting an 8-year-old device" which can't get the update; look at it through the lens of "not supporting an OS which had its initial release just under 3 years ago and is still receiving support itself."
There are plenty of reasons (of varying reasonableness) to avoid an update; people on an OS version this new shouldn't be getting this kind of harsh treatment.
If you have app features that rely on a new iOS feature, you could just put those behind a feature flag.
If your core API changes substantially over time meaning that out-of-date versions of your app quickly stop working without updates, it's better for the user if you use something like Swagger to auto-generate the API stubs; it makes it much easier to support your app in the long term, even for users on what would otherwise be unsupported platforms.
If you're dropping support because supporting an older OS creates irreparable security issues, well, I guess in this case they might actually be ok with that.
- stackskipton 2y agoiOS ecosystem generally doesn't work like that. Most people upgrade to latest when latest.1 comes out so around December. Those on latest - 1 will remain until they become latest - 2 next September and by then, they will very likely upgrade to latest because they buy a new phone. See this blog article by Telmetry Deck about iOS 17 adoption: https://telemetrydeck.com/blog/ios-market-share-13-23/ https://telemetrydeck.com/blog/ios-market-share-13-23/ Since Apple controls phone updates and phone support is long, unlike Android, most companies only do latest - 1 except around September when they will do latest - 2. However, most don't cut people off, you are just unsupported land and they will if older iOS versions give them any trouble.