What 'Local-First' Actually Means
· 3 min read · Updated
Local-first software runs on your own device and keeps your data and its core features working without depending on someone else's servers. You can still use the cloud, but the app does not need it. You hold the data, the app and local state stay usable offline, and nothing essential disappears if a company does.
The phrase was popularized by a 2019 essay from the research group Ink & Switch, titled "Local-first software: you own your data, in spite of the cloud"[1]. It set out a handful of ideals for software that respects the person using it: your data stays on your device and remains yours, the work is available offline, it lasts for the long run and survives a service shutting down, and privacy is the default.
The essay was written about documents and collaboration, but the principles carry over to any tool that touches your data, including one that moves files between clouds.
Local-first sits between two older ideas. Cloud-first software lives on a company's servers: you reach it through a browser, your data sits in its database, and when the service is down or gone, so is your access. Local-only software is the classic desktop app that could not talk to anything else. Your data was yours, but it was stranded on one machine.
Local-first keeps the good parts of both. Your data and the app live on your device, so you keep control and offline access, and the app still reaches the cloud when you want it to. Compared with cloud-first, the change is who is in charge: you decide when the app uses the cloud, and your access does not depend on it.
Applied to moving files between clouds, which is what Blober does, local-first looks like this:
- The app runs on your computer.
- It connects directly to your providers, so your files are not relayed through a middle service.
- Your credentials stay in a local store on your machine.
- The core work does not depend on the tool's own servers, so it keeps running even when they are unreachable.
- It keeps working for the long run. Blober is a lifetime licence with future updates under the current terms, so the copy on your machine does not stop working when a billing cycle ends.
Your Files, Your Machine, No Middleman walks through the same idea step by step.
Your files and your keys stay on your side, and a tool you run cannot quietly change what it does with data it never receives. A local-first tool does not need a company to stay in business to keep working. With no middle service in the path, no extra party sees your files or holds your credentials. And because the tool moves data between storage you already use, it makes leaving any one provider easier.
Local-first is not anti-cloud, and it makes no claim that servers are bad. Plenty of good software is cloud-first for good reasons. Local-first is about control: the data and the core features belong on your device, and you reach out to the cloud on your own terms. For a tool whose whole job is handling your files, that is a sensible default.
Is local-first the same as offline? Not quite. Working offline is one result of it. Local-first means the app and your data live on your device, and offline use follows from that.
Does local-first mean I cannot use the cloud? No. You still connect to cloud providers. The app just doesn't need the tool maker's own servers in order to work.
How is this different from an old desktop program? An old desktop program was often local-only, stranded on one machine. Local-first keeps your data on your device and still connects to the cloud when you want it.