top | item 6442114

Developing for iOS 7 and supporting iOS 6

42 points| jtbrown | 12 years ago |roadfiresoftware.com | reply

14 comments

order
[+] eonil|12 years ago|reply
Posting's nice.

But, should we support users who don't even update iOS - which needs only one button tapping? Wishing them to search and install extra apps?

[+] danabramov|12 years ago|reply
Since you're asking... Had I updated to iOS 7, every single animation on my phone would have become jaggy, and the camera would just take forever (instead of current 15 seconds) to load.

Oh wait, my iPhone 35s doesn't support iOS 7 at all (for these reasons). But I know people with iPhone 4 who don't upgrade because iOS 7 lags too much even on iPhone 4.

Of course we gotta update our devices once in a while, but for those of us who don't live in the US and buy them unsubsidized, it costs some money. All I'm saying is, there are some reasons people won't upgrade right away even if they'd hell like to. Whether to support them for a while is up to you of course.

edit: and there's this iPod Touch thing of course.

[+] saurik|12 years ago|reply
Yeah, there really isn't that much excuse for all those people out there with a 4th generation iPod touch not to upgrade immediately given that Apple licenses Amazon's one-click purchase patent: they are just one button tap away from a 5th generation iPod touch, and then they can use iOS 7... that's pretty lazy ;P.
[+] next89|12 years ago|reply
I'm not updating until iOS 7 has been properly jailbroken, which may take more than half a year.
[+] gcb0|12 years ago|reply
And at another thread here people were saying how they add a fake hardware requirement (e.g front facing camera) just to deny people from installing in older phones because 'it run slow there'.
[+] jtbrown|12 years ago|reply
If you want to deny people from installing on older devices, you can just set the target to iOS 7, meaning you need iOS 7 to install it. Doing that means it can only be installed on iPhone 4 and later, iPad 2 and later, and iPod Touch 5th gen and later.
[+] misterjangles|12 years ago|reply
Great post. I've been holding off on an update due to the navbar issue and not wanting to deal with it at the moment. Thank for the write up!
[+] jtbrown|12 years ago|reply
Yeah, that navbar issue killed my productivity for at least a day. Glad I finally found the topLayoutGuide property so I can align my views properly.
[+] joshdotsmith|12 years ago|reply
Thanks for posting this, Josh! Really came at the exact right time for me as I work with our first production-worthy RubyMotion app.
[+] jtbrown|12 years ago|reply
Glad it was helpful to you. Tell me - do you build views in RubyMotion programmatically? If so, I suppose that -[UIViewController topLayoutGuide] would be useful, right?
[+] anuraj|12 years ago|reply
Not really necessary - more than 90% users upgrade anyway.
[+] jtbrown|12 years ago|reply
Eventually, yes, most users upgrade. But Apple's stats showed about 6% of users still on iOS 5 a full year after iOS 6 was released. I'd imagine we'll see similar numbers with users going from iOS 6 to 7 - lots of them won't upgrade for a full year, and some will never upgrade. Mixpanel is currently showing 36% of users on iOS 6 - that's not an insignificant number. I'll be supporting iOS 6 for probably another year.