- Last post
- 7 Responses
Not sure how many of you are using Figma, but I know a lot more teams are adopting it as the go to tool.
I'm building a new design team and because were an early stage startup, Im considering going full Figma since it seems to encompass a lot of the features that Sketch +Invision/craft+Zepplin used to provide.
The only thing that seems to be missing is version control.
Curious if any of you old heads are using Figma, and whats your experience with it when it comes to version control/branching.
Not quite a full git-style solution like Abstract, but looks like it does have some basic version control built in: https://help.figma.com/hc/en-us/…
Really wish our team had switched to Figma over the cobbled together Sketch+Cloud+Zeplin+Invision+Abs... ... so many places to update everything and it all half-works-together
^ yeah they have version history... but not quite version control.
I can probably get away with not having robust version control in the first 3 or 4 months... but im worried about future state... if I get the team to 4 + people. Is updating a master design system going to be a manual process?
Have you looked at Figma Master Components? And Libraries?
I ask because I'm not sure what you meant by "manual process"
Well even with master components and libraries, there needs to be some governance around those.
Designers need to be able to play with those without fear of effecting all the other dependencies. Which is where automated branching comes in handy.
You could manually duplicate artboards for that type of exploration, but eventually you'll have to take the new and approved components back to the original "master" library for everyone to use. And that seems like a lot of manual work if you have multiple contributors making changes on the fly.
You can use draft mode to fiddle around and then update the components in your team's assets when you're ready. All of it is recorded in the version history. What exactly are you missing as a feature?
^ that could work actually...
...Im just used to using abstract, I built my last team's workflow off of that... so Im trying to wrap my head around a new way of controlling the process.
- It looks like abstract is smoother for branching out a design, it's closer to a dev environment. You could checkout invision's DSM too, it's pretty solid.zarkonite
- Figma is constantly evolving too so I'm sure they'll catch up to abstract in a couple of versions.zarkonite