A more focused Spark UI
Spark UI is now a focused collection of 11 expressive components built for motion, personality, and memorable interaction.
v2.0Version 2 is a deliberate reset around what made Spark UI worth using in the first place: components with expressive motion, distinctive visuals, and interactions that are difficult to find in a traditional component library. The registry now contains 11 focused components, including Interactive Pets, Tactile Highlight, Shimmer Text, Image Trail, Animated Gradient, Ghost Ether, Logo Carousel, QR Code, Receipt, Basic Number Ticker, and Spotify Card.
The first release also shipped familiar buttons, form controls, dialogs, tables, navigation elements, and layout primitives. Those components worked, but they duplicated an ecosystem that shadcn/ui already maintains exceptionally well. They made Spark UI look like another general-purpose UI kit instead of a focused creative layer, and every duplicate primitive increased the amount of documentation, testing, dependency management, and long-term maintenance required.
We removed 25 shadcn-style registry components in Version 2. This was not a rejection of shadcn/ui. It was the opposite: shadcn/ui is already the right place for dependable application foundations, so Spark UI no longer needs to maintain competing versions of the same building blocks.
Spark UI now complements the component system you already use. Build the structure of an application with shadcn/ui, Base UI, Radix, or your own design system, then reach for Spark UI when a moment needs more character: a reactive headline, an animated background, a playful site companion, a visual number transition, or a richer media treatment.
The website and registry were rebuilt around that narrower purpose. Documentation is grouped by Backgrounds, Text & Motion, Media, Interactive, and Commerce. Installation examples, search, navigation, the agent skill, generated registry files, and project dependencies now describe only the retained collection.
Projects that previously copied a removed component are not broken—the source already lives in those projects and remains theirs. The change only means Spark UI no longer publishes or documents those primitive registry items going forward. New projects should install their standard primitives from their preferred system and use Spark UI for the signature layer.
A smaller registry gives each remaining component more attention, clearer examples, stronger accessibility and reduced-motion behavior, and a much clearer reason to exist. Version 2 is less about having more components and more about making every component unmistakably Spark UI.
Templates and Showcase are next. The first template will be a portfolio that developers can use as a starting point for presenting their work, while Showcase will give the community a place to share what they build with Spark UI.
Sign up early for a chance to be one of five users who receive Spark UI Pro for free, along with an exclusive early-supporter badge. More Pro benefits will be announced soon, so stay tuned.