While exploring ideas for the future of Sifter, we started with the most frequently accessed page on Sifter, the issue listing page. It currently gets the job done, but it leaves a lot to be desired. While we're not making any promises about what it will ultimately end up looking like, it's time to begin sharing our vision of where it's going.
Conceptually, there are two major areas of the page. One is the navigation and structure. The second, and our focus for the near future, is the data. How do you efficiently display the data in a useful and minimal manner? There's been an incredible amount of iteration, but the common theme has been agonizing over pixels. We wanted to remove any and all unnecessary pixels in order to create a simple and focused interface.
None of this is rocket science. It's simply a matter of ruthlessly cutting unnecessary pixels. One of favorite principles, and I'm sure the favorite of countless others as well, comes from Edward Tufte. It's the principle of the smallest effective difference.
Make all visual distinctions as subtle as possible, but still clear and effective.
It's a recurring theme for me, and one of the simplest and most useful principles that I can think of with regards to information design. WIthout further ado, let's dig into how we can apply this principle to zebra striping. Our solution might not work in every context, but we think it's a perfect fit for Sifter.
Whether using tables or some other method, it's important to add a horizontal visual element to assist the scanning of rows. Traditionally, you'll see zebra striping used to alternate every other row color. In many contexts, that works, but for me, it makes things too busy and certainly requires too many pixels.
Zebra striping can be busy and visually overwhelming.
A simpler solution would be to only use a single horizontal line where every other line is a different shade or color.
We can minimize the noise while maintaining the same level of utility by simply using alternating color dividers.
For some, that's enough of an improvement to stop there, this is just the first step. We could minimize the number of darker rows by only using a dark row every third time. This would still give each adjacent a row a different signature.
We can further reduce the visual weight by only using dark rows in every 3rd line.
Being obsessive about this kind of thing, though, there's an even simpler solution that would allow us to remove 60% of the dividers entirely. By simply using a line every 3rd row and skipping the other lines, you have just enough information to assist with the scanning without adding too the visual overhead of row colors.
Finally, we could go a step further and only use lines every 3rd row to achieve equivalent utility and significantly less visual noise.
And, for easy comparison, a side-by-side of the before and after.
A quick side-by-side comparison shows the improvement both in a reduction of colored pixels and overall weight.
Much of design, particularly information design, isn't complex at all. It's just a matter of editing your visual elements. Remove things that aren't necessary. However, it's important to remember that "necessary" is relative. In some cases, excessive and/or intricate design is necessary to achieve the feeling and emotion you want. The important part is knowing when to say when.
We built a simple bug and issue tracker named Sifter and we blog about it when we're not working on it. We think it’s a great way to get feedback and keep everyone updated on our status.
Grab our feedWe'll only send emails for significant product announcements, and those happen every couple of months at most. Of course, we won't give away or sell your e-mail address either.
Comments
The design is certainly much slimmer, but since there is only a separator every third row it feels like the items are grouped together for some functional or organizational purpose, instead of just as a visual aid. I keep looking for a commonality amongst the items in the same "group".
Chris - That's certainly a valid point. However, I think part of the reason for that is that you're only looking at a small portion of the page rather than seeing the entire thing.
However, even if it isn't obvious in the large context, I think the drawback of someone occasionally looking for meaning is much less significant than the visual noise created by a dizzying array of lines. The former would only be a problem from time to time, if at all, while the latter would be a persistent problem 100% of the time.
Interesting idea. The result is much cleaner, but I could also it see it leading to some confusion. The lines now look like they divide the rows into groups. My first reaction when looking at versions 2 & 3 was to try and puzzle out the rules were being used to make certain lines darker than others (without reading the descriptions, I didn't notice the pattern was based on # of rows).
FWIW, I had the same reaction as Chris and Jackson. The design is cleaner and more open; however, I found myself instinctively trying to figure out how each group of three related to each other. I admire that you're trying something new and reserve final judgement until I can see the full design in context.
Have you tried to see how it looks if the text to the side of the status labels line up? I suppose it would then become too tempting to turn the whole thing into a table which would then detract from the "conversation" style feel of it..
I agree with the above commenters. I love the amount of thought you put into all of these decisions, and I agree that the zebra striping can be somewhat overwhelming. But it seems like you may be missing the forest through the trees here. There are fewer pixels in the new version than in the striped version, but I think there's actually MORE noise -- because now, instead of just seeing colors that are clearly to distinguish rows, users are seeing lines that seem to indicate some significant difference where there is none. This really doesn't seem to accomplish the "simple and effective" purpose.
Why not use the light-colored line under every row? Less distraction than the zebra striping, but more clear than the current iteration.
Le Roux - I have indeed. I'm actually planning on getting in the decision behind how the rows are laid out in a future blog post.
The simple version is that I really wanted to move away from a tabular arrangement because it puts the emphasis on the columns over the rows. I really want the issues to feel like atomic items in and of themselves rather than breaking each issue up into pieces.
David - While I was worried about that when I first started designing it, I think the combination of the fact that reading a blog post critically analyzing the approach combined with the lack of context that comes from having all of the other page elements visible is tainting the perception.
I'll definitely be mindful of the possibility, and of course nothing's written in stone, but I really do believe that in the context of a page full of issues this works well. With the rest of the page, these lines are much more subtle and without explicitly drawing attention to them, I believe that they'll simply exist and serve their purpose without being a significant focus of attention like they clearly are in this post.
Worst case scenario, we go back a step or two and use more lines, but the process of elimination should still be valid for others.