From static mockups to living prototypes

Speakeasy builds SDK tooling for developers, and its internal workflow reflects that audience: the team treats design as an extension of code. Figma still serves for early visual exploration, but the team found that static pixel designs couldn't communicate the movement, behavior, and interaction that define their product. Meticulously designing every feature in Figma also didn't fit their iteration cadence, so they turned to v0 as the bridge between design intent and shippable code.

Collaborating in a code-native medium

v0 gives everyone at Speakeasy—not just designers or engineers—a way to explore and share ideas quickly. The platform uses AWS Bedrock's foundation model infrastructure to generate full-stack applications from natural language prompts, letting the team describe a behavior or interaction and get working code back in real time.

Some Speakeasy designs begin in Figma and are imported into v0, but many concepts are now born directly in v0. That lets designers and engineers refine ideas together without the usual design-to-code translation step. The initial concept for the Terminal Preview in the Speakeasy dashboard was built in a single day using v0, which let the team invest its effort in interactivity and user experience instead of converting static layouts into frontend code.

The team's workflow leans on a custom Tailwind configuration, which v0 uses to generate components that match their design system. Font weights and colors for the Terminal Preview feature, for instance, were all defined and applied inside v0.

Example of defining custom style preferences in the tailwind.config.js file in v0. Example of defining custom style preferences in the tailwind.config.js file in v0.

Adopting v0 also changed how the team communicates. Instead of long Slack threads or meetings, Speakeasy team members share Loom recordings of their v0 prototypes. The phrase "Share a v0" has become shorthand for conveying a design idea, and it works across roles—backend developers use it as readily as designers.

"The reason I jumped to v0, was a bias towards code. It meant less time having to redo ideas in Figma. When it comes to getting ready to ship, I was already in the right medium. I saved whatever time it would have taken me to translate Figma to code."

Faraz Khan Design Engineer

By prototyping in a code-native environment from the start, Speakeasy shortens iteration loops, keeps design and engineering aligned, and ends up with production-ready components rather than handoff artifacts. For them, v0 is less a design tool than the default way to build developer experiences.