Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Defending Android’s Hardware Buttons

vbsteven.com

Post reply on HN
Print view View original

21–30 of 32 posts

Re: Defending Android’s Hardware Buttons

#21

Post by ajross »

Wilduck wrote: post #11

My not so technically inclined mother just purchased an iPhone to "keep up with the times." Her biggest difficulty with it so far is figuring out how to move around within any application, specifically going back. It's hard for her to realize that sometimes she has to hit the button called "back" sometimes it's called "cancel" and sometimes it's called something else. She would love a back button, even if it were inc…

This is my intuition too. The iPhone model is a single app page swimming in a top-level sea with others. For some things, that's fine. But for many apps (browsers are obvious, but also games that have splash menus, anything with a folder-like hierarchy, etc...) there is a clear and obvious "back" metaphor. And iOS just doesn't do back.

That's not an excuse for Android apps that use it inconsistently obviously (though the framework is pretty good about making sure obvious implementations do the obvious thing). But on the whole I think it's a very good feature.

Likewise, "menu" is something that almost everything has and probably deserves a hardware button (or at least a button with a persistent location and presentation -- the Galaxy Nexus apparently has no "hardware" buttons outside the touchscreen).

The "search" button that so many Android phone have, on the other hand, is completely beyond me. Ridiculous.

Re: Defending Android’s Hardware Buttons

#22

Post by thebigshane »

div wrote: post #4

There are 2 things being discussed here: 1) people being confused by the back button because they don't realize it will always pop the current view of the navigationstack, which is systemwide. 2) the fact that the back, menu, search and home buttons are dedicated hardware buttons. Explaining how 1) works does not mean that 2 is not broken. Personally I find 2 to be the interesting discussion. Seeing how these hardwar…

Even though #2 isn't the topic of the original article, I also find it interesting. And looking over the comments it seems that most people prefer touch to hardware buttons.

I use my android mostly for calling, texting, music and instapaper (actually instafetch). I hate how I can't easily feel my phone and push a button for things like mute, or pause, or end call, or next song. Sometimes I actually have to unlock the phone with the top button, then swipe to really unlock, navigate to the right app/activity if it's not forefront, then look at the phone to see where the appropriate touch button is located.

Am I one of the few that wants more hardware buttons? And not the capacitive (fixed touch buttons) but the real buttons that maggit mentions elsewhere in these comments; buttons you can feel with your fingers.

Re: Defending Android’s Hardware Buttons

#23

Post by Zhenya »

ajross wrote: post #21
Wilduck wrote: post #11

My not so technically inclined mother just purchased an iPhone to "keep up with the times." Her biggest difficulty with it so far is figuring out how to move around within any application, specifically going back. It's hard for her to realize that sometimes she has to hit the button called "back" sometimes it's called "cancel" and sometimes it's called something else. She would love a back button, even if it were inc…

This is my intuition too. The iPhone model is a single app page swimming in a top-level sea with others. For some things, that's fine. But for many apps (browsers are obvious, but also games that have splash menus, anything with a folder-like hierarchy, etc...) there is a clear and obvious "back" metaphor. And iOS just doesn't do back. That's not an excuse for Android apps that use it inconsistently obviously (though…

Search button at first seemed superfluous to me also, however I have really found a few great uses. I use it all the time now:

Instead of launching the browser and then going to an web address, I can punch it in after hitting the search button. Opens browser with that address.

I never have to launch the browser and then search for something.

It's also great if you need to find someone in your contact list and dont feel like scrolling

The search button is also contextual, so that if you're within an app you can search for whatever(maps, sms etc)

Also long pressing on the search button brings up the voice commands.

Re: Defending Android’s Hardware Buttons

#24

Post by ajross »

Zhenya wrote: post #23
ajross wrote: post #21

Earlier quoted context omitted.

This is my intuition too. The iPhone model is a single app page swimming in a top-level sea with others. For some things, that's fine. But for many apps (browsers are obvious, but also games that have splash menus, anything with a folder-like hierarchy, etc...) there is a clear and obvious "back" metaphor. And iOS just doesn't do back. That's not an excuse for Android apps that use it inconsistently obviously (though…

Search button at first seemed superfluous to me also, however I have really found a few great uses. I use it all the time now: Instead of launching the browser and then going to an web address, I can punch it in after hitting the search button. Opens browser with that address. I never have to launch the browser and then search for something. It's also great if you need to find someone in your contact list and dont fe…

Sure, but I don't think that's the right criteria. Any task can be made faster by associating a fixed button with it. But every fixed button has a cost. If you do a ton of "searching" then sure, this is good. My personal usage would be improved with a "go directly to email" button. Most people don't search that much. Or if they do, they do it from a desktop widget (even faster IMHO). I don't think it's an appropriate usage for the very precious physical space on the front panel.

Re: Defending Android’s Hardware Buttons

#25

Post by Fliko »

maggit wrote: post #18
imperialWicket wrote: post #14

Earlier quoted context omitted.

I have a Samsung Captivate (AT&T's Galaxy S) and while I have been quite disappointed with the device at a high-level, my issues have not been with android or the hardware buttons. > 1. They are capacitive, so there is no tactile feedback ever You can enable haptic feedback or tones (cringe), neither of which has substantial effect on battery life. > 2. They are made to be near invisible, so you can't see them in dim…

> You can enable haptic feedback or tones (cringe) Both of which are a poor substitute for feeling the button depress. However, I was mostly concerned about feeling the button and the edges of the button before pressing it (to be able to use the buttons without looking), but I realize now that this might not be included in the commonly accepted meaning of "tactile feedback" ;) > Are you specifically concerned about t…

