Brandon Dorn Brandon Dorn is a senior product designer at Dwell Magazine, where he focuses on prototyping, design systems, and information architecture.

Balancing information density in web development

6 min read 1686

information-density-design-usability-web-nocdn

The myth that minimalist design equates to usable design is well-documented. In designers’ attempts to create interfaces that reduce complexity, they often oversimplify content and interactions based on ideas of simplicity rather than the nuances of the content and needs of the audience.

Aesthetic simplicity is treated as the de facto standard for good design, even when dense, information-rich interfaces — despite their apparent complexity — can be clearer and more usable in many situations.

In this article, we’ll cover what information density is and how designers and developers should consider it when designing and building web and mobile applications.

What is information density?

Information density refers to the amount of informational content in an interface — “data ink,” to use Edward Tufte’s phrase — and is measured by the proportion of information to available space. Ultimately, web and mobile apps should find the right information density for a given interface in order to balance both context and design instead of only seeking surface simplicity.

On digital screens, this can include static or interactive content: text, microcopy, labels, links, buttons, controls, diagrams — anything that is instructive or usable, as opposed to purely aesthetic. Data-rich, high-density displays have an abundance of content, whereas data-thin, low-density displays are relatively spare.

Density Interfaces Comparison
Examples of low-, medium-, and high-density interfaces: Google’s search page, Google’s search results page, and the New York Times landing page.

There isn’t a universal rule for the right level of information density. The success of an interface depends largely on the extent to which the designer finds the appropriate density for a given context, content, audience, and screen size, the last of which complicates this work.

A layout that achieves an ideal level density on desktop, for example, may become overly dense on a mobile screen, whereas a mobile layout can feel overly simplistic on desktop. Usability and comprehension issues can arise at either end of the spectrum.

Rather than arbitrarily simplifying seemingly “busy” designs, a designer’s task is to artfully manage complexity. Here are some principles and tips to help product teams find ideal information density when working with rich, responsive interfaces.

Managing information density for app design

1. Create context by adding detail

Interface design focuses on creating context to help people understand the task and content at hand. While the legacy of people like Dieter Rams (“My intention is to omit every unneeded element”) and John Maeda (“The simplest way to achieve simplicity is through thoughtful reduction. When in doubt, just remove”) have conditioned designers to remove superfluous design elements, the emphasis on subtraction can be at the expense of effective context creation, which requires adding detail.

Less emphasized are Rams’ and Maeda’s exhortations to “make a product understandable” and “be careful of what you remove [from a design],” respectively.

We made a custom demo for .
No really. Click here to check it out.

When designing interfaces at low fidelity, I find it helpful to incrementally incorporate high-fidelity content — including, for example, microcopy, contextual help text, representative body copy, and key data, etc.

Considering representative content from the start requires designers to make decisions about visual hierarchy while working through the core elements of an interaction.

Consider what questions might a user be asking of this interface. What relevant information can I incorporate to help them answer those without leaving their context? How can I adjust the interaction to make it more understandable to first-time users and efficient for repeat users?

High Fidelity Content With Low Fidelity Design
An example of how high-fidelity content can be used in low-fidelity design work.

Like filling in the outlines of a coloring book drawing, I treat wireframes as the conceptual boundaries for the final design; as I work in higher fidelity, I’m introducing aesthetic refinements and incorporating detail as I spend more time with the design and put it through usability tests.

2. Maintain consistent density across screen sizes

The mobile-first design movement was in part a response to poorly handled information density — full desktop websites shoehorned into mobile viewport widths, resulting in unreadably small content and awkward panning and zooming.

Yet as designers learned to prioritize essential elements for small screens and work in fluid grid systems, layouts optimized for mobile viewing risked becoming vacant on desktop and monitor widths.

Interface with Better Density on Mobile
An example of an interface that achieves better density on mobile viewport widths than desktop widths.

Beyond creating patterns for responsive content behavior (defining stacking rules, for example), it can be helpful to consider ways to maintain similar levels of information density across the range of screen sizes — thus, the creation of responsive design in web development.

Mobile interfaces don’t need to be sparse to be usable or attractive. A good example of this can be seen in my colleague Kevin’s article about responsive screen heights. He argues that standard content stacking conventions lead to unnecessarily long pages on smaller devices. His explorations show how density can be increased even on marketing pages to good effect.

Exploring Density Mobile Widths
Explorations for improving density for a marketing page at mobile widths.

Some interfaces are too complex to effectively scale down, requiring significant reworking of layouts, navigation structure, and interactions.

It’s one reason why information-rich products with high levels of interactivity like Airtable create an entirely separate mobile application for showing the same data that users can access on desktop.

