menu

Figma

Figma is the first collaborative UI design tool built in the browser. Join our growing community and kick off a conversation!

Channels
# All channels
view-forward
# General
view-forward
# Start Here
view-forward
# Announcements
view-forward
# Design Systems
view-forward
# Plugins & API
view-forward
# Made with Figma
view-forward
# Prototyping
view-forward
Team
The Figma community has a new home. This thread is preserved for historical purposes. The content of this conversation may be innaccurrate or out of date. Go to new community home →

Version Control

February 6, 2019 at 9:01pm
Hi!
My journey have been Sketch -> Figma -> Sketch. Whereas Figma was a great discovery and I love how streamlined is the component management, there are 3 major reasons for the move back to Sketch:
  • Open-source plugin environment (we build internal plugins in Product Design team)
  • Team being used to Sketch
  • Version Control (Abstract)
My question is: how do you guys control version in Design teams using Figma? Is there any Abstract equivalent for Figma?
Thanks!
Show previous messages

February 19, 2019 at 7:09pm
I find it hard to show different kind of flows when I design something that has a lot of conditionality. E.g. a big survey where the user chooses different options and those different options will lead to different paths.
Designing the hi-fi separated from the context of the conditional flows get's hard. (the low-fi are also designed with the flows)
Edited
like-fill
1
  • reply
  • like
I mean. The prototypes are instances of the static...so it's not that big of a deal. The flow is just separate, and allows us to focus on each page rather than constantly dealing with the big picture.
  • reply
  • like
You can always jump to the prototype, and see how it fits into the flow. And that way it separates your thought patterns.
  • reply
  • like
Allowing you to focus on microinteractions, accessibility of this view, colors, etc.
Edited
  • reply
  • like
I always find it very hard to share just the prototypes even with devs that know the flows. they lose context pretty quickly, when they need to go back on the prototype, they get lost and some pages are not in the right order if you just click left and right on the keyboard. And, also in the context of making changes and iterations, I tend to always show the context of the screens with the flow
  • reply
  • like
but that's fine, I just want to understand how others do things. Until today I've always been the only designer in the teams. tks for sharing :)
Edited
  • reply
  • like
Yeah. I've been aggressive in promoting that they not left and right press on keyboard. I educated them by putting empty slides in that said to not use error keys. After seeing that a few times, and chuckling they learned to stop doing it.
Edited
like-fill
2
  • reply
  • like
private
This channel has been archived