NotificationCenter
An inbox of what happened: a bell key with the unread count, opening a panel of notifications as Items, newest first, each with an LED lit while unread. Opening one marks it read; "Mark all read" clears them. Where a toast goes after it's gone.
Feel A small bell with a lit number on it; open it and the unread ones glow.
Preview
Or let the agent fetch it: get_component("notification-center") on the Echo MCP server.
Installation
First time? Run npx echo-ui-cli init once — it sets the project up, and add refuses to run before it.
At a glance
- Version
- 0.3.0
- Weight
- 3.4 KB · 73.0 KB with what it imports · 3.6 KB of CSS (minified and gzipped; React not counted)
- Needs
- hardware-button (Echo, brought with it), popover (Echo, brought with it), count-badge (Echo, brought with it), item (Echo, brought with it)
- Keyboard
- The panel is a titled Popover; focus moves into it and Escape returns to the bell.
- Reduced motion
- The panel appears without blooming (Popover's rule).
Usage
import { NotificationCenter } from "@/echo/notification-center";
<NotificationCenter notifications={items} onReadAll={markAllRead} />Composition
NotificationCenter → a HardwareButton trigger with a CountBadge, a Popover with a list of Items
Examples
In a top bar
The count is on the bell and in its name.
<NotificationCenter
notifications={items}
onOpen={(id: string) => markRead(id)}
onReadAll={markAllRead}
/>Accessibility
- The bell is a button named with the count ("Notifications, 3 unread"); the badge on it is decoration.
- The panel is a titled Popover; focus moves into it and Escape returns to the bell.
- Each notification is one link or button; unread ones say "(unread)".
Tested against WCAG 2.2 AA on every release:
axe— No axe violations, in the component's own gallery and on its page.keyboard— Every action is reachable and operable from the keyboard alone.focus-visible— Focus is visible on every focusable part, in normal and forced-colors mode.forced-colors— State stays visible when the look's colours are replaced by the system's.target-size— Every target's real hit area is at least 24×24px, at every density.reflow— Content reflows into 320px and survives a doubled text size.
Not covered: screen-reader: not yet verified by a person. Everything above is a machine check; a person has not yet driven this component with a screen reader.
Motion & sound
- Reduced motion
- The panel appears without blooming (Popover's rule).
Props
| Prop | Type | Default |
|---|---|---|
notifications requiredNewest first: a title, a line, when, whether it's read, where it goes. | object[] | |
onOpenCalled with the id when one is opened; mark it read here. | function | |
onReadAllCalled by "Mark all read". | function | |
emptyTextWhat an empty inbox says. Default "Nothing new." | unknown |
Anti-patterns
- Never make the notification center the only record of something important: link to where it lives.
- Never show an unread count that never goes down: opening must mark read.
Changelog
- Every item needs
echo-ui-core0.3.0 (all components). The drawn device, readability past AA and the design tests live in core, and the components that use them are built against it, so each item now declaresecho-ui-core >=0.3.0 <0.4.0. Update core with the items:npm install echo-ui-core@^0.3.0(or your package manager's), thennpx echo-ui-cli update. An item whose files didn't change is the same code under a new version; the 0.2.0 files stay published. - App navigation:
SideNav,TabBarandNotificationCenter. -SideNav: an app's sidebar from data: named groups, icons, count badges and nested sections that fold. The current page carries a rail that travels to it;collapsedshrinks it to icons, each with its name as a tip.renderLinkhands the links to your router. -TabBar: the bottom bar of a phone app, three to five destinations with icons, a count badge and a pip under the current one.fixedpins it to the bottom, clear of the home indicator. -NotificationCenter: a bell with an unread count that opens a list of notifications, unread ones marked, with "Mark all read" and an empty state. - Comments only, no behaviour change. Comments in the component source used to cite documents, milestones and ticket numbers from Echo's own planning, none of which exist in your project. The citations are gone and the sentences around them stay. Where a comment was only a citation, it now says what it meant. Three development warnings (
HardwareButton'sengraved/captionchecks andStatusDot's missing-label check) also dropped the ticket code at the end of the message.echo-ui diffwill show changes in most items; none of them are to code. - An item's version is now a function of declared data, not of how the changelog is formatted. The version an item ships under is published once and never rewritten, and it used to be inferred from prose: a regex for a bolded "Breaking" run across the whole unreleased section, and attribution by "does a bullet mention this name in backticks". One breaking entry therefore moved every item that changed that cycle, and an entry explaining that "
MenuandSheetare unchanged here" filed itself as a change to Menu and Sheet — which it really had. - The agent brief says Echo has not shipped.
llms.txtand the MCP server's instructions led withnpx echo-ui-cli init, and that name on npm is a reserved stub with no executable — so a model following the brief wrote an install step that fails with npx's own error. The brief now opens with the caveat, and the docs carry it on every surface that shows a command. One switch (CLI_RELEASED) silences all of them at launch, and a test refuses to let one move without the others. Affectsall componentsonly in what the brief says about installing them; no item's props, CSS or rendered semantics change. - Echo's home is
echo-ui.com. The registry, the docs and the packages all move to it fromecho.nawwara.studio. Nothing was published under the old host, so noecho.jsonanywhere points at it and there is nothing to migrate — this is the last release where that is true. - Weights, line heights, letter-spacing, z-index, border widths and icon sizes come from the theme scales in
all components, with the old value as a fallback, so components keep working withecho-ui-core@0.0.1. Strays moved to the nearest step: most by under a pixel; HardwareButton icons are 14/16/20px (were 15/17/19). - A light device's recesses keep the body's hue in Chromium (
echo-ui-core, BUG-166). Chromium drops the hue of a colour under 0.02 chroma when it mixes in oklch, and draws the mix at hue 0, a rose. A light device's plastic is that grey, so on a lilac body every field, track and rail was pink. A mix made only of greys is made in oklab now, which has no hue to lose; a mix with an accent in it stays in oklch. On a dark device nothing you can see changes. - Content now reflows into a 320px screen (400% zoom) and survives a doubled browser text size (WCAG 1.4.10, 1.4.4), across
all components.Select's 180px floor,NumberField's readout,SegmentedandStepsas flex items,EmptyState's grid columns, andAvatar's fixed-pixel disc all gave way;Panelcounts its padding inside a width you set (box-sizing: border-box), so a<Panel style={{ width: 220 }}>is now 220px wide overall rather than 260px.