Skip to content
For the complete documentation index, see llms.txt.
Updated (published July 24, 2026) · 4 min read

What is a local-first task manager? A quick test

A local-first task manager keeps tasks on your device, loads instantly, and works offline before syncing. How it differs from cloud apps, plus a quick test.

A brown bear resting in a hammock between pine trees.

Short answer: A local-first task manager keeps the working copy of your tasks in a database on your own device as well as on a server. Reads and writes happen locally first, so views open instantly and keep working with no connection at all. A background sync engine then reconciles your changes in order, so you never resolve a conflict by hand.

Why it matters for a task list

Task managers live or die on two things: whether capture is reflexive, and whether you trust the system enough to stop tracking things in your head. Architecture decides both, more than the feature list does.

Capture has almost no tolerance for waiting. If adding a thought costs a spinner you start batching, then skipping, and a system that isn’t fed stops being useful. Trust is closer to binary. The first time your list won’t load before a meeting, part of your brain quietly resumes remembering everything, which is the job you handed the app.

Local-first takes the network out of the critical path for both. Reads render from a store already on your device, and writes commit locally before anything touches a server. You never wait on the network to see your list or save a task, and the app still works on a plane, in a basement, or while the vendor’s servers are having a bad day.

“Works offline” hides three different things

Plenty of task apps claim offline support, and the claim covers at least three different things. The weakest is a read-only cache: you see stale lists, but changes fail or silently queue. Then there’s an offline mode, where changes queue for later but the app is visibly degraded and conflicts can surprise you at sync time.

Local-first has no mode. Offline is the default path and the network is an extra, so every feature behaves the same with the connection off. Cloud-first apps run the other way round: the server is the source of truth, and offline arrives later as a cache and a write queue.

Todoist documents an offline mode. If you’re logged in before the connection drops, you can add, change, and complete tasks, and they sync when you’re back online. Its warning is the cloud-first tell: close the app or clear local data before that sync, and the changes are deleted (Use Todoist while offline, checked 27 September 2026). TickTick’s help centre has no article on offline use, so its own documentation doesn’t say what works without a connection. That describes each app’s design and says nothing against either one.

How to tell which one you have

You don’t need a spec sheet. Put your phone in airplane mode, force-quit the app, reopen it, add a task, complete another, and search for something old. A local-first app doesn’t notice, and syncs the moment you reconnect. A cloud-first app tends to show stale data, fail or silently queue the writes, or come back with empty searches.

Where Done Bear fits

Done Bear is local-first on every platform, web app included. Tasks live in a local store, so views render instantly from disk and every write commits locally first. From there it goes through a server-sequenced sync protocol that orders each edit and streams updates to your other devices and teammates in real time.

On iPhone, and in a browser where it has loaded before, it passes the airplane-mode test above. The Windows, Mac, and Linux apps load the web app when they start, so they need a connection to open, then keep working if it drops.

Offline edits replay in order when you reconnect, so even shared workspaces converge without anyone resolving conflicts by hand.

Local-first usually gets pitched as a solo-app trait, but it’s also how Done Bear does collaboration: an ordered server action log reconciles offline edits, including explicit server-wins handling when two devices change the same field. The full sync architecture explains the outbox, retry, catch-up, and recovery paths.

Working offline is the easy half. The hard half is agreeing on the order of everything that happened while you were away.

What works with no connection on iPhone, the web and the desktop app is on the Done Bear offline task manager page, next to what Todoist, TickTick, Things 3 and Microsoft To Do document about offline use. There is also how it compares to TickTick and Todoist. The free plan is enough to run the airplane-mode test yourself.

Start free, works offline

The list lives on the device and syncs when you are back. Free up to 250 tasks. No credit card.

Get new posts by email

New writing on GTD, local-first software, and building a calm task manager, sent when it is published. Nothing else, and you can leave any time.