Dom Gordon

I'll be joining Tommy for a live chat about all things design, tools, and new workflows at 12PM Pacific today. I'd love to answer some questions from chat. Come join in!

it has been wild weekend to see @paper pricing be the topic of design twitter let me share some of our internal discussions first: it's really valuable feedback. we want to find the optimal way to price that creates incredible value for the design and agent communities and also supports Paper as a growing team pricing is hard to get perfectly right. we'll iterate and I'm listening to all feedback I'm also grateful for how many people are posting about how Paper is worth it. Seriously, you don't know how much it means to me after pouring our lives into this software for the last 2 years. Paper is a currently 15 insanely talented people who are passionate about design and making the best software we can (we were 5 people earlier this year, growing fast!) we're going through a transition from "early adopter" stage to being the new default design tool for agentic teams, and some of the decisions we made a year ago need an update one thing that is good for everyone: the way Paper is currently pricing is mostly working: our revenue growth is off the charts and we're predominantly charging teams who get the most value. it means your design tool is going to be around in the future. You can invest your time and work in Paper. We can keep funding fixes and new features so next we'd love to find ways to let Paper be usable for side projects, student work, and dabbling. And only charge for professional work where it's easy to pay for your tools. So we're discussing: 1. Education program so Paper can be free for students and educators 2. New onboarding flow that shows how pricing works during the wizard so there are no surprises 3. Faster free tier resets - instead of weekly, perhaps it should be daily, or even hourly You'll see these and other ideas roll out over the coming weeks. Keep the feedback coming!

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 🙏

Testing out Pi's new support MCP in @paper looks to be working great (and fast too)