The "after" screenshots don't seem to have anything in common anymore. Some of the apps look like Android, some look like Windows Phone, some look like Palm webOS. The previous iterations at least shared a few button styles and navigation bar styles, but now it seems like everyone has taken the opportunity to reinvent those too. It's certainly ok by me that app developers are taking more liberties in making their app…
iOS 7 before and after screenshots
101–110 of 165 posts
Re: iOS 7 before and after screenshots
#102Earlier quoted context omitted.
To be fair it's a new style language. It's going to take time for people to normalize on designs. Eventually I think that there will be a more homogeneous experience, but right now everyone is trying to feel it out and explore. Design follows trends, but right now there aren't any trends to follow in ios7.
Previously, wasn't it just follow Apple's style guide or go home? If so, what's happened in iOS 7? Are Apple just being far more lax in enforcing a style guide or is the style guide out of the window now?
No, it never was that way. In fact, Apple has even given Awards to third party apps with totally unique UIs.
Re: iOS 7 before and after screenshots
#103Up until this point I always recommended the iphone to anyone who just wanted a phone that worked, and didn't want to have to worry about bugs, or confusing UI (even though personally I'm a windows phone guy, I can't recommend the OS because it doesn't yet match the full feature set of iOS or Android).
Re: iOS 7 before and after screenshots
#104The "after" screenshots don't seem to have anything in common anymore. Some of the apps look like Android, some look like Windows Phone, some look like Palm webOS. The previous iterations at least shared a few button styles and navigation bar styles, but now it seems like everyone has taken the opportunity to reinvent those too. It's certainly ok by me that app developers are taking more liberties in making their app…
Re: iOS 7 before and after screenshots
#105Wow. Hipmunk is a great example, in my opinion, of how flat can be bad by removing so many visual cues. The old one is easy to see, understand, and instantaneously "grok", because of the depth cues and shading. The new one is a mess of plain colored boxes, where you have to spend time figuring out what is a header, what is a row, etc. -- it's not instantly obvious. The prices are clearly clickable on the left, on the…
Hipmunk really makes the problems of flat design stand out. There is a common belief that simpler design means better UE. The things that are being tossed out in flat design are the things that often made good designs intuitive in the first place though. Many designers are reaching incorrect conclusions about simplicity and the whole KISS principle. The whole KISS principle doesn't require throwing out pixels and pro…
SeatGeek is an example of almost pure dimensional flattening. It's pretty much the same. Just feels a bit cleaner and more elegant. Especially notice how they replaced the shadow with a grey border. The shadow played the role of a separator. Thus they replaced it with a flat separator. What the other kind of a 'flattener' might do is just throw away the separator completely. And that is where you can screw up.
Re: iOS 7 before and after screenshots
#106Re: iOS 7 before and after screenshots
#107Re: iOS 7 before and after screenshots
#108Re: iOS 7 before and after screenshots
#109iOS 7 is less about how it looks and more about how it feels. Hence screenshots are a poor medium for criticism compared to iOS 6.
Re: iOS 7 before and after screenshots
#110Few of these look better, IMO. And I'm definitely not seeing a lot of consistency in design. That said, many of them weren't great in the first place anyway. One clear trend: getting rid of the bottom tab bar. I will mourn that loss - the top left corner is the least accessible place on the screen, and Apple saw fit to put the most important button (Back) there. The bottom bar was a very accessible shortcut in many a…
iOS7 has a swipe from the left gesture that will trigger the back event, for apps that support it. Long overdue imo and it helps some with what you're describing.
The change to a swipe might reduce the accidental fat finger, but discovery is a nightmare for both the gesture itself and application specific behaviors for the back event.
I prefer an application button in both cases, especially because it makes it clear that this is something that will only effect the app, and will not have a weird OS interaction, taking me out of the app.