Skip to main content

Scenario: Large design file with 15+ pages

#Designers per team: multiple
Context: We have multiple feature based design files and each file is 10+ pages with multiple designers in one team working in the same file.
Problem: Branching creates multiple huge files with all pages. With multiple designers working together and making updates every week if not everyday, its very hard to merge these huge files after reviewing multiple updates every time a change is made.

Idea: There seems to be a need for selective branching and merging. The user can select what pages they want branched and merge them once the feature is updated. This would not overload the files or system and would reduce redundancy.

This is a fantastic suggestion! It would absolutely help our design team collaborate in a more efficient and streamlined workflow process.

This could also mitigate merge conflicts as each designer would only branch the pages they are responsible for in a given sprint.

Would love to see this implemented which will really make our team adopt this feature. We’ve been having issues with merge conflicts and going through each individual frame change can be extremely time consuming

Agree with the comments above! Best in class branching and merging allows developers to: 

  • Clearly see the changes (this is really hard in Figma right now)
  • Decide which changes to pull and which to leave (the main point of this suggestion)
  • Go back and see a history of changes, including when they were done, who by, and what changed (this could also do with some improvement, the ‘change history’ feature is REALLY hard to access right now)

Cheers

Reply


Terms & ConditionsCookie settings