home > services 

Adaptive Path Blog

The Team

Andrew

An Observation About Android’s Menu Key

by Andrew Crow

I’ve been using a Nexus One for a month or so now and there is one singular annoyance that continues to frustrate – the heavy reliance on the Menu button to access critical app functionality.

During SXSW, I was talking to a friend who works at Google about this issue and he pointed out something I hadn’t thought about. Turns out, this is a by-product of an evolving operating system for multiple hardware devices. While Android officially requires a touchscreen for Android devices that want to have the ability to install 3rd party apps, there isn’t much that cannot be done by navigating using hard buttons. And, if I’m not mistaken, it wasn’t until Android 2.0 that more softkey functionality was made available.

So, you have a philosophy of supporting multiple versions of hardware and, because of this, not every combination of SW and HW are perfectly matched.

My reaction to this is, yeah, that makes sense. But, every time I have to tap multiple times to get to something in that Menu area, I find it frustrating.

4 Responses to “An Observation About Android’s Menu Key”

  1. Andrew Crow Says:

    Oh yeah, so this is a new thing for our blog. We’re thinking or trying to post more observations or little things that pop into our heads. Honestly, there’s concern that with so many people reading this, we have to have perfectly well-formed, well-thought out opinions on ideas. This bite-sized approach might help stimulate more conversation.

    So, bear with us as we try this out. I’m looking forward to challenges to my post above. Or, better yet, some additional information about the topic.

  2. Ix Says:

    You know, another great example of this is the Blackberry Storm. I was not a huge fan of the Blackberry OS to begin with, but when they switched to a touch screen for the Storm they basically just made the on-screen buttons bigger, which just made the problems in the OS bigger. At some point the problems of software made to use hardware keys outweigh the benefits of a touch interface. The Storm passed that point, but it sounds like Android hasn’t.

  3. Justin Baum Says:

    Andrew, the droid was my first Android device and this design *choice* JUMPED right out at me. I remember opening up the gmail app for the first time and just seeing a list of emails with no controls. “Where is the UI?! Ah yes, buried in a menu. Fantastic.” What pains me, is that when I open up my fav google web app (reader) this is turned on its head. Not only are there hardware UI legacy issues around android apps, but googles mobile web apps feel entirely different. Challenging stuff.

  4. adaptive path » blog » Andrew Crow » An Observation About … — Think Geek Australia Says:

    [...] adaptive path » blog » Andrew Crow » An Observation About … [...]


Where do great ideas come from?

At Adaptive Path, our ideas are driven by the work we do. We do consulting for user interface and user experience design, and offer conferences, training and education for UX designers.

From field ethnography, UI wireframes and task flows, to visual design and implementation, we do it and we teach it.

Learn more in our video, Adaptive Path in 2 ½ Minutes:

ap-video

Want to know more about Adaptive Path? You should read more about our services or contact us to find out how we can help you!

Email Newsletter

Sign up to receive essays, appearance dates and other news from Adaptive Path.