What Does an "Offline Kanban App" Actually Mean?
Plenty of Kanban tools advertise offline support. Far fewer are actually usable — full read and write, every feature — with the network off. Here's the difference, and why it matters more than it sounds.
Two very different things both get called "offline"
Most cloud-based Kanban apps are online-first with a cache: while connected, they store a local copy of recently viewed boards, and if the network drops, you can usually keep looking at that copy and sometimes queue up a few edits to sync later. That breaks down quickly — creating new boards, adding certain fields, or working for an extended stretch offline is often unsupported or fragile, because the app's real source of truth is still the server.
A genuinely local-first app inverts that: your device is the primary copy of the data, full stop. Every read and every write goes to local storage first, all functionality works with the network fully disabled, and syncing to other devices is a layer added on top — not a requirement underneath.
Why most tools don't do this
It's a genuinely different architecture, not a checkbox. A server-first app can add a cache; it can't easily become local-first without re-architecting how conflicts, permissions, and real-time collaboration work — which is exactly the problem CRDTs are built to solve without a server in the loop at all.
What local-first actually requires
- A real local database — not just a cache of API responses — that the entire app reads from and writes to directly.
- A conflict resolution strategy for when a device reconnects after being offline and its local changes need to merge with everyone else's.
- No blocking network calls anywhere in the core read/write path — the app has to work the same whether or not the network exists.
How Driftboard does it
Every workspace is stored via y-indexeddb, directly on your device, as the
primary and only required copy. There's no "offline mode" toggle because there's no online
mode to fall back from — the app works identically whether you're connected to anyone or
not. When another peer is reachable, changes sync over
an encrypted WebRTC connection; when
they're not, your board is exactly as usable as it was a moment before.
Close your laptop mid-edit, reopen it a week later with no network, and every list, card, checklist, and comment is exactly where you left it — because none of it ever depended on a connection to exist.
Who actually needs this
- Fieldwork and travel — construction sites, flights, rural or unreliable connectivity where "cached and hoping" isn't good enough.
- Privacy-conscious teams who don't want task data sitting on a third-party server, cached or not.
- Anyone tired of a spinner between opening the app and being able to actually use it.
A board that's offline by default, not as a fallback
Free, MIT-licensed, no account required to start.