81–90 of 95 posts
Earlier quoted context omitted.
swipe up
No, in the latest update it's really gone. I sort of miss it.
and I too sort of miss it, now the app looks lifeless
Earlier quoted context omitted.
No, in the latest update it's really gone. I sort of miss it.
Yeah, I'm an idiot. I didn't get the update till after I wrote that comment. (and then noprocrast kicked in so i couldn't edit) and I too sort of miss it, now the app looks lifeless
Earlier quoted context omitted.
You have got to be kidding. That looks terrible and wastes half the space on the screen. It's not even very good skeuomorphism, the drop shadows aren't in a consistent direction, and the layering of the brushes and canvas doesn't make sense.
It is very wrong to judge Freshpaint by the static screenshot. http://www.youtube.com/watch?feature=player_detailpage&v... Note how the wet paint mixes up on canvas. More on mixing colors: http://www.youtube.com/watch?feature=player_detailpage&v... This app is really the best skeuomorphism out there.
The rest of the UI is an abject travesty.
Earlier quoted context omitted.
You mean like Notification Centre?
That's not a copy, that maybe you can call it… inspiration. By no means is identical in shape, color and functionality. But we're here discussing something much more higher than a single feature, we're talking about the entire GUI foundation.
Now thats skating to where the puck will be.
Earlier quoted context omitted.
Don't even get me started on the Android "back button". I am still regularly baffled by its behaviour. Especially when combined with the "app within an app" you get when one app launches into another. Except not really. Android Police has a great writeup on Android design weirdness with a section titled 'The Back Button - Let's Just Rename It "Shuffle" ' http://www.androidpolice.com/2013/02/04/stock-android-isnt-p...
It goes backward. It goes wherever you just were, unless it takes you up a level, and if you just press it again, it takes you back to the app you were in. It's really not hard. Contact app -> app an email address -> Gmail Compose window -BACK-> Contact app on the contact you were just on. It takes you backward, it is what makes intents and app interaction work. I can understand why its confusing to an Apple user bec…
That's not really true. The vast majority of iOS apps with nested pages will have breadcrumb navigation at the top, with a big button either saying "Back" or telling you exactly where you will be going back to.
When you launch from one app into another, that's a different matter. I agree that can be annoying/confusing. But no more annoying/confusing than I've found with Android, where I've had some apps go back to the calling app and others going back up their internal chain (to what would normally be the parent screen of the one that you've landed on).
Then there s the amount of direct manipulation in apps. Viewpagers are nice, but there isn't a lot of drag-drop, especially on tablets where it provides feedback and trains muscle memory. Audio ques, haptic feedback, animation, etc. are all dimensions in which apps can expand interactivity where the visual interface, on handsets, is tiny.
Skeuomorphism that is just pictures of things is obviously dissatisfying, but so is a flat UI that doesn't go beyond simple touch.
Earlier quoted context omitted.
> It goes backward. It goes wherever you just were, unless it takes you up a level, and if you just press it again, it takes you back to the app you were in. It's really not hard. And there's no way to tell if you're at the first "point" of the current application(in which case it will switch you to the previous one), or if it will go back to another place within the app. And the Android OS doesn't determine what the…
That's not quite the whole story. Some apps can inject extra state - so when I get an email, pull down and click, read the email and hit "back" it takes me to the inbox. Back again takes me right back where I was. I mean, come on, someone give me an example of going app->app and the back button not getting you back to where you came from.
It's not Android's fault but it does frustrate me that different apps treat the hard button differently. FWIW I would rather have it this way than the way Apple handles it.
Earlier quoted context omitted.
> animations are faster and smoother This is incorrect, and cannot be so for technical reasons. Even the Android OS team agrees on that. Perhaps you had the "new toy" effect?
Citation please? Cannot seems like an unreasonably strong claim. Given the way older iOS devices are often sluggish on newer OS releases, it seems entirely possible that the animations on the switched-from device were slower and less smooth than the animations on the switched-to device.