Real-Time Collaboration & Comments

Figma

Chapter 8 · Real-Time Collaboration & Comments

Chapter 7 built a clickable prototype. This chapter covers what happens once that prototype (or any design file) needs to actually be reviewed by other people — the same real-time, multiplayer collaboration Chapter 1 introduced as Figma's own foundational architecture, put to practical use here.

Multiplayer Cursors: Seeing Where Everyone Else Is Working

Every person currently viewing or editing a file shows up as a labeled cursor moving live on the canvas, the same way Chapter 1 described multiple people editing the exact same design simultaneously. A designer can see exactly where a teammate is currently looking or working, without needing to ask or interrupt.

Comments: Leaving Feedback Directly on the Design

A comment can be pinned to a specific location on the canvas — a particular button, a spot on a layout, a whole Frame — attaching written feedback directly to the exact element it's about, rather than describing it separately in a message elsewhere. Anyone with access to the file can add a comment, reply to an existing one, or tag a specific teammate directly.

Resolving and Threading Comments

A comment thread keeps all replies to one original comment grouped together in order, and marking a thread as resolved clears it from the active view once the feedback has been addressed, keeping a busy file's own comment history organized rather than an ever-growing, undifferentiated pile of open items.

Sharing a Prototype Link for Review

A prototype (Chapter 7) can be shared as a standalone link that lets anyone click through it and leave comments directly on specific screens as they go, without needing full edit access to the underlying file — a natural fit for gathering stakeholder feedback on a design's actual flow, not just its individual screens in isolation.

The Same Underlying Model as Google Workspace

Figma's own multiplayer cursors and live comments are the same real-time collaboration model Google Workspace's own Chapter 2 described for shared documents — multiple people working on one live, shared file, seeing each other's presence and feedback appear instantly, rather than exchanging separate copies and reconciling changes afterward.

Collaboration in Penpot

Penpot supports the same multiplayer cursors and pinned comments, under closely matching terminology, continuing this course's own recurring theme that Penpot's own deliberate similarity to Figma extends well beyond just the drawing tools.

Figma feature	Google Workspace equivalent (from `gworkspace1`)
Multiplayer cursors	Real-time collaboration (multiple cursors, one document)
Pinned comments	Comments pinned to specific text/cells
Resolving a thread	Resolving a comment thread
Shareable prototype link	Sharing a document link for review

This same shared link matters again in Chapter 9

A prototype's own shareable link is exactly what a developer opens to enter Chapter 9's own Dev Mode — the same file, viewed through a different lens built specifically for extracting implementation details rather than leaving design feedback.

Figma comments are annotations, not proposed edits

It's tempting to assume Figma's own comments work like Google Workspace's own Suggesting mode from that course's own Chapter 3 — a formal proposed change that can be explicitly accepted or rejected into the actual document. Figma comments are purely annotations: written feedback pinned to a location, with no mechanism to actually apply, accept, or reject a specific design change directly from the comment itself. Acting on a comment's feedback still means a designer manually going and making the actual change in the design — the comment only communicates what should happen, it doesn't perform it.

Hands-On Exercises

Exercise 1

A product manager wants to leave feedback on a specific button's color without disrupting the designer's own separate edits happening elsewhere in the same file at the same time. Using this chapter's own material, explain how Figma's own model supports this directly.

📄 View solution

Exercise 2

A stakeholder leaves a comment suggesting a button should be blue instead of green, then is confused when the button doesn't change color on its own. Using this chapter's own warning box, explain why this is expected behavior.

📄 View solution

Exercise 3

Explain, using this chapter's own material, why Figma's own multiplayer cursors and comments are described as the same underlying model as Google Workspace's own real-time collaboration, rather than a coincidentally similar but unrelated feature.

📄 View solution

Chapter 8 Quick Reference

Multiplayer cursors show everyone currently viewing or editing a file, live, in real time
Comments pin written feedback directly to a specific location on the canvas
Resolving a comment thread clears addressed feedback from the active view
A shared prototype link lets reviewers click through and comment without full edit access
Comments are annotations only — unlike Google Workspace's own Suggesting mode, they don't propose changes that can be directly accepted or rejected