MiniDev UI vs coss ui (formerly Origin UI): which should you use?

What happened to Origin UI

Origin UI was a large, well loved collection of copy and paste components for application UI, built with Tailwind CSS and React. In October 2025 its creator announced that Origin UI was becoming part of coss.com, the company behind Cal.com. The work now continues in coss ui, described as a modern component library built on top of Base UI and the official design system of Cal.com. The original collection is still available at coss.com/origin.

MiniDev UI is a free, MIT licensed shadcn-compatible registry of over 500 items, also built on Base UI, with Tailwind CSS v4 and motion. It covers core components and goes further into full product screens such as billing, settings, data tables and AI chat, plus page blocks and about 86 motion components.

Where coss ui shines

• Production tested. It is the design system of a real, widely used product, so components are shaped by day to day use.
• Form and input craft. Origin UI was known for many thoughtful variations of inputs, selects and other controls, and particles continue that idea.
• Clean, neutral style. Components look at home in most products without a strong visual signature to override.
• Public roadmap. The docs include a roadmap, so you can see what is planned.

Where MiniDev UI shines

• Whole screens. About 43 blocks and pages, from a sign in page to an admin console and support inbox.
• Product domains. Billing, invoices, settings, notifications, command palettes, kanban boards and AI chat surfaces.
• Motion. Around 72 animated components for heroes, pricing, marquees and scroll stories, all free.
• Material system. One light source drives shadows across the page, and a data-material attribute switches between hairline, glass, metal and paper.

Using them together

Because both libraries are built on Base UI and both install with the shadcn CLI, they share a primitive layer and a workflow. You could use coss ui particles for a specific form pattern and MiniDev UI for full pages, without adding a second headless library. Check for file name overlaps (for example, both may provide a button or input) and keep one version of each base component so styles stay consistent.

The MiniDev stylesheet maps the common shadcn/ui token names to its own tokens, which helps components from other shadcn-style libraries follow the MiniDev theme. One difference to review: MiniDev's accent is the brand violet rather than a subtle fill.

Install and migration notes

npx shadcn@latest add https://ui.minidev.pro/r/sign-in-page.json

Then import the tokens after Tailwind with @import "minidev-ui-kit/styles.css";. If you have older Origin UI components in your project that were built on Radix, they keep working as they are; moving to either coss ui or MiniDev UI means moving those pieces to Base UI, which you can do one component at a time.

Which to pick

• Choose coss ui if you want a neutral, production tested set of core components and form patterns, and you like the idea of tracking the design system a real product ships with.
• Choose MiniDev UI if you want finished screens and page blocks, motion components and a theming system with materials, all under MIT.
• Choose both if you want coss ui form patterns inside MiniDev page layouts. The shared Base UI layer keeps that combination light.