I.e., "Tool A, used to design for technology B, doesn't output files in technology B format. [...] doesn't make much sense".
E.g., why not just use Webflow then? From my understanding, that's what it does, that's what it's made for.
I.e., "Tool A, used to design for technology B, doesn't output files in technology B format. [...] doesn't make much sense".
E.g., why not just use Webflow then? From my understanding, that's what it does, that's what it's made for.
I’d argue Figma got where they are mainly by streamlining the handoff process, not because of their live editing collaboration features per se. But there isn’t really an empirical way to validate this. But my point is really if you want to export natively to the web, just use, promote, etc... WebFlow that's the tool designed for that job.
> [Figma targets] design more broadly than simply website building.
This is absolutely true, but I’d argue it’s impossible to be able to both target many platforms, and simultaneously be able to export to all those platforms natively. I.e., you have to build the constraints of a specific platform into your tool in order to export to that format. This is what WebFlow is (and using it for just 5 minutes makes clear the trade-offs of designing a tool like that).
I think they could do more for exports in this day and age, but I'm not them.