Measured entry

ruixen-notification-inbox-popover

alertglassmorphismmotion on file

A client-side React notification inbox delivered as a single shadcn registry TSX file. It uses motion/react for entry, layout, and read-state animation, inline scoped styles for the glass treatment, browser audio for optional click feedback, and callbacks or local state for marking items read.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of ruixen-notification-inbox-popover at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-notification-inbox-popover at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-notification-inbox-popover at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for ruixen-notification-inbox-popover
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious2
Axe moderate0
Axe minor0
Gzip marginal62.1 KB (127.5 KB build, 65.4 KB baseline)
Bare modeOK
Provider requiredNO
Demo usedwritten from the component source API

Verdict

A polished, functional inbox shell that builds and mounts on its own, with useful controlled-state hooks. Treat it as a strong visual starting point, not a drop-in production alert center, until contrast, focusability, and keyboard activation are corrected.

Use it if

  • You need a compact notification inbox with individual and bulk read actions.
  • Your interface benefits from pointer-driven row emphasis and animated state changes.
  • You want a self-contained client component that accepts external notification data and callbacks.

Skip it if

  • You need production-ready keyboard access without modifying the scrollable list and clickable rows.
  • Your accessibility baseline cannot accept the current low-contrast secondary text and controls.
  • You want to avoid an animation dependency, direct DOM styling, or browser audio behavior.
  • Your primary interaction is touch or keyboard, where the pointer-proximity effect adds little value.

Install

Installation record for ruixen-notification-inbox-popover
Declared dependenciesmotion
Missing on installnone
Bare installbuilds and mounts without the shadcn-style helpers
Providerno provider required in the harness

In a non-shadcn project, copy the TSX component into the app, install Motion, and render it from a React client boundary. No provider is required. Ensure the build supports TypeScript and JSX, then add keyboard semantics and contrast fixes before release.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

Alternatives

Other published entries for the alert pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.