UI DESIGN LAB
  • Home
  • Community
  • Library
  • Knowledge
  • Docs
ZHLogin
Back to knowledge
Design Systems Page Patterns

Notification Center Pattern

Notification Center Pattern turns a frequent interface judgment into an executable constraint before generation.

notificationsinboxstatus

Design Principle

Notification centers should help users judge importance, source, handled state, and next action.

Principle Notification centers should help users judge importance, source, handled state, and next action.

Design action Group notifications by unread, priority, source, or time; each item includes object, event, time, state, and related action.

Examples Positive example: Collaboration, review, monitoring, billing, system alerts, and community activity need centralized handling. Counterexample: Every notification has only title and time.

Apply when Collaboration, review, monitoring, billing, system alerts, and community activity need centralized handling. Users need to judge state, scope, risk, or next action quickly.

Source notes Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries.

Agent Directive

Group notifications by unread, priority, source, or time; each item includes object, event, time, state, and related action.

Apply When

  • Collaboration, review, monitoring, billing, system alerts, and community activity need centralized handling.
  • Users need to judge state, scope, risk, or next action quickly.

Avoid

  • Every notification has only title and time.
  • Irrelevant structure, copy, or decoration is added only to make the UI feel richer.

Knowledge Metadata

Category
Design Systems Page Patterns
Quality
85%
Version
v1
Published
6/6/2026