MotionLoom vs sensory-ui

A future Anica panel can expose After Effects-style controls while preserving the graph underneath.

sensory-ui swaps standard shadcn/ui parts for versions that play short synthesized cues on clicks, toggles and dialogs, with no audio files to ship.

About MotionLoom

A future Anica panel can expose After Effects-style controls while preserving the graph underneath. The same source can be opened, edited, diffed, generated by agents, or compiled by the renderer. Scene graphs render through MotionLoom WASM; native renderer errors are surfaced instead of hidden by a browser fallback. This playground uses a Canvas 2D fallback to demonstrate the graph execution model. The real Anica desktop app runs the same MotionLoom DSL through Rust/WGPU with full GPU compute and video export.

About sensory-ui

sensory-ui is a React and Next.js component set that adds audio cues to familiar shadcn/ui elements such as buttons, switches, sliders, tabs, toasts and dialogs. Developers install components through the shadcn CLI and turn sound on with a prop. All audio is synthesized in the browser with the Web Audio API, so there are no sound files or network requests, and the library weighs about 28 KB gzipped. It ships 24 components, 17 cues and nine sound packs. The design guidance ties each sound to a meaningful interaction, keeps small actions quiet, honours reduced motion settings and allows muting globally or by category. The project now sits under Shadcn Labs.