Skip to content

offline

1 post with the tag "offline"

What 'Local-First' Actually Means

What local-first software means, software that runs on your device rather than a remote server

Local-first software runs on your own device and keeps your data and its core features working without depending on someone else's servers. The cloud is still welcome, but it is optional rather than required. You hold the data, the app and local state remain 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 instead of vanishing when a service shuts down, and privacy is the default rather than an upgrade.

The essay was written about documents and collaboration, but the principles travel well to any tool that touches your data, including one that moves files between clouds.

It helps to place local-first 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. The difference from cloud-first is who is in charge: the cloud serves you, instead of holding you.

Applied to moving files between clouds, local-first has a clear shape:

  • The app runs on your computer, not in a browser tab on someone else's servers.
  • 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.

This is the same idea described in Your Files, Your Machine, No Middleman, set out as a principle here rather than step by step.

  • Ownership. Your files and your keys stay on your side. A tool you run cannot quietly change what it does with data it never receives.
  • Longevity. A local-first tool does not depend on a company staying in business to keep functioning. What works today keeps working.
  • Privacy. With no middle service in the path, there is no extra party to see your files or hold your credentials.
  • No lock-in. Because the tool moves data between the storage you already use, it makes leaving any one provider easier, not harder.

Local-first is not anti-cloud, and it is not a claim that servers are bad. Plenty of good software is cloud-first for good reasons. Local-first is a statement about control: the data and the core features belong on your device, and the cloud is something you reach out to on your terms. For a tool whose whole job is handling your files, that is a sensible default.

Is local-first the same as offline? Offline is one of its results, not the whole idea. Local-first means the app and your data live on your device; working offline follows from that.

Does local-first mean I cannot use the cloud? No. It means the cloud is optional for the app to function. You still connect to cloud providers; you are just not dependent on the tool's own servers.

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.