Different Comment Types for Different Use Cases

This would be great! It would reduce drastically the need for annotation plugins/templates such as 1 2 3 4 5

The plugins/templates are great but they pollute the pages with non-design elements. Having notes as native comments would make everything cleaner, but the way it is it’s impossible to differentiate the different comment types.

This is also a major need for our team. Coming from Zeplin where you could easily handle both client communication, dev handoff and internal review feedback, Figma’s comment system feels very archaic. Adding in the ability to color code comments would be a huge win and add back to our productivity and process on this platform.

Agree with all the points made above! We are sharing our creative with several stakeholders and our files have soooo many comments. Would be great if we could have some type of color hierarchy:

• add an email(s) when sharing the file for review with the option of assigning the task (R1 review)
• having an editable color label for said task (UX team Green, copy team yellow)

That way we can distinguish who reviewed it and easily find the group comments within the file. Or when you click on the color label itself it will only show you the feedback shared for that color label/task/team without the other comments crowding around it. This will help our creative team make the appropriate updates to the file and check off what was done without missing an update.

I didn’t have time to read all comments and replies here, but coming from Zeplin, Miro, and Invision - I definitely also need the ability to color-code comments, for example:

• Yellow = General UX note / meeting note
• Blue = For Product
• Red = Question / To Do
• Blue = Resolved (but still displayed)
• Black = For Content/Copy

Agree! In Zeplin, I used to tag myself in the comments, which sent an email to my inbox, which I triaged weekly as ToDo items. This would be great to also do with Figma.

+1 here for a Miro user thinking of switching to Figjam

Another +1. Would love to see these comment types:

• Note
• Task
• Design QA
• Question for Product
• Question for Engineering
• Question for Design

An overview of Zeplin’s annotation system for reference:

The only thing missing that I would like to see is the ability to add frames, components, etc in comments. That way we can, for example, show a particular state of a component inline in the comment.

Not revolutionary as invision has it but I think it was useful having developer comments, regular comments etc. I could see instead of their breakdown maybe: [“C” to add comment] => defaults to regular comment but you can switch to: standard comment (the one you’re on), copy comment, dev comment, or a research question.

possibly a private note too. And maybe it defaults to the mode you select so if you’re spending an hour on copy review you can keep commenting without having to select every time.