Design System
Components are shared infrastructure: every designer and every product on the platform depends on them. At Corva, only 3 of 10 designers work on the component library, and I build and maintain my components entirely on my own. The bar is high: a single decision ripples across the whole product.
Over time I've built and maintained a range of components across the library: App Header, Templates, Inputs & Selects, Formula, File Upload, Slider, Switch, Table, and Checkbox among them.
End-to-end ownership
I own each component from idea to production, not just the Figma file. The whole lifecycle:
Align
Validate the need and the API with stakeholders and the entire design team before a single pixel is drawn.
Design
Build it in Figma: every state, variant, token, and edge case.
Build
Implement it in Storybook side by side with a developer, reviewing behavior down to the detail.
Maintain
Keep it alive as the platform grows: support, fixes, and iterations.
Templates
20+ appsA core platform feature, now adopted in 20+ apps.
Inputs & Selects
10+ appsOne unified component replacing every input across the platform.
Formula
0→1A brand-new 0→1 component with no precedent on the platform.