Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Another rule was: Design a product for the “98 percent use” case. [...] Mayer believed on every good product there should be a big button like that for the 98 percent use case, where if the user clicks it or taps it, they get a delightful, fluid, simple experience.

This is all good, but hereis the thing that many designers with great responsibilty doesn't seem to get: As much as there is one big button/search field etc, DON'T REMOVE advanced options for advanced users. Example: For a long time Google Maps on Android it would be impossible to look up a route from anywhere but where you were now. It was not only streamlined to start with current location but rather neutered so you couldn't. To add insult to injury it used to work fine before someone started their UX work :-/



> For a long time Google Maps on Android it would be impossible to look up a route from anywhere but where you were now. It was not only streamlined to start with current location but rather neutered so you couldn't.

I almost lost my mind trying to do this exact thing.


Google maps refusal to make offline reasonable has pretty much killed my use of it. You can use OSM data pre-download the whole set of countries you're driving through and not worry about poor signal / roaming charges / data use.

Or you can use Google maps and get screwed. Guess it works better if you're in the US.


Does offline not work where you are? https://support.google.com/gmm/answer/6291838?hl=en


I can't upvote you enough. This is my #1 pet peeve with modern UI/UX design. I'm perfectly fine with the "big green button" scenario where the most most common use case is the one that gets most of the visibility, but those advanced features NEED to still exist somewhere. Minimalism taken too far can and will hurt the quality of the product.


> As much as there is one big button/search field etc, DON'T REMOVE advanced options for advanced users.

I think Mayer's rule implies that. If you remove the feature entirely, you aren't designing for the 98% case, you're designing for the 100% case because the remaining 2% case is gone.

I interpret "design for the 98% case" to mean "focus on that, but don't eliminate the other 2%".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: