Figma has quite possibly the worst versioning I've ever seen in a “collaborative” tool. Try it yourself — open a file (which takes an eternity if you have more than a dozen screens)1 and navigate to the history tab. You’re presented with a list of ALL the changes that have been made to the document, ab initio. And that’s where the Sequoia-invested Product Managers called it a day. One would imagine if you clicked on a certain date, you’d be able to see updates, or at the very least the delta. But no, apparently it’s super difficult to show states. As a developer, this doesn't provide nearly enough useful information immediately and only hinders the communication flow.
We have had to resort to adding comments and tagging devs near the relevant sections. The problem is no design tool has really solved this issue.
The tight feedback loop that was so carefully curated in our AGILE process is now completely blocked by a missing feature request that has a high impact at a relatively low implementation cost.
No, “naming” a version is not going to solve my pet peeve. I need actionable assistance so I don’t have to rifle through a hundred different app states and compare it with the current major version in production. Taking a screenshot and uploading it to JIRA/ Linear/ your current flavor of issue tracking software doesn't solve the problem and only moves the conversation to a different medium.
Miro does this adequately well, but it still sucks. At a glance, I'd like to see the highlighted changes, and instantly know what's changed in every iteration or design sprint.
I’m not even going to get into caching components and performance issues.
Share this post
Figma Fucking Failed
Share this post
Figma has quite possibly the worst versioning I've ever seen in a “collaborative” tool. Try it yourself — open a file (which takes an eternity if you have more than a dozen screens)1 and navigate to the history tab. You’re presented with a list of ALL the changes that have been made to the document, ab initio. And that’s where the Sequoia-invested Product Managers called it a day. One would imagine if you clicked on a certain date, you’d be able to see updates, or at the very least the delta. But no, apparently it’s super difficult to show states. As a developer, this doesn't provide nearly enough useful information immediately and only hinders the communication flow.
The tight feedback loop that was so carefully curated in our AGILE process is now completely blocked by a missing feature request that has a high impact at a relatively low implementation cost.
No, “naming” a version is not going to solve my pet peeve. I need actionable assistance so I don’t have to rifle through a hundred different app states and compare it with the current major version in production. Taking a screenshot and uploading it to JIRA/ Linear/ your current flavor of issue tracking software doesn't solve the problem and only moves the conversation to a different medium.
Miro does this adequately well, but it still sucks. At a glance, I'd like to see the highlighted changes, and instantly know what's changed in every iteration or design sprint.
I’m not even going to get into caching components and performance issues.
MightyApp is solving for x.