Member-only story
UI/UX Design: Version Control
A little-known but extremely powerful feature of Figma that can be a game-changer for your design workflow.
Overview
I’ve been asked in the past why I’m such a fan of Figma, and it’s because in all my years as a designer, I’ve never come across such a well-rounded, versatile tool.
From document sharing, collaboration, and real-time editing, to a totally open community with plugins, files, and resources, not to mention a robust set of modern UI/UX design tools, components, instances, properties, variants, the list goes on.
Today however, I am going to be sharing with you a a little-known but extremely powerful feature of Figma that can be a game-changer for your design workflow.
What is version control?
Once the domain of developers only, version control has slowly made it’s way into every facet of the product creation lifecycle.
In short, version control allows multiple users to:
- work on the same base project,
- view changes to the project,
- track different versions of the project,
- merge changes to the main version of the project,
- and if necessary roll back to any previous version of the project.
If you’re like me you’re already giddy about the prospect of being able to smoothly and easily swap between versions of your design documents.
Let’s take a look at how it works.
Version control in Figma
I was absolutely giddy the first time I heard that Figma had a type of version control built in, and it absolutely delivers.
With Figma’s version control system, you can both actively save document states with names and dates, or you can allow the system to automatically generate saved document states as you’re working within your project.
The automatic way happens, well…automatically, but the named saves are where things can get REALLY interesting.
