Measured entry

ruixen-gooey-dock

cursor-effectunclassifiedmotion on file

A client-side React dock that enlarges and lifts nearby items as the pointer moves, with hover labels, an active marker, and optional generated tick audio. It ships as a shadcn registry component, styles itself inline, and depends on Motion; icons and click handlers are supplied by the consumer.

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

What the harness recorded

BARE BUILD

✗ Build failed in 489ms
error during build:
[vite]: Rollup failed to resolve import "lucide-react" from "<sandbox>re-5614f2978498/src/cut/demo.jsx".

Verdict

A polished desktop pointer effect that builds and mounts cleanly without extra providers. Use it for secondary launchers, not as-is for primary navigation: the div-based actions need keyboard semantics, and the signature interaction offers little to touch users.

Use it if

  • You want a compact desktop launcher whose pointer proximity effect is central to the interaction.
  • Your app already uses Motion and can supply its own icon nodes, labels, and actions.
  • You want light and dark presentation without adopting a separate component theme layer.

Skip it if

  • Your navigation must offer equivalent keyboard behavior, since each action is implemented as a clickable div without button semantics.
  • Touch interaction is the primary experience, because the magnification and labels depend on mouse movement and hover.
  • You cannot justify adding Motion for a single navigation effect.
  • Your product should never create interface sounds by default unless every caller remembers to disable them.

Install

Installation record for ruixen-gooey-dock
Declared dependenciesmotion
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

Install Motion, copy the client component into the project, and ensure React supports client components. Supply icon nodes and action callbacks yourself. Add button semantics and keyboard handling before using it for navigation, and set sound off where interface audio is inappropriate.

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