Paper.design

Paper.design is a collaborative interface design tool: infinite canvas, components, variables, prototyping and developer handoff. It is built with code output in mind — it pairs with Cursor so a design can move towards implementation without a translation step in between. The problem it addresses is the gap between a design file and the code that ships.

It is in active use here. We use it for interface work that has to become code, which is nearly all of it. Keeping components and variables close to how they exist in the codebase means fewer decisions get lost between canvas and repository, and handoff stops being a separate ceremony.

Figma is the incumbent and remains the safe call: the plugin ecosystem, the hiring pool and the fact that everyone already knows it are real advantages. Framer is the better fit when the design is itself the deliverable and you want to publish the site from the same tool. Penpot is the option if you need open source or self-hosting. Sketch still suits macOS-native teams with established libraries. If you want to skip design files altogether, v0 or Lovable generate the interface as code from a prompt. Paper is the right call when the design-to-code loop is your bottleneck. If your constraint is collaboration or ecosystem instead, stay on Figma.