From first public testing to Q3 2026 launch. Here is how BBUI evolved.

A few months ago we put out a call to the design community. We were looking for testers — real designers willing to poke around BBUI and tell us what wasn't working. The response on LinkedIn was genuinely surprising. A lot of impressions, a lot of engagement, and a healthy stream of designers who actually showed up and helped.

We said we'd listen. We did.

The feedback came back, we split it into two buckets: things we could act on now, and things that need more time and resources. The first bucket is done. The second is in the backlog.

What we've been building since then

The biggest piece of work was our variables system.

When we stress-tested BBUI with AI agents, a clear problem surfaced: our variable naming wasn't close enough to Tailwind's conventions. In the vibe-coding era, AI agents can read the metadata of your Figma files and generate code directly from them. A misaligned variable name breaks that handoff. So we went back through the documentation and updated the variables to follow Tailwind precisely.

We also tightened a lot of smaller things — sizing, whitespace consistency, the details that determine whether components scale cleanly from large to small. They do now.

Where we are today

We've integrated BBUI into three client projects. Having it as the foundation has changed how quickly we can start new work — no manual setup, no rebuilding the basics from scratch. Customizable, extendable, battle-tested.

We're now in the final polish phase. We're targeting Q3 2026.

If you signed up for early access — you'll hear from us first.

Join the waitlist

The Figma kit we built for ourselves. Soon available to everyone.

A Figma UI kit inspired by shadcn and Tailwind. Keeps designers and developers working from the same foundation.

Join the waitlist