We’ve written about how we handle conflict resolution in multiplayer before. Figma’s central paradigm is being a browser-based, cloud-based, and realtime application.

But as it often happens, interesting challenges lie not in individual features, but the interaction between them. When the user next reloads this document in a new tab, the changes will be restored and uploaded to the server.īut why does such a feature warrant a blog post? “Saving the file to disk periodically” isn’t exactly a groundbreaking innovation. With our newly expanded autosave system, edits now save to disk when a document becomes disconnected from the server so changes to the document persist-even if the tab with Figma closes. Until recently, users ran the risk of losing data should something happen to their computer or browser while offline. In online applications like Figma, we flush changes to the server as soon as they’re made offline changes can’t sync with the server until you reconnect to the internet.

After all, we’ve all had an unlucky circumstance in which we closed the application accidentally, it crashed, or we lost power-and hours of work. It wasn’t so long ago that software made you hit the save key obsessively. Engineer Rudi Chen takes us behind the scenes of building this update: how we made product decisions, managed large merge conflicts, and navigated the complexities of Figma’s multiplayer technology.

We recently expanded autosave in Figma so you can work offline without worrying about losing changes.

Bullet force multiplayer account issues