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

inVision DSM vs Sketch Library vs Figma Team Library

April 22, 2019 at 7:06pm

inVision DSM vs Sketch Library vs Figma Team Library

April 22, 2019 at 7:06pm
Does anyone has experiece trasition between any of these that can tell us about pros and cons?

April 22, 2019 at 8:00pm
Depends on what you need it for -- dev handoff, designer collaboration, documentation, code examples, all of the above? Our team used InVision DSM, currently uses Sketch, and plans to switch to Figma team very soon. Anyway, if you describe your planned collaboration model, I may be able to share my 2 cents. There are other tools such as Abstract (and even straight-up Git) for versioning, if that is also important for your design team.
  • reply
  • like
Thanks . I'm most interested in the Designer Collaboration aspect of those tools and the possibility to update components and styles across multiple files while keeping everyone in the loop. I try them all but haven't really use them on a project yet so I might be missing limitations that will appear in the long term. With the reaserch I did so far I'm more inclined to finally make the switch to Figma and stick to that. Reasons are easy of use, granularity in styles (color, stoke, shadow, etc..) that you can apply to everything, seamless comunication when changes are made, and just the fact that Figma provides everything we need within the tool without having to rely on external plugins or syncing.
  • reply
  • like
Got it. InVision DSM is "nice" but it feels more built for documentation and less collaboration, specifically between designers. Plus you (at the time we tried it) needed Sketch to upload so it just felt like an extra step to always have to jump through. Sketch is nice, and if you bundle it with a tool like Abstract, you can sort of get a nice collaboration model going, but still, no ability to do cool stuff like work in the same file at the same time.
Edited
  • reply
  • like
The reason our team has/will switch to Figma is that we wanted to collaborate with not just designers, but also product owners and developers, who may not be on Macs and/or a Sketch license. The fact that viewers can add comments for free and view files even on a PC was the big "let's switch" moment for us. Doing the same thing with Sketch requires Zeplin or some other tool for commenting and versioning (we currently use Zeplin) but then it always requires designers to upload designs for review … over time, it felt like an extra step not worth taking.
Edited
  • reply
  • like
While I'm biased toward Figma, to be objective Sketch + Zeplin (or something similar) has the advantage of being able to control exactly what you share and source of truth. A Figma viewer can see an entire project, so you can't keep parts of the project "off limits" ... we've had to label pages in Figma to denote what pages developers should look at, and which to ignore. Regardless of what you choose, good luck with your transition!
Edited
  • reply
  • like