Case Study · ZapBook Design
Three component libraries fighting each other. Investors noticed.
Five years, three developers, two mid-cycle UI framework switches. We audited every screen, built a complete Figma system, and shipped a Storybook library — 1.8 months to handoff.
Status: Shipped.
Last updated:
Problem
The challenge
Five years, three developers, and two mid-cycle UI framework switches left ZapBook with three component libraries fighting each other. Buttons looked different on booking than on reporting — a signal about engineering quality for investors and enterprise prospects.
Outcome
What we built
We audited every screen before replacing anything, then built a complete Figma design system covering every component, state, spacing rule, and typographic scale. Every Figma component was then built in Storybook — same states, testable in isolation.
- →Full interface audit (all screens + states)
- →Complete Figma design system
- →Storybook component library (all states)
- →Spacing, typography + colour system docs
Tech stack
Full stack used on this build
Screenshots
Product in context
“Most dev shops build what you spec. SociiLabs built what you actually need.”
— Ben Karpinski, Owner, Supersonic Media Solutions
Talk to an engineer
30 minutes. You'll leave with a rough scope and a real timeline — whether or not you work with us.
