2 ms·
There's a sliding scale here. I don't think anyone is expecting app developers to support every OS version that ever existed. But iOS8 doesn't work on the iPhon
by untog 12y ago
There's a sliding scale here. I don't think anyone is expecting app developers to support every OS version that ever existed. But iOS8 doesn't work on the iPhone 4, and according to comments on here works pretty terribly on the 4S, and even on the 5.
Supporting the current version and the most recent version doesn't feel like the biggest imposition. As a web developer we've adopted it - we just phased out iOS6 support now that we're looking at iOS8. And there aren't actually that many differences between 7 and 8 - especially compared to 6 and 7. What iOS8-specific SDK features are developers using that means they absolutely have to only target iOS8?
- rqebmm 12y agoThe difference is that as a web developer you don't have to drop roughly ~$2k on devices to test the older versions of browsers, you just fire up a VM. Apple developers can't roll back the OS version, and need to have at least one 4/4s, one 5/5s, and one iPad for each OS they would like to support. Let alone the new screen fragmentation. The inability to roll back iOS is inconvenient for customers, but it's a HUGE middle-finger to developers. Customer are caught between "don't update a few of my apps" while we are caught between "don't support a number of new users" and "spend a lot of extra time and effort"
- untog 12y agoThe difference is that as a web developer you don't have to drop roughly ~$2k on devices to test the older versions of browsers, you just fire up a VM. Why? You can fire up an iOS Simulator just as easily for web developer as you can native development. The same issues affect both. In neither case would I suggest relying on simulated versions of devices - I've been caught out by too many touch event oddities in the past.