Scroll to explore the choreography

Information density isn't static—it's choreographed. The right amount of detail at the wrong time is noise. The wrong amount at the right time is frustration. Great interfaces understand when to surface complexity, not just how much to show.

The same weather data can appear as "73°" or as a full hourly forecast with humidity, wind, and precipitation probability. Which one should the system show? The answer isn't about the data—it's about the moment.

When you're walking, glanceable wins. When you're planning, detail wins. The system must read context and adapt density in real-time, making transitions feel inevitable rather than jarring.

01

Context Adaptation

Walking and sitting create fundamentally different cognitive contexts. When you're moving, attention is divided—the interface competes with navigation, obstacles, other people. Detailed information becomes noise.

When you're stationary, attention capacity expands. The same detail that was overwhelming becomes useful. The interface should breathe with your movement—expanding when you stop, contracting when you go.

Same data, different presentation. Context determines the correct density.

The visualization shows this relationship directly: as velocity decreases, density increases. The weather card expands, revealing layers of information that were always there but hidden until the moment was right.

02

The 800ms Dance

A good density transition takes approximately 800 milliseconds from signal detection to fully surfaced detail. The sequence is precise:

T+0ms: User begins to slow down. Velocity change detected.

T+200ms: System confirms intentional stop vs momentary pause.

T+350ms: UI begins expansion transition.

T+750ms: Transition completes, details fully visible.

T+800ms: User is stationary, reading comfortably.

Feels instant. Feels like the system read your mind. It didn't—it read your behavior and timed the response perfectly.

03

When Timing Fails

Density timing failures are immediately obvious. They create friction where flow should exist. The same interface becomes frustrating through mistiming alone:

Walking + Detailed
Full email preview while crossing street. Too much information, can't process safely.
Stopped + Minimal
Just "Turn left" when parked and lost. Need the full map, alternatives, context.
Focused + Interrupting
Notification preview during deep work. Wrong timing entirely, regardless of density.
Quick glance + Full calendar
Week view when checking "what's next?" Overwhelming for a simple question.

These aren't design failures in isolation—they're timing failures. The information was correct. The presentation was correct. The moment was wrong.

Same interface, wrong moment = failure. The when matters as much as the what.

04

Rise and Settle

This is the heart of ambient computing. Surfaces rise when relevant. Details emerge when needed. Complexity settles when you're done. The interface breathes with you.

The pattern connects to the Latent Graph: behavioral prediction tells the system what you'll likely need. Density timing tells the system when to show it. Together, they enable anticipation.

Example: The system knows you approach the coffee shop at 5:47pm on Tuesdays (from the latent graph). The loyalty card surfaces at T-10 seconds (from density timing). Not after you arrive—before. Anticipation, not reaction.

Traditional approach: Arrive → open app → find loyalty card. Too late, already in line.

Timed approach: Walking toward shop → card rises automatically → ready when needed.

The difference is subtle but profound. One requires conscious effort. The other feels like the system understood your intent. Both show the same card—timing creates the magic.

The Interface That Breathes

We've been designing interfaces as if context is static. It's not. You're walking, then stopped. Focused, then distracted. Rushing, then idle. The interface that works in all these states isn't showing less—it's showing the right amount at the right time.

Density timing transforms static interfaces into living ones. The weather widget that shows "73°" as you walk past and expands to a full forecast when you pause. The message that appears as a name while driving and reveals its preview when you park. The calendar that surfaces your next meeting and dissolves when it ends.

This isn't about hiding information—it's about revealing it at the moment of relevance. The data exists at all density levels simultaneously. The system's job is to choose which level to surface, based on who you are, what you're doing, and when you need it.

Great interfaces don't fight for attention. They rise when you need them and settle when you don't. They breathe with your rhythm. And when they get the timing right, they become invisible—which is exactly what good design should be.