Haptic feedback is not a poor substitute for feeling a button depress, it's just the current reality of having a phone with a large touchscreen. You have the choice between a (relatively) much larger screen (with option of haptic feedback), or some buttons you can depress that will eventually wear out mechanically (I bet the touchscreen would outlast a mechanical button).

The only real problem I can find with not having a mechanical button is that you may sometimes bump your finger onto one of the buttons, and will find yourself suddenly in the home screen. This actually happens to me a lot in the Nexus One, but I also blame that on failed multi-touch implementation that ends up sensing my finger in some spot it's not in, or when the capacitive sensor senses my palm holding the phone through the case.

The HTC Legend menu button isn't consistent with the design of the other buttons, and it's very ambiguous. To me 'menu' is the equivalent of the home button; I expect it to take me to the home menu. Another interpretation is that it would take me to the home menu of the current application I am using, but this function is very similar to the back button.

The back arrow doesn't symbolize a lack of forward motion (it just points right to left). There are many languages (Hebrew, Persian, Japanese. Sometimes Latin and Greek too) that read from right to left defeating the universalness of the icon.

The search icon is actually designed very well as it is consistent with most devices in the world.

On the other hand is the home icon isn't very well designed on the Galaxy Nexus, but it would be very impossible to confuse the button for a shift-key, an up-arrow, or a pointed rock (I don't understand how you got the connection between a hardware button and a rock, I feel like you are just nitpicking at this point, which is why I am nitpicking your post).

In defense of the Galaxy Nexus having 3 icons instead of 4 is really more effective (why have a menu & home button, and I don't think a lot of people use the search button), it's just too bad the icons weren't designed better.

Re: Defending Android’s Hardware Buttons

#27

Post by imperialWicket »

maggit wrote: post #18
imperialWicket wrote: post #14

Earlier quoted context omitted.

I have a Samsung Captivate (AT&T's Galaxy S) and while I have been quite disappointed with the device at a high-level, my issues have not been with android or the hardware buttons. > 1. They are capacitive, so there is no tactile feedback ever You can enable haptic feedback or tones (cringe), neither of which has substantial effect on battery life. > 2. They are made to be near invisible, so you can't see them in dim…

> You can enable haptic feedback or tones (cringe) Both of which are a poor substitute for feeling the button depress. However, I was mostly concerned about feeling the button and the edges of the button before pressing it (to be able to use the buttons without looking), but I realize now that this might not be included in the commonly accepted meaning of "tactile feedback" ;) > Are you specifically concerned about t…

Part of my confusion was that I am referencing the carrier-specific US devices. The button configuration in that image isn't available from the major US carriers. Fascinate, Vibrant, and Captivate all include the menu/home/back/search buttons across the bottom (http://www.samsung.com/us/mobile/cell-phones/all-products).

I would tend to agree that the Galaxy S image you provided offers a confusing button layout for an android device.

Re: Defending Android’s Hardware Buttons

#28

Post by billpatrianakos »

The dominating theme here is how the button feels. This post is a great defense and the facts are straight but in the end facts don't matter. Feelings do.

Apple has done a magnificent job of creating loyal converts based on feelings. Their devices have traditionally been behind Android on a number of features (but always catch up later) because they focused on making people feel like they could accomplish the tasks they wanted to.

Android goes about adding features that are super coolnewawesometrendy and they give it to you right away and it's your job to jump in and learn how to use it. Apple will slowly introduce you to new concepts even if it means limiting functionality. The Android and iOS approaches are both valid but one is better for my mother while the other is better for me.

So when we talk about the back button on Android maybe we're missing the point? Maybe instead of discussing whether the button is inconsistent or not we should be talking about how to make the entire OS feel like it helps you get what you want to do done. I don't have all the answers but I do know a few of the right questions.

Assuming you give someone an Android phone or tablet who has no previous experience or expectations... How do you make the button feel like its consistent? What is the intent of someone pressing the button? How will the action of the button fit in with the rest of the user experience? How can we get users to know what to expect after a single use of the button? Is the button even necessary? Was the decision to include this button made because of preconceived notions such as how phones used to function before touch screens?

This might be a tad bit off topic but I feel like these ideas are a natural next step in the discussion.

Re: Defending Android’s Hardware Buttons

#29

Post by nextparadigms »

joebadmo wrote: post #19
nextparadigms wrote: post #17

I'm an Android user and I'll continue to be one in the forseeable future, but I have to agree that the back button "feels" inconsistent. There might be a logic behind how it works (OS-wide back button), but that doesn't mean it will make sense for the user. An app-level back-button makes a lot more sense to me. It should work just like it works in the browser. That being said, I hope Google will try to get rid of all…

To me it rarely feels inconsistent. I like that the back button remembers the context for whatever my current action is. It means I don't have to keep it in working memory. I just press back when I'm done. I also disagree with Gruber's complaint: Here’s one thing I don’t like about the Android Back button that I’ve never seen a counterargument for: it presumes that you, the user, remember the activity stack. If you t…

But if I hit back to get out of an app, I don't want to return to the previous one. I want to return to a default/home setting. And I'll usually want to use a different app after that, so I'll use the homescreen or the multitasking view anyway.
Post reply on HN