FigmaStrategy6 min readMultiplayer as a distribution strategy
Cursors with names on them did more for Figma than any feature list.
- The surface
- The collaborative canvas and the sharing path: live cursors, the avatar row, the share dialog, link permissions, and the browser view a non-designer lands in.
- What the user wants
- I need the people reviewing this design to actually look at the current version and tell me what they think, without a round of exported PNGs.
The file opens in a browser
Figma files open in a browser from a URL, with no install required for a viewer to see the current state of a design.
Remove the step before the value
Every install is a gate, and the person on the other end of a design review is usually the least motivated participant in the flow. Making the artifact a link means the reviewer's effort is one click. The designer's willingness to share goes up because they are no longer asking a favour.
Named live cursors
Everyone viewing a file appears as a coloured cursor labelled with their name, moving in real time across the canvas.
Social presence
Presence changes the nature of the document from a file to a room. Seeing someone else move makes the work feel live and makes review feel like a conversation rather than an inbox item. It also creates mild accountability, since being in the file is visible.
The avatar row
Avatars of current viewers sit in the toolbar, and clicking one follows that person's viewport around the file.
Shared context on demand
Most of the cost of a design review is establishing which frame everyone is looking at. Spectating someone's viewport collapses that negotiation into one click. It turns a synchronous call into something closer to sitting next to them.
The share dialog
Sharing offers a link with a permission level attached, with view access available to people who are not paying seats.
Asymmetric pricing along the collaboration edge
Charging the people who create and letting the people who consume in for free is what lets a file spread through an organisation. Every reviewer who opens a link is an unpaid, low friction impression of the product. The moment one of them wants to edit, the pricing model is already waiting.
Comments pinned to the canvas
Reviewers can leave comments anchored to a specific point on a frame, visible to everyone in the file.
Feedback in context
Feedback loses most of its value when it is separated from the thing it refers to, which is why review threads in chat are painful. Pinning the comment to a coordinate removes the translation step for both sides. It also gives non-designers a real job inside the tool.
Version history as a safety net
Figma keeps a version history of the file, and named versions can be restored.
Reversibility lowers the cost of letting people in
Real time editing is frightening if a mistake is permanent, and fear is what keeps files locked down. A restorable history makes granting edit access a cheap decision. Collaboration spreads only as far as the owner's confidence that nothing can be destroyed.
The free side is the distribution
What not to copy
- Presence is also surveillance. A cursor with your name on it tells your colleagues when you opened the file and how long you sat on one frame, and there is no polite way to lurk.
- Link permissions are easy to get wrong in the direction of over-sharing, and the dialog makes the broad option feel like the normal one. For confidential work that is a real exposure.
- Comments anchored on the canvas scale badly. A frame with forty pins becomes unreadable, and the product gives weak tools for deciding which feedback has been resolved and which was never addressed.
- Free viewers are a growth engine and a support burden. Non-designers dropped into a professional canvas with no orientation often leave vague feedback, which shifts work onto the designer.
The takeaway
Decide which side of the collaboration you charge for, because the free side is your distribution channel.
Finished the teardown? Bank it and the day counts toward your run.
Where the principles come from
- Crossing the Chasm (adoption and beachheads), Geoffrey Moore
- The Design of Everyday Things (feedback, visibility of system state), Don Norman
- 10 Usability Heuristics for User Interface Design, Jakob Nielsen, NN/g
- Working in Public (participation and permission), Nadia Eghbal
Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.