Croquet. A Unique Collaboration Architecture
summary
Croquet claims synchronized, bit‑identical multiuser state by running the client-side TeaTime kernel on every device while a tiny reflector timestamps events and forwards them; all app data is end‑to‑end encrypted so servers can’t read it. The JavaScript SDK (Model/View/Session) plus examples—hello‑world sync, Wide Wide World, a WebAssembly Rapier physics demo, a Q collaborative desktop, and a Raspberry Pi “Croquet‑in‑a‑Box” reflector—are working now; live coding, snapshots for joiners, and plans for many 5G edge reflectors complete the stack.
AI-written summary · about
chapters (17)
- 0:00Croquet introduction
- 1:29Real-time multi-device sync demo
- 2:12Engelbart’s collaborative vision
- 4:56Croquet architecture principles
- 6:43Virtual computer synchronization
- 9:06Simple collaborative app demo
- 11:14Model-View-Controller breakdown in Croquet
- 17:19Client-side vs server models
- 21:12Bandwidth and latency benefits
- 23:38Global reflector network
- 26:31Croquet applications
- 29:37Rapid development with SDK
- 31:39Live-coding in Croquet
- 35:04Croquet history
- 37:23Old vs new Croquet
- 38:42Croquet future plans
- 39:25Closing thoughts
related talks
30mEverything's better with friends
31mEverything's better with friends
23mMoQ: Not Another Tech Demo
57m🚨 Live On the Edge 🚨
44mReal-Time Multi-User State Management for the Collaborative Web
28mReal-time collaboration with Rails
38mReal-time Communication on Mobile
34mMaking Webapps Collaborative with Composable CRDTs