Design Moved Into the Browser: What Figma Changes About Working Together

The annual design-tool surveys have confirmed what our own project workflow quietly settled a while ago. Figma’s browser-based, multiplayer model has shifted the industry’s center of gravity, and the drafting table we work at now lives at a URL. The file stopped being a deliverable and became a room. Now you have to decide who gets a key.

The industry conversation about this shift keeps running as a feature comparison. Vector tools versus vector tools, prototyping, plugin ecosystems. That conversation misses the actual event so completely that we want to file the correction formally. The change that matters is not a feature. It is ontological. Design stopped being a file someone owns and became a place people meet.

A Sketch file was a document. It lived on a designer’s machine, traveled by export, forked by duplication, and embodied a workflow in which design was produced in private and revealed in ceremonies. A Figma file is a location. Everyone relevant is looking at the same living artifact, at the same time if they wish, cursor by named cursor. The entire social structure of design work reorganizes around that fact. This post is the field report from our own projects: what actually changed, what it costs, and the process hygiene the new physics requires. Most reader organizations are living this shift mid-transition, and the transition is where the lessons are cheapest.

What multiplayer actually changed, on real projects

The concrete inventory, from two years of running engagements this way. Stakeholder feedback moved into context. Comments attach to the actual element at the actual size in the actual flow. That replaced the annotated-PDF ritual, its email threads, and its version confusion with conversation that lives where the work lives. Feedback got measurably better when stakeholders stopped describing locations, ‘the blue box on the third page,’ and started pointing.

The version-numbered file graveyard simply ceased. Homepage_v7_FINAL_revised_2 is extinct as a category. There is one file, its history is the version system, and the archaeology of ‘which version did we approve?’ ended without ceremony.

Design systems distribute as living libraries. Shared libraries push updates to every consuming file. You can see who uses what. The system team ships the way software teams ship, which is what treating the system as a product always implied. And developer handoff lives at a URL that is never stale. The inspect tooling replaced the redline-export genre. The handoff document, a snapshot aging from the moment of export, became a reference that is simply always current. That collapsed a whole category of build-phase discrepancy we used to bill hours reconciling.

The democratization, priced honestly

Now the cost column, because pretending the shift is free would be dishonest to the organizations mid-transition. More voices in the file means more voices in the file. The same access that improves feedback also brings costs. The executive cursor hovering over work in progress. The comment thread that becomes design-by-committee. The chill on exploration when every rough draft is visible to the whole company in real time.

The document era’s privacy was not only pathology. It was also the studio, the protected space where unfinished thinking could be unfinished, and multiplayer abolishes it by default.

The correction is not tool settings alone, though draft-space conventions help. It is process, designed on purpose. Which files and pages are open studio versus review-ready. When stakeholders are invited in, and, as important, when the invitation ends. Comment rules that separate observation from direction. Above all, explicit decision ownership: whose voice decides, named per project. The multiplayer file makes every opinion equally visible. So it forces a question the document era answered implicitly through file custody: who decides? That is the transferable law here, and it reaches well beyond design tooling. Multiplayer tools surface process gaps that single-player tools hid. The tool did not create the ambiguity about decision rights. It revealed it, at cursor speed. Teams that meet the revelation with process, rather than nostalgia or tool-blame, convert the transparency into the asset it is.

The hygiene we now set per project

• File and page conventions, written down: the studio-review-approved structure, named the same way everywhere. The state of any file should be clear from its location, so nobody reviews rough work by accident.

• Comment protocol, agreed at kickoff: what comments are for (questions and observations) and what they are not for (directives that bypass the decision owner). Threads get closed by the owner, not abandoned, and the file gets swept on a cadence.

• Decision ownership, named in the project charter: one accountable owner per decision domain, visible to everyone in the file. Visibility without ownership is how committees happen.

• Review sessions, still scheduled: ambient access does not replace the structured walkthrough. The presentation moment (context, rationale, recommendation) remains where design earns its decisions. The always-open file makes protecting that moment more necessary, not less.

Two wider patterns

First, the browser keeps absorbing professional tools. It has now absorbed design tools, after documents, spreadsheets, and coding tools. It runs real-time shared vector editing at native quality. The tech behind it (WebGL, WebAssembly, the sync engineering) is itself proof of the web as an app platform. What the browser absorbs, it tends to keep. Plan tool strategy accordingly.

Second, note where the disruption actually landed. Not in features. The incumbent tools drew vectors competently. It landed in workflow: who can see, who can speak, where the work lives, and what coordination costs. That is where it always lands.

That is the lens we recommend for evaluating every ‘X, but collaborative’ pitch the SaaS economy will deliver over the coming years. Ignore the feature matrix. Ask what the multiplayer physics will surface about how your organization actually decides things. The tool will not answer that question. It will, with cursor-level precision, force it. The organizations that answer deliberately will be the ones for whom the place where people meet is also a place where work gets finished.