vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-progress-button

buttonliquid-glassmotion on file

A client-side React button that moves through idle, loading, and done states with a filling backdrop and animated label changes. It ships as a shadcn registry component with its theme CSS embedded in the file, depends on Motion for animation, and can create short browser audio ticks.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of ruixen-progress-button at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-progress-button at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of ruixen-progress-button 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-progress-button
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal60.6 KB (126.0 KB build, 65.4 KB baseline)
Bare modeOK
Provider requiredNO
Demo usedwritten from the component source API

Verdict

A polished, self-contained choice for demos and predictable timed actions, and it builds and mounts cleanly without framework helpers. For real submissions, its internal timer and lack of controlled error handling make it a starting point rather than a finished workflow control.

Use it if

  • You need a compact submit control with a self-contained simulated progress sequence.
  • Your interface already uses Motion or can justify adding it for this interaction.
  • A timer-driven confirmation is appropriate because the action has predictable duration or is only a demo.

Skip it if

  • The done state must reflect the actual resolution or failure of an asynchronous operation.
  • You need controlled loading, disabled, error, or cancellation states from a parent component.
  • You cannot accept audio being enabled by default or do not want to manage browser audio behavior.
  • You need a form button with an explicit button type and production submission semantics out of the box.

Install

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

In a non-shadcn React project, copy the component into a client-rendered module and add the Motion package. No utility CSS framework or provider is required because the styles are embedded. Decide whether to disable the default sound and add explicit form behavior before production use.

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.

Author repository

github.com/ruixenui/ruixen.com
License
MIT
Record published
2026-08-14

Alternatives

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