GitHub user breautek added a comment to the discussion: cordova-ios 8.0.0: Support minimum iOS 15
> > It's a bit of an ethical decision in a world of planned obsolescence, > > climate change, and rampant e-waste to make choices around which devices > > you're willing to support. Oddly enough, I am in support of this virtually in every other context I can think of. Dpogue really provoked some thought on this because I've always been the person to bump minimum requirements usually by looking at some metrics including but not limited to: - market share usage - Debug and Testability/Support of underlying tools - Software or technical requirements requiring newer features - Security concerns And I feel like we have hit some of these checkpoints. E.g. on XCode 26 afaik you can't install any simulator older than iOS 15. Even if I go into my simulators and add a new one for an older device like 1st gen iPhone SE, the oldest runtime I can download is iOS 15.0. Which makes testing or supporting anything older a bit difficult. But I admit this is viewing the problem from an app development lens, not from framework development lens. Diving deeper... > Debug and Testability/Support of underlying tools In order to properly test older iOS platforms, one would need to either have physical devices, or they will need to have an older XCode version available, potentially requiring an older MacOS version depending on how far back you actually need to go. So that you can get access to the older iOS simulator runtimes. > Security concerns Honestly, while security concerns are present in general usage of an out-dated OS, I don't think this applies directly to the Cordova framework, unless if the security issue involves linking with a particular SDK version. > Software or technical requirements requiring newer features Sometimes supporting older platforms requires holding off migrating off of deprecated features as the replacement has a higher minimum version. So either we are stuck with using deprecated APIs that is no longer recommended, or we create two pathways via runtime version checks and/or compiler macros. I think this needs an evaluation on a case-by-case basis, but there is definitely a balance required in my opinion. So I feel like supporting iOS 11 in 2025, going on 2026 is definitely a bit much. There is a lot of features I think we can look into integrating if we bump it up to at least iOS 13. I'm not sure if there is anything that requires iOS 15 so I think I'm +0 for that. Bias disclaimer: In my own apps, I use Google Maps, which I typically keep at a modern version. Their latest major has a minimum iOS of 16, which they treat has "frozen", which means while they support iOS 16, they will not address any issues for iOS 16 in normal circumstances. So as a result, my own apps are iOS 16+. GitHub link: https://github.com/apache/cordova/discussions/566#discussioncomment-14677320 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
