Hi {{first_name|Oncer}},I’ve spent the last few months building around Once UI, and that exposed a lot of things I wanted to fix in the system itself.Once UI 2.0 is the result.It is not just a component update. It is a systems reset designed to make Once UI easier to adopt, extend, upgrade and trust in production.
Once UI 2.0 is entering the final stretch
The release is roughly 2–3 weeks away.Instead of carrying every old decision forward, we are using 2.0 to rethink the architecture, product layer and developer workflow together.
Less coupling
The repository is being split into clearer packages, and framework-specific behavior is moving behind adapters.That means Once UI will no longer be tightly coupled to Next.js. A dedicated adapter will preserve the smooth Next.js experience, while the core becomes much easier to use in other React environments.We are also building a Tailwind adapter, so teams can bring Once UI into an existing Tailwind stack without giving up the system underneath it.
Better foundations
Component APIs are becoming more consistent across the library. We are adding new components, improving performance, reducing unnecessary client-side work and expanding test coverage.The goal is not simply to ship more components. It is to make the whole system easier to understand and safer to depend on.
A complete Pro and template rework
Once UI Pro and the template collection are being rebuilt alongside the core.The templates should feel like composed products built on the system, not disconnected downloads that slowly drift away from it. They will share clearer foundations, better upgrade paths and a more coherent role inside the wider Once UI ecosystem.
Built for humans and agents
The new CLI replaces the fragmented tools that exist today. It is being designed for both humans and AI agents, with every important workflow available non-interactively.The AI harness is also getting a major upgrade, with better guidance and validation for generated code. A codemod will handle as much of the 1.x to 2.0 migration as possible, so adopting the new architecture should not mean rebuilding your project from scratch.This is less about adding another layer of AI branding and more about making Once UI predictable enough for agents to work with safely.
Once UI 2.0 is becoming easier to adopt, less coupled, more consistent and much easier to trust.
I’ll share more of the architecture and migration path over the next couple of weeks. If you use Once UI today, this is the release to watch.
You can now add a URL and have Frametic build and render a complete promotional video from the page automatically.
I’ve talked about Frametic quite a bit recently, so I’ll keep this one short. But this is probably the clearest version yet of what I originally wanted the product to become.
Everything else I published recently. Pick whatever looks interesting.
How I deleted 460 customer accounts
I thought Aveiro was being exploited, disabled 460 accounts and wiped almost $6,000 in projected MRR. Then I opened what people had built.
