Fashion, Food & Business School

Feb 08 2012
uxrave:

Excellent article by @globalmoxie: Designing for Touch
“Stacking controls in a touch interface should always be avoided, especially at screen bottom. Unfortunately, that means Android apps should have their controls at the top of the screen to avoid crowding the system buttons. It’s not ideal: this puts navigation outside the thumb zone, and when you tap a button, the hand covers the entire screen. But it’s better than the alternative, which invites fat-finger errors.”“For Android, app navigation and controls should float to the top. This is the reverse of the convention for iPhone, where the Home button doesn’t create the same kind of competition as Android’s buttons. Compare the Foursquare app for Android, left, and for iPhone, to see the resulting difference.”

uxrave:

Excellent article by @globalmoxie: Designing for Touch

Stacking controls in a touch interface should always be avoided, especially at screen bottom. Unfortunately, that means Android apps should have their controls at the top of the screen to avoid crowding the system buttons. It’s not ideal: this puts navigation outside the thumb zone, and when you tap a button, the hand covers the entire screen. But it’s better than the alternative, which invites fat-finger errors.”

“For Android, app navigation and controls should float to the top. This is the reverse of the convention for iPhone, where the Home button doesn’t create the same kind of competition as Android’s buttons. Compare the Foursquare app for Android, left, and for iPhone, to see the resulting difference.”

16 notes

  1. angelasw reblogged this from uxrave
  2. brunolamelas reblogged this from uxrave
  3. hola-leo reblogged this from uxrave and added:
    Interesting analysis. Don’t know if I agree with it, since...are hidden. Which is
  4. predictablyawesome reblogged this from uxrave
  5. andsometimesidothis reblogged this from uxrave
  6. uxrave posted this
Page 1 of 1