LocalFirst: You Keep Using That Word
If you’ve been following the local-first scene over the past few years, you already know a good definition for the term “local-first” is hard to pin down. Part of the reason is that most people write software for money … and true local-first software is harder to capitalize. “Local-first” is a direct attack on vendor lock-in of all forms: data, formats, protocols, apps, services, and even environments. But the fact your employer can’t exploit this technology with a new revenue model (yet) is a minor problem.
Local-First Software: Taking Back Control of Our Data | a mini-doc
Local-first Software
Exploring software architecture that returns data to users and enables collaboration in every tool.
Local-first software: You own your data, in spite of the cloud
A new generation of collaborative software that allows users to retain ownership of their data.
Adam Wiggins (Ink & Switch) - Local-First Software: Pragmatism vs Idealism
Convivial design heuristics for software systems
The theme of this workshop is the proliferation of ideas about calling into question the cultural roots of our current programming languages, and the search for alternative paradigms with other cultural bases.
Local-first software: you own your data, in spite of the cloud | Proceedings of the 2019 ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software
As part of the Digital Library's transition to Open Access, new features for researchers are available in the Premium Edition. Click here to learn more.
Exploring the AT Protocol as a legibility layer for local-first software | grjte
Check out the project at https://notebook.groundmist.xyzCross-posted to https://baincapitalcrypto.com/atproto-for-local-first-legibility/ Some people like vim and some people like emacs and some people like something else, and why not have our documents able to be edited in all of those programs? ...
Lunaria 🌘 The missing localization management toolchain for open-source projects
Supercharge your localization workflow
Let It Disconnect: A Local-First Future
“Let it crash” was never really about crashing — it was about designing systems that assume failure and keep working anyway. Local-first software takes the same view about the network, service providers, and open source: assume disconnection, variable latency, service EOLs, and forks to design for convergence and user agency rather than coordination and lock-in.
The Local Relational Technologist
Who can we rely on for meaningful software in our communities?
Exploring interoperability & composability for local-first software | grjte
Check out the project at https://github.com/grjte/groundmist-syncCross-posted to https://baincapitalcrypto.com/atproto-for-local-first-interoperability/ This is the third exploration connecting local-first software with the AT Protocol (atproto). Previously, I explored how atproto can enable new fu...
Building more resilient local-first software with atproto – Day 1 – Local-First Conf 2026
The world's first and best event dedicated to local-first software.
