Skip to main content
Question

Making it easier for developers to consume Figma files


Suzanne4

Hello,

My team just switched from a Sketch/Abstract combo over to Figma, mainly because of the auto layout engine and the flexible component system.

One thing I am somewhat concerned about is how collaboration, and communication, with product owners and developers works in Figma - or I should say, doesn’t work.

In Abstract we prepared Collections, where we specifically selected the relevant artboards. Links to those collections, and sometimes even directly to artboards, were then shared on Jira, etc. People visiting those links always only had 1 artboard (=screen/state/whatever) in front of them and could comment and annotate away. Switching to a different artboard was always a deliberate choice and a very obvious user experience. Also, you would only ever see comments that were posted on that specific artboard.

In Figma, on the contrary, you have free navigation on the infinite canvas of a page. Yes, you can share direct links to artboards and on visiting those links you are taken directly to that artboard. However you will still have to navigate freely to move between artboards, zoom in and out, etc. This is much more complex and overwhelming than having always only 1 artboard on the screen and moving via arrow left/right. Furthermore the right sidebar for comments will show all comments on the whole page (not only the artboard in view) which makes the comment function more overwhelming as well.

is this something you’re working on? Or perhaps I have I overlooked some clever functionality?

Designers - have you maybe been in the same boat and found a good solution? Any best practices you can share are super appreciated!

Many on our team are regretting the choice to switch. Now with the Adobe purchase, perhaps justification to return to Sketch.

3 replies

WarrenC
  • 1 reply
  • October 3, 2022

I too am VERY much missing the control Abstract provides with regard to presenting work coherently. Figma is a hot mess. We looked into Zeplin which does much the same thing, but unfortunately is too $$ for our organization. Figma, please tell us this is on your roadmap.


KCW
  • 2 replies
  • November 3, 2022

We have the same problem. It’s weird this is not a feature yet. Why would you want to share the entire document? POs want to focus on specific screens instead of having the whole document (with all the comments) in front of them… @Josh


Suzanne4
  • Author
  • 2 replies
  • November 10, 2022

Here’s a proposed workaround for this shortcoming.

The problem:
There is no way to save and publish a “collection” of specific frames the make up a user flow for handoff to dev that they can:

click through, one frame at a time
comment on
inspect

The solution:
Add options for the prototype preview which already provides a way to click through the frames that make up a user flow. Then provide controls that allow:

comments to be turned on or off
viewing of inspect on or off

Perhaps when publishing the prototype there is a choice to “publish as” either a prototype, or collection for dev hand-off.

In response to this post (my team has the same problem) Sketch/Abstract => Figma - concerned about PO and Dev handoff


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings