In-App Notification Center
An in-app notification center keeps useful updates in one place. Each item shows what changed, when, and whether it is unread.
Another example
A teammate mentions Maya in a comment. Maya can read it now or return from the unread list later.
Main parts
- 01Unread count
- 02Notification item
- 03Source and time
- 04Destination link
- 05Preference controls
Use it when
Use it when important product updates must remain findable after a banner disappears.
Do not use it when
Do not repeat the same event many times or expose private details. Give people notification controls.
Name used in code
event + recipient + unread state + dedupe + deep link + preferences Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use In-App Notification Center to solve this user need without losing the current context. User context: A teammate mentions Maya in a comment. Maya can read it now or return from the unread list later. Recommended pattern: In-App Notification Center. Why it fits: Use it when important product updates must remain findable after a banner disappears. Do not use it when: Do not repeat the same event many times or expose private details. Give people notification controls. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of In-App Notification Center. Definition: An in-app notification center keeps useful updates in one place. Each item shows what changed, when, and whether it is unread. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.