iOS 7 only is the only sane thing to do
71–80 of 82 posts
Re: iOS 7 only is the only sane thing to do
#72Earlier quoted context omitted.
I wish other developers would adopt such a considerate attitude. Alas, my personal experience is that many simply abandon users who dare to have a device more than a couple of years old. My worst personal experience being an app that became obsolete, only to be replaced by an app that doesn't support my version of iOS.
Obsoleting an app is a problem, but -- at least in the PC space -- people who do not upgrade from e.g. XP to Win7 are unlikely to pay for new apps - so, if you care about getting paid, there's no point in supporting XP home users (enterprise is different, and I do not wish to go into that). Does anyone here know if that's also true for iOS devices? I'm quite sure that the big app spenders would be the people who cont…
Re: iOS 7 only is the only sane thing to do
#73Note that Apple now keeps the previous version of the app around for users on older OSes. Of course they won't get any of the upgraded features, but at least there's still something there for them - and you won't have to worry about all that messy code for supporting multiple versions. My next app updates will also be iOS7 only, since I know the iOS6 version will still be around. Makes it much easier to decide to use…
Re: iOS 7 only is the only sane thing to do
#74I originally wrote game code with OpenGL ES, and then tried very hard to make the same code work on a Mac with regular OpenGL. It took more time than it should have to see results and it wasn’t that fun. About all I can say is that I learned a lot and OpenGL clearly runs efficiently.
After seeing Sprite Kit (Mac OS X Mavericks and iOS 7 only) and working with it, I am now completely devoted to these latest OSes. That framework has solved virtually all of my Mac/iOS parity issues, while allowing code to be almost identical in ways that really impressed me. Sprite Kit requires far less effort and it produces far greater results. About the only downside I see is that there would be no hope of porting my code to something like an Android phone (and I don’t happen to care about that).
It doesn’t hurt that Mavericks is free so about the only device left out in the cold is my old iPad. I decided that I was probably holding myself back by trying to support it anyway; the device is quite slow compared to almost any other iPad. I will likely just buy a new iPad.
Re: iOS 7 only is the only sane thing to do
#75Re: iOS 7 only is the only sane thing to do
#76Note that Apple now keeps the previous version of the app around for users on older OSes. Of course they won't get any of the upgraded features, but at least there's still something there for them - and you won't have to worry about all that messy code for supporting multiple versions. My next app updates will also be iOS7 only, since I know the iOS6 version will still be around. Makes it much easier to decide to use…
Apple only offers older versions of your app to users that have previously purchased it. New users will still get the traditional "this app requires iOS 7" failure message.
Re: iOS 7 only is the only sane thing to do
#77Re: iOS 7 only is the only sane thing to do
#78Earlier quoted context omitted.
I saw somewhere that Apple doesn't allow new apps to target less than iOS 7. Is that correct?
Depends what you mean by "target". You can specify the whatever minimum OS version you want for an app. You have probably heard something like "[After Feb 1] new apps [...] must be built with the latest version of Xcode 5 and must be optimized for iOS 7." That only means you must use the latest dev kit and satisfy some other requirements. It does not mean that you need to disable support for older OSes.
Re: iOS 7 only is the only sane thing to do
#79Earlier quoted context omitted.
> Supporting iOS 6 and 7 visuals at the same time just means your app looks out of place in both versions. It's just a little more work. Facebook looks the same on iOS 6 even now that it supports iOS 7. If you are mostly using native UI with only a few customisations, I don't see the problem.
The problem is a lot of iOS 6 apps don't use mostly native UI. The article touches on this when talking about all their custom code because previous iOS components were not as easily customizable. My next update will be iOS 7 only, at which point I plan to drop a lot of custom code and switch back to mostly native UI.
But even then you can port it to native UIKit (which is a good idea either way), and then make iOS 7 frameworks optional, and add a few UIAppearance calls for iOS 6. The last two pieces are extra effort that might not worth it for < 30% of your users, but it's still completely possible.
Re: iOS 7 only is the only sane thing to do
#80Earlier quoted context omitted.
I saw somewhere that Apple doesn't allow new apps to target less than iOS 7. Is that correct?
Depends what you mean by "target". You can specify the whatever minimum OS version you want for an app. You have probably heard something like "[After Feb 1] new apps [...] must be built with the latest version of Xcode 5 and must be optimized for iOS 7." That only means you must use the latest dev kit and satisfy some other requirements. It does not mean that you need to disable support for older OSes.