In the screenshots below, the browser viewport (1280px × 694px) is about 3.5x larger than the mobile viewport (375px × 667px), and shows 63 table cells compared to the mobile viewport’s 12 cells.

Were the mobile viewport able to display 6 more cells, it would more or less match the proportional density of the desktop view. All things considered, Airtable effectively handles each viewport density well.

Airtable density
An example of how Airtable preserves density across mobile and desktop viewport widths.

3. Use minimum text and touch target sizes as boundaries

Although content — not aesthetic — considerations should prompt designers to work at higher density levels, accessibility standards can serve as guides for preventing interfaces from becoming overly dense.

Even though minimum font size hasn’t been defined for the web (readability depends on the alphabet, contrast ratio, and user’s vision), it’s generally agreed that somewhere around 12px is a good minimum for interface text.

Another helpful reference is mobile touch target size, which Google’s Material Design spec defines as at least 48px square. (It should be noted that the visual representation of the linked element can be smaller than 48px square, but the effective clickable area should be at least that size).

The Material Design density guidelines give helpful examples for maintaining accessibility when introducing higher levels of density.

Material Design Mobile Touch Targets
Material Design’s recommendations for mobile touch targets.

4. Conduct comprehension design testing

The purpose of increasing density is to help people understand and interact with the content, and the best way to validate that is through usability and comprehension testing — especially on mobile devices.

Apart from standard task usability measures, product teams might keep an eye out for a few things when testing dense interfaces:

  • How easily are users able to move between summary and detail views of information? Do they maintain a sense of context when they are moving from one level to another? Experiment with different approaches for representing levels of abstraction (like Jeff Dance’s “vertical” and “layered” concepts) to find the most effective way to invite exploration and understanding.
  • Are users scrolling where they’re expected to? Mike Bostock lists a number of rules for scrolling interactive, data-dense graphics, and visual narratives, pointing out that scrolling (instead of clicking or tabbing) is an effortless behavior so long as visitors are aware of additional content outside of the viewport (and so long as scroll interactions behave as users expect).
  • Does the information displayed aid users’ cognitive effort? A challenge of representing complex information on smaller screen sizes is the burden put on users’ memory as they navigate through the content. As Raluca Badiu puts it, “The capacity of the human–device communication channel is naturally limited by the user’s working memory. If the site or an application asks the user to learn too much new information…often the user will reach an impasse where his working memory will not have that information anymore and he will need to go search for it.” Smaller device screens inherently provide a narrower view of the content, requiring users to piece together information viewed sequentially that they might otherwise see in a single view on desktop. What types of contextual help or responsive layout changes might aid this sense-making on narrower screens?
  • How do users perceive the interface’s density before and after using it? Perceptions of density are subjective, varying across cultures, tech-savviness, cognitive ability, and age. Asking people about their impressions of an interface’s density at first glance and after performing a number of tasks can defuse concerns about a product being overly complex. If people perceive the app as complicated at first and after getting familiar with it, additional revision is likely needed.

Conclusion

The aversion to high-density interfaces is largely an aversion to poorly designed dense interfaces. In his classic The Elements of User Experience, Jesse James Garrett notes that, “When people comment that a design is ‘busy’ or ‘cluttered,’ they’re really reacting to the fact that the design doesn’t lead them smoothly around the page.” The designer has failed to establish clear information and visual hierarchy.

The issue isn’t with the content itself, but how it’s displayed. By reframing complexity as a design problem, and not a content problem, more information that is thoughtfully displayed makes for a more informed, clearer interaction.

Information Dense Interfaces
Examples of information-dense interfaces used by wide audiences every day.

As designers recognize the usability of everyday, information-dense applications like Airtable, Spotify, and Google Maps, they should seek the best level of density rather than the minimal level, seeking the elegance that can result from well-considered displays of complex content.

: Full visibility into your web apps

LogRocket is a frontend application monitoring solution that lets you replay problems as if they happened in your own browser. Instead of guessing why errors happen, or asking users for screenshots and log dumps, LogRocket lets you replay the session to quickly understand what went wrong. It works perfectly with any app, regardless of framework, and has plugins to log additional context from Redux, Vuex, and @ngrx/store.

In addition to logging Redux actions and state, LogRocket records console logs, JavaScript errors, stacktraces, network requests/responses with headers + bodies, browser metadata, and custom logs. It also instruments the DOM to record the HTML and CSS on the page, recreating pixel-perfect videos of even the most complex single-page apps.

.
Brandon Dorn Brandon Dorn is a senior product designer at Dwell Magazine, where he focuses on prototyping, design systems, and information architecture.

Leave a Reply