At @paper we think that design has different needs than eng for good reasons Design is expanding: what should we do? Mapping the problem space, studying prior art, experimenting visually, trying 10 versions right next to each other, sharing in real time Engineering is narrowing: defining precise behaviors under exact browser conditions and states when you know what to build Being able to do both is really good. We should all be builders at the end of the day. But design and eng are different modes of work and do not have the same needs. With love to my friends at Cursor, a lot of IDEs have added a font picker and called it a design tool. And while I think that it's useful, but it's only a tiny fraction of what designers do. What we do need is our design tools to be connected and open, which is why Paper: - Uses real html/css code as our rendering engine. It's LLM native and lets you drag and drop your code components on a multiplayer canvas - Will use AI and data connectors to pull in real data from Notion, Google Docs, APIs, or sync your visual design decisions to Cursor - Is adding design agents to save boilerplate work, letting you do a week's worth of design work in a day and focus effort on the inspiring work In any case, I'm excited for all the new possibilities and tools. My advice to everyone is to lean into it, have fun learning, and make more great software for the world!