Another option here @chase-lambert is to try out #datahike, a fork of datascript which supports durability (persisting to disk). At the moment, I think it officially only supports the JVM, but durable JS/browser support is in beta, and writes out the data to an indexeddb.

Using #datahike, or writing an entire datascript db value to localstorage, is fine if you only want the data to be accessible from a single device. But obviously, if you want to share state/data between devices, you either need a central database or some other form of data transfer between clients. Building out an entire SQL data model is doable, and affords some benefits, but is also a lot of work, and you may find it more natural to use either #datomic or #datahike on the back end for this purpose, since then you'll have a more similar data model across the system.

@chase-lambert Hey I work at Roam and I open sourced our original datascript persistence code awhile back https://github.com/panterarocks49/datascript-firebase. It’s very much just a POC but it could give you an idea of how we do it

Great stuff here, I will check these out. Thanks folks!