Local-First Software
The cluster centers on discussions of local-first software, including its principles of offline access, data ownership, and synchronization challenges without central servers, with references to key articles and real-world examples.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Its better to design, implement, and use local-first software: https://www.inkandswitch.com/local-first/
Related idea to local-first: https://stephango.com/file-over-app
"Local-First software." Isn't that just a desktop application that syncs?
Local-first software is the future:[1]Local-First Software:You Own Your Data, in spite of the Cloud:https://martin.kleppmann.com/papers/local-first.pdf
You may be interested in the concept of “local-first” software — https://www.inkandswitch.com/local-first/Data storage concerns are orthogonal to app distribution method, as others have pointed out.
Maybe you're missing some other context.Here's an article about local-first software: https://www.inkandswitch.com/local-first/Here's an article about why you might want this: https://medium.com/all-the-things/a-web-app
Local-first is the future. Most cases don't even need a backend to self-host.
Me neither. Considered we are talking about collaborative network applications, you are loosing the single-source-of-thruth (the server database) with the local first approach. And it just adds so much more complexity. Also, as your app grows, you probably end up to implement the business logic twice. On the server and locally. I really do not get it.
Local-first apps should not need hosting.
One of the points of the article was that storing data completely on the net, instead of synchronising local and remote versions, is not in their vision of the future because "users shouldn't have to worry whether they're online or not", so what you proposed is specifically what they're avoiding.