The first line must stand alone when collapsed

What it is

A privacy-safe self-contained notification opening lets the title and first body text convey the safe minimum needed when truncated on a lock screen, banner, watch, or notification list: event category, critical state, and whether action is needed. Self-contained does not mean revealing a full source, person, or object. Before unlock, for sensitive content, or when previews are hidden, use a generalized but truthful state and defer detail until authorized viewing.

Why it happens

The first encounter often occurs in limited space visible to other people, and users decide whether to ignore, expand, or act from the front-loaded text. Putting critical meaning after truncation replaces judgment with suspense; forcing sensitive specifics forward exposes them to bystanders, shared devices, or companion screens. Systems may group by app, suppress the body, or speak only the title, so title, opening, and privacy level must work together rather than depend on one character count.

Studying it

Capture actual collapsed states across target operating systems, fonts, languages, grouping, and devices. Cover locked and unlocked views, preview settings, screen sharing, watches, car displays, and screen-reader speech. Ask participants to identify event category, urgency, and next step, while privacy review checks inference of identity, relationships, health, finance, or security. Include long names, repeated and stale notifications; do not validate only one mockup width.

Where it stops holding

Some lock-screen states can safely say only that an item needs attention. That is a disclosure boundary, not necessarily copy failure, but it must not be compensated with fabricated urgency or clickbait. Expanded and rich notifications may carry secondary detail, so the first line need not contain everything. Codes, health, finance, security, and private communication may require stronger redaction. Lock-screen disclosure controls belong to privacy governance; this leaf orders only the fields permitted in each view.

Applying it

• Define locked, unlocked, hidden-preview, and companion-device variants, listing the allowed source, actor, object, content, and action fields for each.
• Lead with event category, critical state, or action need; move pleasantries and promotion later. Never use “guess what happened” to force opening.
• Regress title and body under system truncation, grouping, large text, translation expansion, and screen-reader order so truncation does not alter facts or hide required risk.
• Update or retract notifications completed on another device or made stale. When synchronization is unavailable, verify current state after open before presenting the old action.

Related

• Same group: T2.08.2 State the source and the object it concerns · T2.08.3 Anxiety-inducing copy gets notifications switched off entirely
• Adjacent: O3.07.2 Pre-unlock information exposure needs to be controllable · T2.02.1 Headings must accurately preview page content
• Search terms: notification truncation · lock-screen privacy · collapsed notification