Skip to main content

Currently, Figma allows users to view who made changes on specific dates and restore file versions. However, in collaborative environments, when multiple designers work on the same file, it becomes challenging to track specific changes (e.g., who modified a component, altered a style, or moved an element). This lack of granularity can lead to inefficiencies when trying to pinpoint changes to revert or discuss.


Proposed Solution:

Introduce a Design Change Log feature in Figma, similar to Git for developers. This log would:



  • Provide detailed change tracking at the object/component level.

  • Highlight who made each specific change and when.

  • Allow users to review changes in a granular view (e.g., “Designer X resized this frame,” “Designer Y updated the text in this component”).

  • Enable selective restoration of changes (e.g., restore only one modified component instead of the entire file).


Benefits:



  • Improves collaboration in multi-designer projects.

  • Reduces confusion about overlapping changes.

  • Enhances accountability and transparency in the design process.

  • Helps teams maintain a clean and consistent design history.


What do you think about it guys? do you had the same problem?

Sounds like a good idea, at least at a higher design level (components, styles, variables).

Hey @Hossein_Khalili, thanks for the feedback!


We’ll pass this onto the team for future consideration.

Great News! Thanks for your quick response

I think you can get sort of the same function by using todays function ‘save to version history’ (file > save to version history). Its a very simple feature, but it might be a solution?

Screenshot 2024-11-19 at 09.59.01

That’s a nice for an overview of the changes - but it’s manual. It would be great to see, in detail, which elements were changed without having to rely on everyone not forgetting to write all the changes.


Plus, there’s no way to select what to restore (like Git), only the full file.

Definitely agree - that would be much smoother.

I wasn’t aware of this feature, thank you for bringing it to my attention. While it works well in certain scenarios, maintaining a detailed log of changes tends to be more reliable. The main challenge arises when individuals modify a component or page, or even replace it entirely, but fail to document these changes in a log. However, with this feature, we could establish a new protocol requiring designers to consistently log their updates. This approach could offer significant benefits and improve accountability within the process.

love this idea - changes works well with the dev mode things but not so much amongst designers

Reply


Terms & ConditionsCookie settings