3 ms·
I know, but even with my small app I don't feel comfortable dropping support for the 20% users who are behind. And if I'm supposed to maintain both the old and
by yreg 3y ago
I know, but even with my small app I don't feel comfortable dropping support for the 20% users who are behind. And if I'm supposed to maintain both the old and the new API in parallel then why bother.
Now for new apps I can see going all in with the latest SDKs.
- valianteffort 3y agoI mean it's not too complicated to add OS specific exceptions in Swift. You can build your app for the lowest version you want to support and add newer OS features a la carte.
- szundi 3y agoWhile you're finishing it, it goes to 5%
- yreg 3y agoSo be it. I released a year ago and for now I support iOS 14.0 and above. I just think it's the right thing to do when reasonable enough. I will probably rewrite some parts to more modern SDKs and cut that support at some point, but I don't want to do it just for the sake of using the newest thing.
- Jaxan 3y agoThanks! I appreciate this attitude as I’m stuck on iOS 15, but still like my phone as it is.