Live data from Hacker News

iOS 7 only is the only sane thing to do

berzniz.com

21–30 of 82 posts

Re: iOS 7 only is the only sane thing to do

#21

Earlier quoted context omitted.

I agree that the article could've gone into more depth about the difficulties they faced, but most developers will agree "a lot of the UI is compromise" is the key point. Supporting iOS 6 and 7 visuals at the same time just means your app looks out of place in both versions.

> 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.

Re: iOS 7 only is the only sane thing to do

#22
post #17
post #14

Earlier quoted context omitted.

Our app is iPhone only, but this is a great point to remember for anyone thinking about dropping the non-retina image.

People with non-retina iPads can and will download your app.

Non-retina iPads use retina assets for iPhone apps.

Re: iOS 7 only is the only sane thing to do

#24
post #14

Great points, except for "@2x only." If your app supports iPads, then the iPad 2 and iPad Mini (first generation) are both non-Retina screens and are still available for sale directly from Apple. Given Apple's 3 year support cycles, iOS 10 will be the first iOS that can fully drop support for non-retina displays if the iPad 2 and original iPad mini are discontinued by the end of this year.

Our app is iPhone only, but this is a great point to remember for anyone thinking about dropping the non-retina image.

Unfortunately, an app cannot be made `-568h` only. And -[UIImage imageWithName:] does not support `-568h` infix.

Re: iOS 7 only is the only sane thing to do

#25
I've done the same for the app that I work on, but not because I needed an if-else for the UI code. The biggest problem for me was that every now and then, I'd get a bug that shows up on a device, but not the simulator. If this happens even once, it is one time too many for a small team without a lot of leftover devices to sport old iOS versions on.

Re: iOS 7 only is the only sane thing to do

#27
post #7

> When we added pull to refresh to our app there weren’t many apps using this technique and it added a premium feel to our app. This makes me want to vomit. I can't wait until implementing flashy UI is so trivial and common that shallow things like this don't actually affect an application's perceived value. I don't remember the transition to GUI in the 80s as being as shallow as the mobile app market is.

Its not shallow, it makes the app easier to use and therefore better designed. Also, perception is reality.

I contest the idea that any two apps are so similar that something as trivial as list-refresh mechanism could push one over the top.

Re: iOS 7 only is the only sane thing to do

#29
post #24
post #14

Earlier quoted context omitted.

Our app is iPhone only, but this is a great point to remember for anyone thinking about dropping the non-retina image.

Unfortunately, an app cannot be made `-568h` only. And -[UIImage imageWithName:] does not support `-568h` infix.

Which is pretty lame considering xcassets supports an image 'subtype' called R4 that's designed for 4" screens.
Post reply on HN