Files
figcraft/docs/collaboration-parity.md
T
BFlatandClaude Opus 5.5 94ff3d4df6 M9: collaboration: per-user undo, rejections, reconnect (#105)
* M9: collaboration: per-user undo, rejections, reconnect

Step 3 of docs/collab-protocol.md, the parts that don't need the transport:

- Per-user undo and redo (figcraft_collab::Client::{undo, redo}): each undoable batch is a step
  (values before/after by target, nodes created/deleted). Others' batches ordered after the step
  take its targets for good; creates invert to deletes (not when others built inside), deletes
  re-create the subtree. An undo or redo waits for every earlier batch and is remade from the
  confirmed state when it goes out; derived data follows as a follow-up batch.
- Rejections: refused batches leave the history (with an undo waiting on them) and queue a
  Notice; the engine shows it through Session::message (the UI's toast).
- Offline queue and reconnect: Hello.resume {session, client_id, seq}; the server keeps a
  bounded log and answers with the missed batches or a snapshot, plus what it did with the
  client's batches (processed {last_batch, refused}); queued batches then go out.
  Server::state / restore persist the session (client-id counter, log, session id).
- Presence carries editing_text {node, caret, selection}.
- Engine: documents in a live session (LiveDoc, Session::collab_*): commands, gestures and
  groups sync as one step each; edit.undo / edit.redo route to the per-user history; remote
  edits show under a gesture in progress. Outside a session snapshot undo is unchanged.
- Sim: dropped connections, undo/redo, and a checker that no undo reverts a change by someone
  else its author had seen. New tests in undo_tests, reconnect_tests, collab_live_tests,
  collab_undo_tests.
- CLAUDE.md / AGENTS.md: collab in the L2 layer list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* M9: collaboration wording in the progress docs after per-user undo and reconnect

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* M9: protocol doc: what the engine's live-session tests cover

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-11 03:19:24 +07:00

3.2 KiB
Raw Blame History

Collaboration parity

Last reviewed: 2026-10-10 · Last updated: 2026-10-10 · Change: minor (the multiplayer core landed in #103) · Target: Figma Design (desktop app 126.10.7)

Figma is multiplayer first; FigCraft is local first. Ready ~12% (estimated): comments and version history work inside one file on one machine; the real-time collaboration core landed in #103 (sync model, server ordering, client reconciliation, convergence tests) without networking, so nobody can co-edit yet (collab-protocol.md). Remaining: 55–110 h (multiplayer 45–90 h, shared libraries 10–20 h), plus branching 8–15 h.

Feature Figma FigCraft Hours
Real-time co-editing yes core built, no networking (#103): client-scoped ids, per-property change sets with fractional positions, server ordering and validation, optimistic clients, binary messages; randomized multi-client convergence tests over real commands. Live sessions over the network landed (crates/collab-net): the WebSocket transport (keep-alive, size and rate limits, reconnect with backoff), hosting from the app (this machine or the local network) with invite links, live cursors with name tags, selections, avatars and follow, collab.* commands. Document sync between apps works over them (the host's server orders every batch; guests open the host's file as a new tab). Undo is per person (only your own steps, others' later writes left alone), refused edits roll back with a toast, and a reconnect resumes as the same client with what it missed (or a snapshot) and sends what was made offline. Left: browser client, standalone server 25–55
Live cursors, selections, viewports; follow / observation mode; spotlight yes no (presence messages encoded; no UI or transport) 8–15
Cursor chat, audio, high-fives yes no 4–8
Share links, permissions (view / edit), teams and projects yes no 8–17
Comments: pins on frames and layers, threads, reactions, @mentions, resolve, unread, search and filters, links, in the presenter yes (shared) done, local: stored in the file, your name from Preferences (shared once multiplayer lands)
Version history: named versions, autosave checkpoints, view before restore, restore, duplicate yes (cloud) done, saved in the .figcraft file —
Branching and merging yes (paid plans) no 8–15
Team / organization libraries yes local library files only (components-parity) 10–20
Notifications, activity yes no with sharing

Revision history

Date Change Summary
2026-10-10 minor Merged main after #101–#103: WASM plugins (plugins area 0% → 35% breadth, 20% ready; ecosystem 5% → 20%) and the multiplayer core without networking (multiplayer 5% → 15% breadth, 5% ready; collaboration 8% → 12%); menu breadth 97.5% → 98.5% (200/203); ready for real work ~46% → ~47%; full parity 420–790 h → 390–745 h; beta 210–380 h → 200–365 h. Fixed the stated weight sums (areas 1–16 sum to 94, total 113; percentages were already computed with those)
2026-10-10 major Created from the 2026-10-10 re-measure