shadcn/ui vs Kittl
Side-by-side trajectory, velocity, and editorial themes.
shadcn flips new projects to Base UI by default and grows into chat UI and open registries
This is shadcn/ui's dated docs changelog, and the entries are clean human-written headlines describing real shipped capabilities rather than version stamps or marketing filler. The recent window mixes a foundational default-primitive switch with new component families and registry/CLI tooling. No feed-quality issues here.
Two arcs are visible: the underlying primitive layer is shifting from Radix to Base UI (now the default for new projects, Radix still supported), and the distribution model is opening up via GitHub-repo registries, registry include/validate, package.json imports, and preset commands. On top of that, the component surface is expanding into chat interfaces and denser themes (Rhea). The direction is less about individual widgets and more about shadcn as a primitive-agnostic component-distribution platform.
With Base UI now the default, expect more components and themes to standardize on it while Radix compatibility is maintained. The registry tooling investment suggests continued work on third-party/community registry distribution.
Kittl goes agentic: design by intent, with the tools you use wired in.
Kittl is a browser-based design tool that has moved aggressively into AI-native creation. Its weekly product-update cadence carries steady craft improvements (brand kits, on-brand generation), but the last two headline releases are directional: an Apps panel that pulls external tools into the canvas, and now an Agentic AI mode that shifts creation from manual prompt-and-parameter tuning toward stating intent and letting the system drive. Kittl is compressing the distance between idea and finished design.
The product is consolidating the whole design workflow inside one surface — first by integrating outside tools (Apps), then by automating the decision-making inside creation (Agentic AI). Together they point at Kittl as an AI design environment where the user sets direction and the agent handles model, format, and style choices, with connected services feeding assets and distribution.
Expect Kittl to widen the Apps ecosystem and give the agent more reach — chaining multi-step design tasks and acting across the connected apps rather than generating single artifacts.
See more alternatives to shadcn/ui →
See more alternatives to Kittl →