News for hackers. Stuff that matters.

A comment on Android Design. Parent comment

Re:Android Design by cuu508 on Thursday January 12, 2012 @07:12PM (#3458562)
I'd be wary of configuration settings like this, they sidestep the problem and create another one--you still have potentially confusing navigation and now there's more clutter in configuration screen. In this case, the configuration setting is badly named too, 'Manage "Back" button' makes sense to the developer, less so to the user.

There are useful settings that help me accomplish the task, and then there are not so useful settings where developer simply couldn't decide. I particulary dislike configuration UIs that devote whole section of toggles and switches for configuring the configuration screen itself.

[ Parent | on HN ]
Re:Android Design by kefs on Thursday January 12, 2012 @07:20PM (#3458585)
So, giving the user more control is a bad thing?

While I understand that users can be easily overwhelmed with a plethora of options, this one makes sense.. especially for an email app.

[ Parent | on HN ]
Re:Android Design by cuu508 on Thursday January 12, 2012 @08:02PM (#3458696)
Looks more like working around deficiency in navigation, than giving more control.

Rethink your UX, put together prototypes, user-test, and repeat. Leave configuration option as last resort. That's the approach for app that wants to "Simplify my life" and "Make me amazing".

[ Parent | on HN ]
Re:Android Design by underwater on Thursday January 12, 2012 @11:35PM (#3459211)
There are hundreds of design decisions that go into any product. Designers can't give each and every one a configuration setting, and can't know before launch which decisions will be the wrong ones.

If the back button did it's job properly then the feature would just work; you wouldn't need to manually configure it to match your mental model.

[ Parent | on HN ]