✳flâneur — a map of the web's best reading

Bootstrapping a UI component library — Ramp Builders Blog

engineering.ramp.com · 54 words · saved by 1 readers

At a small startup, the timing is never quite right to start a component library. Extremely quick iteration is not usually associated with putting together a standardized set of components and conventions to use across your app, as your components and conventions change all the time in the frenzy of finding product-market fit! Nevertheless, component libraries can be tremendously valuable in separating design concerns from feature development and business logic, eventually leading to faster-than-ever iteration. In this article we'll explore what went into our component library — we called it Ryu — and what we left out, the tradeoffs we made along the way, and the vision for its future. Let's go! In essence, our component library consists of colors, sizes, fonts, line heights, and even media breakpoints and z-indices. When building a component library you don't generally come up with these values, but rather you take them from what Design has already fleshed out — probably in Figma. The

How we agentically found, validated, and patched ~100 security issues in a 1-week experiment. Agents acting on behalf of a user provides a natural starting point for finance teams beginning to adopt agents, as well as for fully autonomous companies. How we are building agentic operations at Ramp, and where we are headed next

Explore this link on the map →

related reading