HUGE fan of Webflow. Been using it for 4 years and yes, I understand what you’re saying. I’ve actually been working with them over the last few months on a long format tutorial. Stay tuned for that on their site. (shameless plug)

The limitations of it, though, are that it’s super awesome at making great marketing sites, but not so much product design, which is what I do. It’s missing that component-able, reusable side of things that would be needed for true product designs. I’ve build product prototypes in it, and built spec sheets with it, but for riffing, getting a team oriented around a single design system, and being able to experiment, it’s too rigid IMO.

Yes, a lot of the issues I originally brought up have been addressed with Sketch. They recently added prototyping, a better team library, and some of the constraints functionality. I’ve not used it for a while, so I don’t know how well they work, but I’m sure they’re great. Others, like inVision Studio, seem to be improving on some of the other parts as well.

As of the last few months, though, I’ve joined a relatively large design team which was using Sketch, but living with the issues that arose from everyone having their own file management system. There was little to no transparency across teams, and working together on a project was a frustrating experience. We decided to switch everyone over to Figma, and it’s been great thus far. Not having worked in a team this size before, I was more flippant about the multi-player aspect of it… Now, I think that’s their killer feature.

• We no longer are in Dropbox file management hell.
• We no longer have to save, version, and attach our Sketch files to emails to slack threads.
• We no longer are using different plugins that the design when someone else opens it.
• We no longer have to worry about missing local fonts.
• We no longer have to pay for Zeplin and Invision to share prototypes.
• We no longer have to take screenshots of what part of a file we’re talking about when sending it to other designers.
• We no longer have to comment about design elements in slack, away from the context of a spec.
• We no longer have to point at someone else’s file to try to explain what we mean, but can duplicate an element right next to their’s, and show them in the same file.
• We can jam on a problem in the same file from multiple locations.

It’s really blown my socks off with the collaboration aspect. I think Webflow will, by nature, lag behind that for a true product design space. The handoff from designer to designer is much more difficult. I’ve opened many a Webflow project and understood what was going on, but had my own ways of doing things that would have broken that system. I’d love to see how teams are documenting and ensuring consistency across Webflow projects. I’ve never seen or done that part too well.