Measured entry
tripled-glass-forgot-password-card-shadcnui
auth-formglassmorphismmotion on file
A client-side forgot-password card distributed as a shadcn registry component. It uses React state for its confirmation message, Framer Motion for entrance and status transitions, and shadcn-style Button, Input, and Label primitives with Tailwind theme tokens. The included submit handler is only a visual demo and does not call a reset service.



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.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 70.5 KB (135.9 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 43.40s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/label.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A polished presentation layer for teams already using the expected component conventions, but not a finished recovery feature. It builds and mounts in the prepared harness, while a bare project fails because it needs a shadcn-style setup, including shared UI primitives and the usual utility module.
Use it if
- You need a compact forgot-password form that can drop into an existing shadcn and Tailwind application.
- You want a glass-style auth card with reduced-motion-aware animation and an inline submission status.
- You are prepared to connect the submit handler and sign-in action to your own authentication flow.
Skip it if
- Your project does not use Tailwind theme tokens or shadcn-compatible UI primitives and you do not want to recreate that styling foundation.
- You need a complete password recovery flow with API calls, validation feedback, error handling, and navigation already wired.
- You are minimizing client-side animation dependencies for a single authentication form.
Install
| Declared dependencies | framer-motion, react, radix-ui |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add React and Framer Motion, provide Button, Input, and Label equivalents, configure the at-sign source alias, add the shared class-name utility used by those primitives, and supply Tailwind classes plus the referenced theme tokens. Then replace the demo submit state and back-to-sign-in button with real authentication behavior.
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/moumen-soliman/uitripledAlternatives
Other published entries for the auth-form pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- meraki-auth-sign-in-card-with-side-imageminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.9KB
- Bare
- pass
- Prov
- NO
- shadcn-block-login-01minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 30.3KB
- Bare
- fail
- Prov
- NO
- shadcn-block-login-02minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 31.9KB
- Bare
- fail
- Prov
- NO
- shadcn-block-login-05minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 31.9KB
- Bare
- fail
- Prov
- NO
- 8bitcn-login-formskeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 33.2KB
- Bare
- fail
- Prov
- NO
- 8bitcn-advanced3skeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 33.3KB
- Bare
- fail
- Prov
- NO