vibecodng.com

Free MCP betaIndex and tools live

Measured entry

ruixen-phone-mockup-card

statsunclassifiedmotion on file

A client-side React card that presents copy and typography metrics inside a cropped phone frame. It ships as a shadcn registry component styled with Tailwind utility classes, animates its entrance with Motion, and uses React Icons for the status bar symbols.

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

Verdict

A polished, focused presentation card that mounts cleanly and adapts without overflow. It is a sensible pick when the phone metaphor fits the page, but its animation and icon dependencies are a meaningful cost for content that is otherwise static.

Use it if

  • You need a decorative phone preview for a product, portfolio, or design-system section.
  • Your page already uses Tailwind and can accommodate an animated client component.
  • You want configurable title, body copy, highlighted text, and metric labels without rebuilding the device frame.

Skip it if

  • You need an interactive phone simulator with controls, scrolling, or real application content.
  • Your design cannot justify adding Motion and React Icons for a single decorative card.
  • You need a complete device outline rather than a frame that deliberately fades and crops near the bottom.
  • Your project renders only server components and cannot include a client-side animation boundary.

Install

Installation record for ruixen-phone-mockup-card
Declared dependenciesmotion, react-icons
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 component into your source tree, install Motion and React Icons, and ensure Tailwind scans the file and provides its neutral palette, dark-mode variant, arbitrary values, mask support, and standard utility classes. The host must support React client components.

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 stats pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.