UI
v2.2
August 5, 2026
Moving the UI primitives to Base UI
In progress: shadcn components are shifting from Radix to Base UI. Not finished — some surfaces still Radix — but the direction is locked.
Radix served the kit. Base UI is where shadcn is going, and the kit is following. This is a migration in flight, not a victory lap — dialogs, menus, and the rest still have leftover Radix, and we are replacing them as we touch each surface.
Direction is set
New UI lands on Base UI. We are not adding more Radix primitives.
Not done yet
Several dialogs, menus, and form controls still sit on Radix. They move when we next touch that file.
Same look
shadcn new-york styling stays. Buyers should not notice a theme rewrite — just fewer Radix-shaped bugs over time.
Ship on V2 today
Get the full monorepo — web, mobile, extension, SDK, and MCP.
Zero To Shipped V2 gives you the production Next.js app, Expo mobile app, browser extension, auth, billing, REST API, and deploy paths already connected.
One-time payment. Lifetime updates.
Why bother mid-flight
Waiting for a perfect cutover means shipping more Radix. Better to lock the destination and migrate in place.
- components.json already points at the current shadcn / new-york setup
- New primitives come from Base UI
- Old Radix pieces get replaced as they get touched — no big-bang rewrite
More updates
September 4, 2026 · v2.6
Agent rules hardened
Read updateSeptember 1, 2026 · v2.5
The kit is agent-native now
Read updateAugust 21, 2026 · v2.4
Every dependency bumped
Read updateAugust 12, 2026 · v2.3
Moved lint and format to oxlint + ultracite
Read updateJuly 18, 2026 · v2.1
Buyers can file bugs from inside the product
Read updateMay 22, 2026 · v2.0