Tag Archives: indicators

Red indicators mean everything’s fine?

I was turning the lights off in the house a few nights ago and my eyes were drawn to the bright indicators coming from our new phone in the living room. Not one … not two … but three separate RED indicators were glowing and getting my attention on the main phone cradle, which doubles as an answering machine. Was the phone in trouble? Was it screaming for my help? Was it about to die or self-destruct? Nope. These three red indicators happen to be completely normal for this model of phone.

The little red line on the left is supposed to tell me that the phone is charging or is fully charged. It would cost a bit more to design and implement, but wouldn’t it make a lot more sense to use red for charging and green for fully charged? What about a slowly blinking green for charging and a solid green for fully charged? Why is the manufacturer using a red indicator for a state that the phone is going to be in for 99% of the time? Isn’t red supposed to indicate an abnormal situation or a problem to the average user?

The light on the right tells me that the answering machine function is turned ON. Again, that’s the normal mode for this device. Why red? I think green would be much more appropriate here.

The red number in the middle tells me how many messages are stored on the machine. It flashes when there is a message on the machine that we haven’t listened to. I think either red or flashing slowly is appropriate for new messages, but probably not both. Using both red and flashing is overkill in this case. And using red to tell me the number of old messages is not appropriate. Green would be nice.

I suppose after a few weeks I’ll get used to the three red indicators and the fact that they are red probably won’t even phase me anymore. But is getting used to these red indicators being normal really a good idea? I mean, won’t it cause me to give red indicators on other devices less criticality than they might deserve? As a software designer, I’ve always been taught that red indicators were only to be used for errors or problems or critical situations where the users attention needed to be drawn immediately toward a situation for awareness and/or corrective action. Who told the hardware and appliance designers that it was perfectly acceptable to use red for normal happy status indicators? Don’t these companies perform human factors studies and usability studies and ask potential users for feedback before starting mass production?

I’m stuck with these red happy indicators now because even as picky as I am, I’m not going go to the trouble of packing these phones back up and finding my sales receipt and carting these phones back to the store and then having to go to the trouble of researching to find another phone that actually uses happy colors for happy indicators. It’s just too much trouble. I’m stuck with these phones with their un-intuitive indicator colors.

Let’s quickly examine a few other fairly common electronic devices laying around my house that give me information in the form of lights and indicators:

This tuner/receiver uses a nice blue color for the main display, but it uses various red lights just to tell me about different modes that have been activated. These different modes are completely normal and should not be indicated in red, in my opinion.

I haven’t done any research on the topic, but I believe that a large percentage of digital alarm clocks today use red for their displays. Is red easier to see in the middle of the night without your glasses/contacts than blue or green? Please educate me, because I don’t understand this color choice.

We love our iRobot Roomba floor vacuum and I couldn’t be much happier with the user interface. While it’s charging, the power indicator beats like a heartbeat and changes between orange and green. When fully charged it sits happily at solid green. This is intuitive to me. The folks at iRobot have a winner.

In our computer room we have a DSL modem, a wireless router and also an Ethernet switch. Ninety nine percent of the time that I glance at these devices, all the lights are green. If I see a different color or no lights at all, then something is probably wrong.


[ photo of oven and/or toaster oven goes here]


Stove and toaster oven lights are red when the heaters are on, even though that’s the normal operation for that appliance. That okay in that case, because I want to be drawn to these lights if they are on for more than the relatively short period of time while I’m cooking. In this case, I think it’s okay to use red, since I could potentially burn my food or even burn down my house if this “normal” mode of operation stays in use for long periods of time.

I guess my whole point here is that there should be known acceptable uses and known undesirable uses of indicators, colors, etc. in the hardware industry just like we often see in the software user interface industry. Donald A. Norman, the author of the books “The Design of Everyday Things” and “The Design of Future Things” states the following in the latter book:

“Every piece of equipment has its own code for beeps, its own code for lights. A small red light visible on an appliance could mean that electric power is being applied, even though the appliance is off. Or it could mean that the unit is turned on, that it is working properly. Then again, red could signal that it is having trouble, and green could mean it is working properly. Some lights blink and flash; some change color. Different devices can use the same signals to indicate quite different things. Feedback is meaningless if it does not precisely convey a message.”

I highly recommend both of these books. They are both worth reading whether you design websites, stand-alone computer applications, portable electronic devices, cars, or space vehicles.

So please don’t use red indicators to tell me that everything is perfectly fine. I’m fairly certain the blue and green LEDs don’t cost that much more than the red ones. 🙂

Thanks for reading,
(overanalyzing our world for 38 years)

User Interface Annoyances: Indicator Buttons

As a software programmer, I feel the need to make the user happy so that they will like my product. We all just want to be loved, right? In order to make the user of my software happy, the user interface must not be annoying and the whole user experience must be positive. I personally have lots of opinions about what should and should not be done in a user interface, and I’m sure the whole world will not be totally in agreement with all of my opinions, and that’s fine. We can agree to disagree.

Today’s annoying user interface is inside the elevator in my building at work. It’s not very nice to make your floor indicators (which cannot be pressed by the user) look exactly like the floor selection buttons. (Sorry about the poor quality photos.)


Now, I consider myself a fairly sharp guy, but on the rare occasion that I actually use the elevator in my 2-story building, the indicator lights which look exactly like the floor buttons always throw me for a loop. They look like buttons that can be pressed.
The only reason I haven’t been tricked into pressing them is because they are way up high on the panel. But still, last time I was in the elevator I had to try to press them just to make sure they were not actually buttons. They’re not. But they sure look like buttons. Why would any user interface designer in their right mind design an indicator to look exactly like a button? Is this a game they play just to mess with our minds or something?

This would be even more annoying if this were done on a software user interface. But I don’t have any examples of that to post right now. Let’s just try to avoid using buttons as indicators, shall we?

Just my opinion,

Kurt (with a tip of my hat to Joel Spolsky)

User Interface Annoyances: Labeled Toggle Buttons

As a software programmer, I feel the need to make the user happy so that they will like my product. We all just want to be loved, right? In order to make the user of my software happy, the user interface must not be annoying and the whole user experience must be positive. I personally have lots of opinions about what should and should not be done in a user interface, and I’m sure the whole world will not be totally in agreement with all of my opinions, and that’s fine. We can agree to disagree.

But one thing that I think is a bad idea is to use a toggle button to turn on or off a certain feature and to put a text or image label that states the current value of the feature onto that toggle button. Was that sentence confusing? Well, so is a labeled toggle button! And what’s the last thing you want your user interface to do? Confuse the user!

.Labeled Toggle Button from PrintKey 2000

I use PrintKey 2000 as my free screen capture software. Yeah, it’s old and outdated, but it works for me and I haven’t felt the need to go out searching for a replacement. Hey, if it ain’t broke …

All of the big fat buttons across the top actually do what their label says … all except for one, that is. The button labeled “OFF” does NOT actually turn something OFF. It does just the opposite of turning something OFF. It turns something ON. It’s a toggle button for the Auto Save feature and the current state of the Auto Save feature is OFF, so when you click on the button labeled OFF, it will turn the Auto Save feature ON and change the label on the button to read ON.

So the button is telling the user the current value of the feature, not what action the button will perform when pressed. But users are used to buttons doing what their label says. The Print button prints, the Save button saves, etc. But this one button acts differently than all other buttons in the world?!? Why? This sort of user interface behavior is not intuitive to most users and should be avoided.

Solution: If the value of the feature were placed into a text field that is separate but adjacent to the toggle button and the toggle button was labeled something like “Auto Save”, that would be just fine. It might be even better if the button label were “Toggle Auto Save”, but I realize that might be too wordy. Another solution would be for features that can be toggled, to forgo buttons altogether and use checkboxes with labels instead. A checkbox labeled “Auto Save” would turn the feature on when the box is checked and vise-versa. I think most users would find that intuitive.

Just my opinion,