Comments on postSubform
Ryan Lucas
@ryanlucas
Thanks for the hunt, Kevin! Kevin Lynagh and I started working on Subform over a year ago, frustrated with the limitations of print-based design tooling for building complex UIs. We’ve since talked with hundreds of designers and front-end developers about their design process—and what they wish design tools could do. Subform is the end result of those conversations. I'm obviously biased, but having access to a true layout engine at design-time has been amazing. It feels like the future. We're excited to get it in everybody's hands. If you have any questions, just reply---I'll be around today.
Jamie Wilson
@jmwlsn · Designer/Developer
@ryanlucas Hey Ryan, I posted this over on Kickstarter as well, but feel free to answer it here instead. I'm really excited that you guys are seeking funding to make Subform a reality, but two questions I have, based on some frustration with other new apps I've tried, are: 1. What's the current support for working with SVGs within Subform? 2. Will Subform be able to work with/import other file formats like .ai or .sketch?
Ryan Lucas
@ryanlucas
@jmwlsn I think Kevin just posted an answer for you over on the Kickstarter page. Let me know if you have more questions.
Bruce Criscuolo
@usabilityarts · Senior UX Designer, EPAM
Our team is closely watching Subform. We need to iterate constantly and output HTML or InVision prototypes or wireframes that just can't show what we need them to show - Subform will reduce our design time, let us test/iterate against the output, and ultimately would enable us define the responsive spectrum against viewport sizes and content. I'm rooting for this because I see a huge gap that this realistically fills.