Originally shared by Andrea Riva
TL;DR (which imho is equally true for both Apple and Google): a button should be a button!
TL;DR (which imho is equally true for both Apple and Google): a button should be a button!
Published
Originally shared by Andrea Riva
TL;DR (which imho is equally true for both Apple and Google): a button should be a button!
John Hardy Developer 
I just poke and swipe everything to see what happens.
LikeLike
Android won two minor victories in the article — the universal back button, and earlier implementation of a keyboard that shows character case.
LikeLike
That universal undo button is a big one. All android devices have some button that lets you undo, and also a task-switcher, as well as the home button, and on my own device, these are actual physical buttons. Without these, I get very frustrated very quickly, which is why I avoid iPhones.
I have a laundry list of complaints with touch UIs. Fortunately, most UIs I work with have the good sense not to do anything important after a single touch, usually a button press executes an action that can be undone, or an action that can be canceled before executing. If Apple software doesn’t do that anymore, they really have lost their touch. (No pun intended).
But interoperability on all touch UIs that I have used are just plain awful.
LikeLike