K2.06.4hover progressive disclosuredesignresearch

Hover can progressively reveal secondary information so the first view is not crowded

Aliases: uncrowded first view · hover secondary actions · layered disclosure

What it is

Not every hint and secondary action in a desktop window has to be present at first glance. Progressive disclosure through hover: primary-path controls and text stay resident; secondary hints, extra actions, and supplementary fields wait until the pointer asks about that region. The first screen can stay sparse without deleting capability.

It is a crowding problem, not a commitment-preview problem. Preview asks what would happen on click. This asks which things never needed to occupy space on arrival.

Why it happens

Desktop has many pixels and not much attention. Density at first glance decides whether the window can be read as one picture. Parking edit, delete, share, timestamp, and permission on every row turns the list into a wall of tools and pushes the object out of the schema. Hover postpones those marks from “window opened” to “pointer entered this row,” so the first glance keeps the objects. Progressive disclosure is layered reveal; desktop hover is the cheapest layer, because it spends no click and opens no extra page.

The layers have to be right. What is postponed must actually be secondary: the object can still be identified, the primary path still finished, without it. If price, unread, error, or the primary action is also postponed, the sparse first glance is fake—the cues the task needs have been hidden. That is missing persistent cues, not successful progressive disclosure. The opposite of crowding is a sparse primary view, not an empty one.

Studying it

Run the same task at two densities: secondary actions always visible, versus secondary actions only on hover. Measure how many primary objects can be identified at first glance, time to the primary action, time to a secondary action, judged crowding. Independent variables: secondary information resident versus hover-revealed, number of secondary actions per row. Dependent variables: primary-path time, secondary-path time, crowding rating, times a secondary action is taken as nonexistent.

Lab prompts that say “find delete on every row” punish progressive disclosure; the primary task should be identifying and opening objects, with secondary tasks measured separately.

Where it stops holding

Expert workstations (an editing timeline, a trading blotter) treat density itself as a resource; progressive disclosure hides what the expert is using. Touch has no free postpone, so a cross-form-factor product must move secondary information to resident chrome or a tap, and cannot expect the same sparse first screen. Print, projection, and screenshots have no pointer; the hover layer will not appear, so a view meant to be shared has to print what matters on the resident layer. Screen readers never reach this postpone either.

Applying it

  • List every element visible at first glance and mark it “required on the primary path / secondary.” Only the secondary set may go to hover; primary-path items stay resident.
  • Let hover reveal extra actions on a row, not the object’s identity (name, status, error).
  • Verify with a screenshot that has no pointer hovering. Someone new to the UI should be able to say what the primary objects are and where the primary action sits. Slide the pointer down a row: secondary actions may then appear. If the screenshot already cannot show the primary object, progressive disclosure failed as crowding; if it cannot show an error or a price the task needs, the wrong layer was postponed.

Related

  • Within the group: K2.06.1 Hover allows preview and hints without commitment · K2.06.2 Hover-dependent designs cannot migrate to touch · K2.06.3 A product that spans form factors needs two schemes · K2.06.5 Hover delay must filter pass-through mouse movement · K2.06.6 Functions triggered only on hover are undiscoverable to keyboards and screen readers · K2.06.7 If hover-state information is indispensable, the interface is missing persistent cues
  • Adjacent: D1.05 Hover feedback · F2.11 Fluid and adaptive layout
  • Search terms: progressive disclosure · hover secondary actions · uncrowded first view

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/K2.06.4