Today I learned about local-first software, and honestly, it feels like discovering a secret resistance movement hidden in plain sight. Local-first is the idea that your data belongs to you first, that your apps should work offline, prioritize your local copy, and sync as a courtesy. It’s not just a new technical approach; it’s almost anarchist in spirit.
Think about it: for years, SaaS apps have lured us into “convenient” cloud services, only to slowly enshittify them. Reducing control, introducing dark patterns, and monetizing every bit of your attention and data. Right now it feels almost as if we’re held hostage of such subscription fees, which get more and more expensive every time, and in return give us access to less features.
Local-first flips that script. It’s a push for self-ownership. Developers and users alike reclaim agency by designing systems where:
Instead of begging platforms to respect us and stop usurping our data, the movement is building a new standard that makes lock-ins a thing of the past.
The philosophy here feels unmistakably anarchist. Local-first isn’t about chaos; it’s about sovereignty. Users and developers jointly assert ownership over digital tools and data. It rejects centralized control while offering an alternative that is more resilient, more customer-centric, and inherently less exploitative.
We can see this trend creeping into projects like Automerge, Obsidian and Figma that started adopting Local-First goals in their features. A very nice list was compiled in a GitHub repo by alexanderop.
It’s a movement that for me says: if big tech is enshittifying everything they touch, the answer isn’t cozying up to them, it’s building something that doesn’t need them.
I’m looking forward to dive deeper into this and learn much much more.