3 ms·

Looks cool! I have a somewhat related question for anyone who works on tools/frameworks (for iOS I guess)... is it a pain to deal with iOS versions, ARC/non-AR

by cclogg 13y ago

Looks cool! I have a somewhat related question for anyone who works on tools/frameworks (for iOS I guess)... is it a pain to deal with iOS versions, ARC/non-ARC, and anything else? I was reading the quick start guide here and I noticed it said iOS 6.0+, so I guess you just have to look at the market share and make a trade off as to how much you want to support? I've personally only worked on apps themselves, but I've always wondered if the people making Flurry, Tapjoy, etc have to go through hell getting their framework to work for every combo of Xcode and iOS out there lol.

ryanhuff 13y ago
From a developer perspective, one of things that Apple does very well is to move people to quickly adopt new versions of iOS. As of December, iOS 6+ covers over 95% of its user-base. http://appleinsider.com/articles/13/12/05/apple-pegs-ios-7-distribution-at-74-ios-6-at-22 http://appleinsider.com/articles/13/12/05/apple-pegs-ios-7-d...
jonathannorris 13y ago
Thanks for your interest! I'm one of the co-founders of Taplytics. Building for iOS in general has improved a lot. Apple has really cleaned up iOS and Xcode in the last two years, with ARC being a huge improvement for developers. Seeing that iOS 6+ is now 97.7% of devices (https://mixpanel.com/trends/#report/ios_7 https://mixpanel.com/trends/#report/ios_7), we feel that focusing on iOS 6+ is a safe bet going forward.
michaelmior 13y ago
I'm sure many others have far more experience than I do, but here's my thoughts. I think there's little value in dealing with non-ARC at this point. ARC has been supported since iOS 5, which is available for the 3GS and up. I no longer do app development full time, but as of last year, a very tiny percentage of our users were on iOS 5. Most of the new features in iOS 6 that would be used by libraries are developer conveniences and can be ignored with a bit more effort. (e.g. Auto Layout, UICollectionView) As far as different versions of Xcode, there's really no reason for developers not to use the latest in my experience, so targeting that is likely fine.
Blahah 13y ago
On AnkiMobile, whenever we find we want to use a feature or library that is much easier or only possible on later iOS versions, we review market share. We recently started retiring 4.3, and will soon retire 5. We already develop some new features only for iOS6+ devices, and simply decide at runtime whether they are to be used. It's not a huge pain, but it's a prominent feature of developing for devices that are frequently updated. We always use the latest XCode and the latest SDK. Often there are language features that greatly reduce development time, like the NSDictionary/NSArray literals for example. The only downside is that later XCode versions don't support low-iOS version simulators, so you have to test on-device only when supporting older devices. But this all helps justify to users when you stop supporting older devices.

by cclogg 13y ago

ryanhuff 13y ago

From a developer perspective, one of things that Apple does very well is to move people to quickly adopt new versions of iOS. As of December, iOS 6+ covers over 95% of its user-base. http://appleinsider.com/articles/13/12/05/apple-pegs-ios-7-distribution-at-74-ios-6-at-22 http://appleinsider.com/articles/13/12/05/apple-pegs-ios-7-d...

jonathannorris 13y ago

Thanks for your interest! I'm one of the co-founders of Taplytics. Building for iOS in general has improved a lot. Apple has really cleaned up iOS and Xcode in the last two years, with ARC being a huge improvement for developers. Seeing that iOS 6+ is now 97.7% of devices (https://mixpanel.com/trends/#report/ios_7 https://mixpanel.com/trends/#report/ios_7), we feel that focusing on iOS 6+ is a safe bet going forward.

michaelmior 13y ago

I'm sure many others have far more experience than I do, but here's my thoughts. I think there's little value in dealing with non-ARC at this point. ARC has been supported since iOS 5, which is available for the 3GS and up. I no longer do app development full time, but as of last year, a very tiny percentage of our users were on iOS 5. Most of the new features in iOS 6 that would be used by libraries are developer conveniences and can be ignored with a bit more effort. (e.g. Auto Layout, UICollectionView) As far as different versions of Xcode, there's really no reason for developers not to use the latest in my experience, so targeting that is likely fine.

Blahah 13y ago

On AnkiMobile, whenever we find we want to use a feature or library that is much easier or only possible on later iOS versions, we review market share. We recently started retiring 4.3, and will soon retire 5. We already develop some new features only for iOS6+ devices, and simply decide at runtime whether they are to be used. It's not a huge pain, but it's a prominent feature of developing for devices that are frequently updated. We always use the latest XCode and the latest SDK. Often there are language features that greatly reduce development time, like the NSDictionary/NSArray literals for example. The only downside is that later XCode versions don't support low-iOS version simulators, so you have to test on-device only when supporting older devices. But this all helps justify to users when you stop supporting older devices.