The Dilemma of Icons
fairpixelsco.medium.com
fairpixelsco.medium.com
This is connected to another UX trend I don't understand of dumbing down interfaces because too many options are "too distracting." Probably not the best forum to ask this but has anyone ever stopped using an app because they got distracted by the menu?
Perhaps it takes a certain kind of person to decipher icons as easily as text. But of course, I don't know all of them already, and so frequently I just go on a journey of discovery by tapping random buttons to see what they do. I would say that's not an efficient way to learn a UI, but what else to do? Documentation sucks!
Lastly, the real curse of icons is forcing support people to attempt to describe, in our native tongue, the appearance of a thing, rather than its plain name. It was deceptively easy to guide a newbie by saying "now click open, then save, now go home" but nobody is going to know what the "hamburger" or "floppy disk" or "share" icons look like, so the verbal mode of communication has been hampered significantly.
Sadly, this is bucking the trend. More and more designers are thinking mobile and trying to cram everything into very confined spaces.
My personal pet peeve are washing instruction icons. Yes it is a simple easy to learn consistent system. None of which helps me when I am at the machine trying to decide what the hell this squiggle is trying to tell me. If I were smarter I would tape a decode sheet to my machine.
the koan is.
A picture is worth 10K words -- but only those to describe the picture. Hardly any sets of 10K words can be adequately described with pictures.
[1] https://www.parkersdrycleaners.com/2011/05/care-label-tags/
Note: No endorsement of, or affiliation with Parker's Dry Cleaners.
I don't want a hippy brand to write a 50 lines poem instead. Nor do I want "woogie boogie wash only" jargonning that felt cute to the copy righter, nor do I want to try to understand the Indian instructions.
That was never true. The icon for "print" remains something you have to learn. Even the trash can icon had to be explained before it became "intuitive".
My chrome browser has a row of icons across the top. Only the <- and -> icons are reasonably intuitive.
You can’t make an “intuitive interface”. What you can make is an interface that is familiar, and consistent, which means people can reasonably anticipate what doing something they haven’t done before will do.
(Good interfaces should also allow for mistake recovery - eg by supporting universal undo - which is something everyone seems to have forgotten)
Even arrows are not uniformly perceived across cultures as showing direction (although you can safely assume most anyone who lives in 21st century globalized modern society will have learned to decode arrows fairly early in life).
The old quote goes that “the only intuitive interface is the nipple; after that it’s all learned” - but that quote was clearly by someone who was never around newborns, because lots of newborns have to be guided to breastfeeding.
I've also seen telephone icons that are an outline of a telephone that hasn't been seen since the 1950s. An outline of a modern phone isn't very distinctive.
Legend has it that the original Mac trash can icon looked a lot like a traditional British mailbox.
Non-hilarity ensued.
This is before you even get to the dumbness that ensues by the UX designers getting confused to whether a button that is a toggle should have the icon representing the current state, or the state that clicking it will cause to happen, like every other button in existence. (Think of the Mute button in every videoconferencing app -- at least Zoom still has a text label on it though!)
1. The gas pump goes on the right side of the car?
2. The gas pump goes on the left side of the car, and the hose goes to the right into the fuel inlet?
But designers pretty much insist on it, these days, and fun, ensues (and sometimes, F*kN sues).
I have found the best UI, is UI that gets out of the way, and doesn't call attention to itself. There's a reason that waitstaff usually wear black.
An example: I designed this really clever Swift UIKit widget (not SwiftUI)[0].
I keep trying to use it in my projects, and keep removing it, because it's too "in your face."
As with written characters, meaning drifts over time. I don't know if it's as much a 'dilemma' as an intrinsic aspect of existence.
I think he means audio players, but it's possible they's never seen one of the old audio tape machines...
Random example: https://www.techonthenet.com/excel/questions/neg_time_calcs....
The Visual Studio 2010 Image Library is a pinnacle example of that era: https://learn.microsoft.com/en-us/previous-versions/visualst...
It should be noted that these need to be viewed with 1:1 pixels on a non-hi-DPI display to be truly appreciated.
That also means icons don’t have to make sense visually, they just need to be recognised and distinguished.
Text is for when you have time or no idea, icons are for when you have to decide quick and you understand what you are doing.
The icons really aren’t going to matter as much. And I’d argue they’d probably be better off replaced by text labels. Imagine a new operator in a stressful situation being guided eg on the phone - how would you describe to them which of the 2 buttons with a center arrow with a curve to their right they should press, for the control panel at 4:31? You’ll end up saying “the center left/right button”, or “the one above the green P button” because those icons are pretty hard to distinguish.
Swap the icons between 2 controls one day, and watch even the most skilled operator make mistakes.
This is, for me, categorically untrue, it's quite the opposite. I am sure it must vary from person to person. I find myself wondering whether people tolerate or like icons-only because they would find the actual reading of an array of text buttons fatiguing. I'm not better than someone who finds reading more time consuming or difficult than I do, but I do kind of resent that UIs appear to be designed to cater to the less literate, because of how slow it is for me to pick the correct icon out of 7 very similar ones.
It's especially bad because these should just be preferences. Give me text and lose the icons altogether. Others should be free to have icons.
For example the cloud "obviously" means something on the internet, something like online storage, and you can derive a lot of "self explanatory" icons from there. But what about those who don't understand it?
Funnily enough, I once saw a cloud icon on a piece of software, I thing it was mapping software, I instantly though about something about the internet. It took me a bit of time to realize it was for the weather, I mean, actual clouds.
So said the ancient Egyptian scribes, and yet they wrote a Rosetta Stone.
And it's not the only case where something similar happens:
https://ux.stackexchange.com/questions/90445/mail-icon-is-th...
In the words of Eleanor Shellstrop, "No, it's annoying, and I'm right not to."
Not everything -- not even close to everything -- should be an icon at all.
Looking up at my browser toolbar, I can count several icons that are so abstract that I can't remember what they do without wasting about 4 seconds on each button waiting for a tooltip. Some "UX Designer" thought it was important to not label icons, because of either aesthetic "elegance" or space worries, and as a result they've wasted a 3-inch strip of space with 4 icons that I'll never use. If they'd used text or labeled-icon buttons, they could have fit the top 2 functions. Same situation but even more intense with VS Code. So fun to teach someone how to use this by speaking to them. "Click the button with the three tiny circles connected by lines." "In the Find window, click the button with three uneven horizontal lines." (Obviously that conveys "Find in selection" right? Much better than those 3 words with a checkbox!) Or in that same UI, how about "Letters 'ab' relaxing in a boat made of a knocked-over square bracket" icon?
I don't get it. This absolute trash style of UI wasn't needed in order for us to get advanced and detailed tasks done on 9" 512x384 4:3 screens. I have a 4K screen and plenty of space and every desktop app seems to think the most important thing is squeezing its entire UI into a tiny strip or floating bar.
Now your second toolbar is probably hidden by some hover or keyboard action (in my browser it is reviled by a single press of my left alt key) it is all text and has numerous categories such as view, bookmarks, help, tools, etc. inside these categories there are functions such as copy, synced tabs, troubleshoot, etc. (mine is actually in Icelandic and many of those words I’m seeing for the first time and have no clue what they mean).
If your app has only a few functions putting the correct icon next to the function label can help you navigate to your desired function more easily. If your app has a lot of functions (like your browser, or a document processor) all these icons will be an overkill, so you only design an icon for the most essential/most used functions (back, zoom in, boldface, undo, etc.). If loading a language model is an essential feature in your app, which is often performed, it may help users to have an icon next to the label (and sometimes even in place of the label if the label is complicated). Personally for “load language model” I probably would just use the upload icon (commonly an arrow pointing upwards from a bucket).
There's a reason so few modern languages are pictographic.
Apparently, the fear is that some pre-contact tribe in the Amazon rainforest would not understand the labels on a car's controls.
I think that one is meant to be a ship.
Wrong. The Xerox Star broke the ground for icons. Dave Smith was the person who came up with the concept.