The case for an offline to-do app in 2026
Sync is now the default assumption for anything you type into a phone. It solves one genuine problem — the same data on two devices — and quietly introduces several others that nobody puts on the feature list.
This is not an argument that sync is bad. It is an argument that for a personal task list, the trade is closer than it looks, and that the honest version of "local-first" is worth understanding before you pick either side.
What sync actually costs
The first cost is an account. To sync you need an identity, which means an email address, a password, a session, a reset flow, and a record on a server that says this person exists and here is what they were planning to do. None of that was needed to write a task down.
The second is a business model. Servers cost money every month, so a synced app needs recurring revenue: a subscription, ads, or data. That is not cynicism, it is arithmetic — and it explains why so many free task apps eventually feel like they are working on someone else's behalf.
The third is failure modes. Offline conflicts, half-synced states, a login that expires while you are on a plane, a server outage that makes your own list unreadable. Every one of those is a moment where the tool asks you to think about the tool instead of the work.
A task list is unusually revealing
Worth saying plainly: your list is not neutral data. It contains the medical appointment you have been avoiding, the interview you have not told anyone about, the argument you need to have, the amount you owe someone. Read end to end it is closer to a diary than to a spreadsheet.
If a review habit is going to work, you have to be able to write things honestly. People edit themselves when they are not sure who else can read it — and a list you have edited for an audience is no longer useful for planning.
What local-first actually means here
Anonymous crash and usage signals are the one exception, and they are worth being specific about: an app that cannot see its own crashes cannot fix them. What matters is the boundary — technical signals yes, task content never. Ours is written out in the privacy policy, including how to have that anonymous record deleted.
The real trade-off, stated honestly
Local-first has a genuine cost, and it is not privacy theatre to admit it: if you lose the phone and you have no backup, you lose the data. There is no support team who can restore your account, because there is no account. There is also no web version, no tablet copy, and no shared list with a partner or a colleague.
For a shared grocery list, that is disqualifying and you should use something else. For a personal planning and review habit — the thing you do alone, twice a day, on the device that is already in your hand — it costs you almost nothing.
The one habit that makes it safe
Export a backup on a schedule you will actually keep. Once a month is fine; attaching it to something you already do — the weekly review, the first Sunday of the month — is better than relying on memory. Save the file somewhere that is not the phone: cloud storage, a laptop, an email to yourself.
Because the export is plain JSON, it has a second benefit that automatic sync never gives you: the data is readable and portable without our app. If Plan Forward disappears tomorrow, your history is still a file you can open, grep and move somewhere else. That is a better guarantee than a promise that the servers will stay up.
Sync may still arrive one day, but only as something you switch on deliberately, off by default, and only if it can be done without us being able to read your list. Until that is true, staying local is the more honest default.