Hi {{first_name|Oncer}},Once UI 2.0 is on Product Hunt.The past several weeks have been intense. Alongside this release, we built six in-house apps, worked with local businesses, rebuilt our landing page and rethought the entire Pro offering.What made that possible was the infrastructure around the work. We finally had the capacity to give a major release the testing, measurement, migration support and documentation it deserves.
Measured before we decided
We started with an alpha release so the system could meet real projects before the wider launch. We built a codemod and migration guide, expanded the tests, ran accessibility and performance audits, and reworked the documentation down to the last prop and utility.The work behind that is easy to overlook. Every proposed change needed evidence: what it would improve, which apps it would affect, and how we could verify the result. The decisions stayed human; the capacity to investigate them changed dramatically.That is what maturity means to me here: being able to explain a decision, test it and help people move forward with it.
Six apps, one shared view
We built six in-house apps in parallel with the same agent overseeing their repositories alongside Once UI itself.
That shared context made duplication visible. A sidebar or settings pattern repeated across products became a reason to improve the system. A proposed change could be checked against the apps that would actually need to adopt it.Our products became a continuous source of evidence for Once UI, and improvements to Once UI went back into those products. We could develop the foundation while seeing exactly where it helped and where it got in the way.
The launch reaches beyond the package
The landing page has been completely reworked. All of our blocks are now free under MIT, so you can use and adapt them in your own projects.We also rebuilt the whole Pro offering. A single scaffolder can spin up several different app surfaces, with optional Supabase authentication and Stripe integration. The goal is to make the path from a design system to a working application much shorter.
During the same period, we worked with multiple local businesses and built web infrastructure around how they operate.
Side, a local café, is one example. The project began with a brand and a website. Adding reservations opened up the software behind the business: tables, availability, timing and the interface needed to manage them.
The café's public website and its operator interface have different needs. Building both on the same foundation gave us another way to test how far Once UI could stretch while keeping each experience appropriate to the people using it.
The infrastructure behind the launch
Claude, Vercel, Supabase and Bunny made this work possible. Anthropic's Claude for Open Source program gave us the capacity to take on the engineering work a release like this needs.
Our own tools carried the launch too: Aveiro for publishing, Chirio for social media distribution, Frametic for launch videos and Scenetic for screen captures.
While we were busy shipping, Aveiro and ChatGPT helped keep communication moving: publishing blog posts and preparing and scheduling social content for review. Having that workflow in place gave us room to focus on the release without letting the story disappear.
Built with you
Thank you to Justin, Div, Chander and the Design Engineers Club, and to everyone who used, improved and contributed to Once UI and the community around it.
Div's work on the earlier release became an important part of the foundation for 2.0. The reports, pull requests, questions and real projects from the community kept showing us where the system needed to improve.
Once UI 2.0 represents weeks of concentrated work, supported by years of building the systems around it. I'm proud of what we shipped and of the care we could put behind it.
Take a look at the Product Hunt launch, try it in a real project, and tell us what you think. Your feedback will help shape what comes next.
