Ownership before synchronisation
Local-first thinking starts with a straightforward question: can a person keep using their information when the network disappears? The answer shapes storage, export and failure handling long before it shapes a sync button.
It is not a promise that every app can avoid a server. Shared work, backups and AI providers introduce real trade-offs. Name them instead of hiding them behind a slogan.
For an early prototype, test one offline path and one recovery path. Disconnect, make a change, reconnect, and inspect what happened. A reliable small workflow teaches more than an elaborate architecture diagram. Portable formats such as Markdown also make an exit path easier to explain.
Original topic source: movofo — Local-first or bust. This is a short original adaptation of the topic, not a quotation or reproduction of the source article.