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

I'd also defend the text from the emptiness. In the Magnolia evoke example the text label is small while there is plenty of space around.

Also, you can go on the attack with text and make it rich! Bold / emphasising individual letters with colors to make all those visual scan easier.

Though the ultimate solution is allowing easy user choice of both to override whatever mistakes the designers made, and at an "OS level", so that a user could use a single identical icon for "Export" and avoid the mentioned per-app inconsistency. But that will have to wait until the fantasy era of UI design arrives

> We’ve spent our lives learning to recognize words instantly, while most app icons require new visual vocabulary.

Unfortunarely we haven't reached that level of magic reading skills despite spending a part of our early lives learning to... well, also not instant recognition.

> Scanning text is fundamentally easier than scanning icons. A stacked list of text requires only a one-directional scan (top-to-bottom), while icon grids demand bi-directional scanning (top-to-bottom and left-to-right).

But this is a fundamental mistake, besides the fact that icons take less space, so "efficiency" is higher, you can recognize familiar shapes/positioning without full per icon scanning



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

Search: