Live data from Hacker News

Stop using icons in data tables

medium.com

61–66 of 66 posts

Re: Stop using icons in data tables

#61
post #5

> When we pack high-density information into a data table or a complex dashboard we are increasing the visual entropy of the entire system. Forcing the brain to decode intricate, non-universal shapes in a tiny 16-pixel footprint, creates a “cognitive tax” that users pay en masse every time they scan the table. What if it's an icon with a simple shape? How does that compare to noising up the table with long phrases an…

Right, this article overlooks the difference between a first encounter and regular encounters. The concise representation pays off when you do learn it, as long as it's executed well. And I'm fine with a bit of cognitive exploration to figure out a green check and red X scheme rather than see a whole table column filled up with words like "active" and "inactive". The former allows more columns on screen at once. Hori…

I agree that certain icons that are common parlance can increase cognition ( vs. x). However I think expanding a users icon lexicon and forcing memorization can actually harm cognitive experience.

Our users are context switching across dozens if not hundreds of digital experiences a day. Forcing memory recall is a tax. The question is always "whats the ROI?"

IMO color and words go just as far as an icon without relying on net new visual language.

As per your comment on horizontal scrolling, I couldn't agree more. Horizontal scrolling is booty. However, depending on the job to be done you can avoid overly wide tables with customizable columns, expandable rows, hover states, and strategic truncation.

I certainly would prefer those strategies over relying on a unique icon language that isn't part of the dozen or so immediately recognizable icon schemas already familiar to users.

Re: Stop using icons in data tables

#62

Stop blogging on medium. I start to read your post and as I'm scrolling down the page, I get a full-page modal nagging me to subscribe. Why should I listen to anything you have to say about user experience?

Valid point. Should I stand up my own blog or should I use a different platform? What recommendations do you have?

Re: Stop using icons in data tables

#63
post #60

I literally can't tell what the author is arguing against or for. All the example table images seem fine, and have no captions saying whether they're supposed to be examples of good usage or bad usage. So either I have no idea what "bad" examples of icon usage are because the author doesn't show any, or the author thinks some or all of them are bad when, to me, the icon+text+color examples seem great (and one figure…

Hey, author here, I'll attempt to clarify. In a data grid or table the relative cognitive load of the page is already very high. Adding iconography to the table body content is often unnecessary and increases visual noise, processing requirements, and generally reduces readability/scanability. I've always felt that icons in this context are a risk or liability instead of a strength. I decided to info dump my findings…

I think you need to show examples of this bad usage, then.

Your first image has zero icons in the rows. It has album covers but those aren't icons.

Your second and third images show very usage that combines text, color, and relatively standard icons like checkmarks, X's, or in-progress. These are good and if you're trying to suggest these reduce readability, scannability, or add noise, then I'm frankly baffled.

Your third image also shows profile images, but again those are not icons.

So what are you arguing against? I can't ever remember coming across icons in a datagrid that "added to the relative cognitive load". And if you're arguing against checkmarks or X's, I don't think your arguments hold up.

But even with "real" icons -- like, I've seen icons to show if a software package is for Windows or Mac or Linux. If a row is a TV show or a movie. If it's one file or an archive. If there's a PDF file download attached. An alarm icon for something past due. But these all seem totally fine and helpful. They're generally linked to a major feature of the platform that everybody understands, and help scannability.

Without clear examples of what you're arguing against, I'm frankly completely lost.

Re: Stop using icons in data tables

#64
post #62

Stop blogging on medium. I start to read your post and as I'm scrolling down the page, I get a full-page modal nagging me to subscribe. Why should I listen to anything you have to say about user experience?

Valid point. Should I stand up my own blog or should I use a different platform? What recommendations do you have?

No specific recommendations, sorry. Thanks for taking the feedback seriously, though, and good luck with finding a more reader-friendly platform.

Re: Stop using icons in data tables

#65
post #38

Earlier quoted context omitted.

> But graphical UIs are mature and we all need to acquire a vocabulary for these, so that information is conveyed across national and linguistic barriers. Or we could just translate the text? Colors and pictures aren’t exactly free of cultural baggage, either.

yes, e.g. the version of Windows 3.x and accompanying office suite that I used as a child had German words next to the icons. The idea of labeling a pictogram with text isn't a concept that suddenly breaks when using a language other than English. > Colors and pictures aren’t exactly free of cultural baggage, either. I remember being really confused that I had to click on a picture of a frying pan for "search".

So were you able to learn the skeumorphism eventually and equate the operation with the frying pan?

If I were in E.U. I would be afraid of needing to learn enough of 2 dozen assorted languages vs. learning an icon interface once. It would seem that human languages are not as inclusive or universal as icons.

You can do all the l10n you want, but who translates all of them and keeps current?

Re: Stop using icons in data tables

#66
post #60

I literally can't tell what the author is arguing against or for. All the example table images seem fine, and have no captions saying whether they're supposed to be examples of good usage or bad usage. So either I have no idea what "bad" examples of icon usage are because the author doesn't show any, or the author thinks some or all of them are bad when, to me, the icon+text+color examples seem great (and one figure…

Hey, author here, I'll attempt to clarify. In a data grid or table the relative cognitive load of the page is already very high. Adding iconography to the table body content is often unnecessary and increases visual noise, processing requirements, and generally reduces readability/scanability. I've always felt that icons in this context are a risk or liability instead of a strength. I decided to info dump my findings…

I agree that your screenshots doesn't make any sense in relation with the content of your text. It's like image randomly spread along the text without no meaningful relation. So much that I was wondering if it was not an AI generated article or partially.

Everyone would expect that you show example of good and bad UX for each point that you are making.

Making me see confirm by myself with example that doing X is clearly looking nicer to understand than doing Y.

Post reply on HN