One could implement a write queue and caching for the front end. That might sound like a lot of work to go through to avoid moving to a proper multi-user datab

One could implement a write queue and caching for the front end. That might sound like a lot of work to go through to avoid moving to a proper multi-user database. But given that writes are probably done through a handful of API endpoints, it's probably not really that much work to implement.