Dismissed notices must be replayable in history

What it is

The shade is a short-lived surface: swipe, timeout, or a newer arrival knocks a card out. A history list lets those vanished items be opened again—not by pinning them in the shade forever, but by offering searchable replay. A swipe is often "not now," not "void." Without replay, a temporary clear becomes permanent loss.

This is whether something can be found after it leaves the shade. It is not the do-not-disturb contract that suppression needs a landing place when the mode ends, and not collapsing like items into a shade summary.

Why it happens

Arrival and the window in which someone can handle it are often offset: driving, a meeting, a swipe in a pocket. The shade is built for a glance now—small capacity, short life. History splits now from later: the shade owns interrupts and short-term to-dos; history owns memory. Without that memory, people hope they read it at the time, or open every plausible app—which turns retrieval into guessing the app.

Replay must keep an object link, not only the line of copy. Copy goes stale ("your car has arrived"); the tap should land on the object as it was, and if the object's state has moved, it should still be clear that this was that notice.

Studying it

Have people swipe away several notices during a busy task and retrieve them later. Compare system history, in-app inboxes only, and neither.

Independent variables: where the history sits, retention, searchability, whether object links still resolve. Dependent variables: retrieval rate, time to retrieve, wrong-app attempts, repeat app opens caused by not finding the item.

Lab "please remember these" overstates recall without history. Insert an unrelated task first. Dismiss rate is not successful cleanup—dismiss may be deferral.

Where it stops holding

Codes, ephemeral messages, and encrypted threads may forbid persisting bodies; at least leave source, time, and "there was one, open the app." Law or enterprise policy may demand longer or shorter retention; history is not a license for a permanent log. On shared devices history is itself a leak and should clear on lock or sign-out.

Applying it

• Provide system or in-app notification history; dismissed, timed-out, and crowded-out items enter by default and stay for at least several days.
• Each row should open the original object; if it is gone, mark expired rather than a dead link.
• Put the entrance where people look for "that one just now": foot of the shade, system settings, the app inbox—not an about page.
• Verify by having someone swipe three notices from different apps, do something else for ten minutes, and retrieve them. If they cannot, or must guess the app, history is not doing replay.

Related

• Within the group: H5.11.2 History must keep original timestamps, not reorder by time of viewing · H5.11.3 Items held during do not disturb must merge into history, not vanish · H5.11.4 Missing history drives repeated checking for updates
• Adjacent: H5.03 Do not disturb and focus · H5.04 Notification bundling · H5.06 Actionable notifications
• Search terms: notification history · replay · dismiss is not delete