Almost every app you use today stores your data on someone else's server. Your photos live on Apple or Google servers. Your documents live on Microsoft or Google servers. Your messages live on Meta servers. This arrangement is so normal that most people never question it. But a growing movement in software development is questioning it seriously, and the result is a new category of applications called local first software.
What Does Local First Mean?
Local first means your data lives on your device first, and the cloud is optional. The application works completely without an internet connection. When you are connected, it syncs. When you are not, it keeps working. Your data never disappears because a company shut down their servers or changed their pricing. You own your data in a literal sense because it physically lives on hardware you control.
Why Is Local First Software Hard to Build?
This sounds obvious when you say it out loud. Why would you design it any other way? The answer is that building local first software is genuinely harder than building cloud first software. Synchronizing data across multiple devices without a central server creates complex technical problems around conflicts, ordering, and consistency. If you edit a document on your laptop while offline and someone else edits the same document on their phone, how does the app decide which version is correct when you reconnect? Solving that problem elegantly is the central engineering challenge of local first design.
What Does Zenith Show?
A project called Zenith, built by a developer named surprisetalk and currently trending on Hacker News, demonstrates local first principles in a planetarium application. It is a real time interactive star map that runs entirely in your browser with no server calls during use. The developer describes it as local first and fixed viewport, meaning it loads once and then operates entirely from data already on your device. You can take it offline and it keeps working.
Why Does Local First Matter?
The local first movement matters beyond just apps for developers. It represents a philosophical shift about who owns your digital life. In a cloud first world, the company that hosts your data can change their terms, raise their prices, get acquired, or go bankrupt, and your data becomes inaccessible or disappears. In a local first world, your data is yours regardless of what happens to any company.
What Is the Future of Local First Software?
As internet connectivity becomes assumed and cloud storage becomes commoditized, the designers who figure out how to build software that respects user ownership without sacrificing collaboration will define the next generation of applications.
What Tools Exist for This Today?
The local first movement has moved past academic papers into working software. Libraries like Automerge and Yjs give developers a practical way to handle the conflict problem described above, letting multiple devices edit the same data offline and merge changes automatically when they reconnect. Note taking apps, drawing tools, and even some project management software now ship with local first architecture under the hood, often without users ever knowing the term. The technology is maturing quietly while most of the software industry still defaults to cloud first design out of habit rather than necessity.
Does Local First Mean No Cloud at All?
Not necessarily. Most local first applications still use a server, but the server's role shifts from being the source of truth to being a sync helper. Your device holds the real data and can function completely without the server. The server exists only to help multiple devices agree on the latest version when they are online. That distinction, cloud as convenience rather than cloud as dependency, is the entire philosophy in one sentence.