I wanted to share more about Components in @paper to help everyone plan for the upcoming launch. We've been hard at work and we have something truly next level to ship soon. 1. Components dev is going very well. We don't set hard deadlines, we're a "release it when it's good" kind of product, but I'd estimate ~1 month or so. Certainly before EOY. 2. Creating one shared world from your codebase to the canvas and back is the priority. We don't want to just repeat the abstractions from existing design tools; we want to fix the fragmented workflow between developers and designers. But we also don't want to add cognitive load or engineering concept while you're designing. Principle: designing with components should feel familiar, designer-first, and then also happen to align to your codebase effortlessly. No tool has ever pulled this off yet. 3. The initial components release will be mature and include: slots, variants with props, React in, React out, and full agent support. Components from your codebase can also run real code, so components can have logic, dates, and math. 4. Agents can read and write components quickly, accurately, and with low token usage. To your agent, components in Paper just look like React, which means they already know exactly how to use them. I'm so excited to share Paper components with the Paper community. Thanks for your patience as we do the R&D necessary to ship something next level 🙏

843