From the server to SQLite to reactive Svelte state

Milieu's engineering team describes a local-first design in which a new browser starts as a server-rendered SvelteKit app while a worker downloads the account's SQLite file. The tab switches to the in-browser database (SQLite on WebAssembly, stored in OPFS) only once its per-owner cursors reach the highest server state the tab has seen, so the screen never goes backwards. Pending changes are replayed on the server's state rather than merged with CRDTs. The claims come from the company's own post, with no independent verification.