11 May
Posted by Matt
in apple, buttons
Whilst fighting with a Mac today to test a website, I suddenly realized why I find most Apple products a hassle to use - they hate buttons.
Even the newest Apple laptops have only a single mouse button. Whilst I'm sure 90% of the computer-savvy world will accept this, to me it's a hindrance. Generally, for any object I may aim my mouse at, there's one of two things I want to do - select it for some future operation, or do something to it immediately. This is why two mouse buttons work well - one is always used to select, one is always used to view further options.
On a Mac you have to hold the Apple key down to get this options menu which is annoying at the least, especially on a laptop. Or you have to always select first then dive into some menu to perform your operation.
OK, so far this post seems like me just being a hater, but think about this premise other situations, specifically the iPhone. One of the problems with a small device is always the screen - how do you show large amounts of information in such a small space yet allow the user to interact with the unit efficiently?
Generally on smaller screens you have to split large functionality into smaller steps so you can navigate through those steps to get to the end result. Most iPhone apps have option icons at the bottom, and a bar at the top allowing the user to go back (or forward) to the previous step or screen. The top and bottom bars can take up almost 20% of the available screen, leaving much less actual content area (see below).
This is where Google's Android system really excels. They thought about this, realized what the most used operations would be and figured it would be a great idea to have a MENU and a BACK button on every Android phone, thus freeing up vital screen real estate for the application itself.
Imagine having two extra buttons on the iPhone, to the left and right of the main home button. Think how games could use these for easy directionality without you having to clumsily cover up half the screen with your pudgy fingers.
Simple stuff really, but it makes a world of difference to the user.
Comments
But...
Them buttons can't be labeled distinctly on a per-application basis :)
I'd argue Android apps are less usable and inconsistent because those h/w buttons are used in different ways across different applications.
No menu and back buttons are a big mistake
I am porting an Android app to the iPhone right now, and came across this article. I was searching for a way to avoid implementing on screen menu/back buttons, but it doesn't look like I have much of a choice on the iPhone, so now I have to redesign/squish my interface. Whatever my design will end up being, there is no way it will be as clean as it is for Android. My app is game targeting little kids as end users. Taking up real estate on the iPhone screen with non-game buttons takes away from the experience of the app, by distracting and providing a chance for them to hit those buttons by accident. Sometimes people over-engineer, but in Apple's case they tend to over-simplify. I think Android did it right by adding the back and menu buttons (the search button I don't think was necessary, but it's Google the search giant, so we have to deal with it).
Can you give me an example? I
Can you give me an example? I can't think of a situation where the buttons are used differently.
Well reading what this guy says...
http://allancaeg.blogspot.com/2010/02/ux-of-android-os-buttons.html
I must confess I haven't spent more than a few minutes with an Android phone so I can't comment based on direct experience. However, I _have_ had experience with many other phones that include multiple h/w buttons and I've yet to see any that implement them as intuitively as the iPhone does with its single button with on-screen / dynamically-labeled buttons. Especially when you allow 3rd party apps access to them h/w buttons and NOT pass them through any kind of approval system to ensure they conform to style/user guidelines ;) (Yes big brother control is bad in some cases but it has its perks too.)
Yes, you lose a little screen real-estate but I'd say that's worth sacrificing.
I doubt it'd bother me that much though. I'm thinking far more of average Joe on the street.
Interesting reading. He has
Interesting reading. He has a valid point whereby you don't always know what the back button will do (I admit I've had a similar experience - the stock Calendar app for example is particularly frustrating - if you click an event, it goes to the details, but pressing BACK takes you out of the app instead of back to the week/month view, Luckily the HTC Sense UI version is much better).
I guess at the end of the day it's personal preference more than anything else. I like getting as much important stuff on my screen as possible. Once I'm used to an app, I know what back will do and if menu will do anything or not.
But...
Them buttons can't be labeled distinctly on a per-application basis :)
I'd argue Android apps are less usable and inconsistent because those h/w buttons are used in different ways across different applications.