Keeping notes on three devices without the official sync: the routes people take, and where each one bites

I run the version-control route and I want to be honest about who it suits, because it gets recommended too broadly.

It is superb if you already live in a terminal. The history is real history, I have recovered a paragraph I deleted eight months ago in about twenty seconds, which no sync service would have given me. Conflicts are explicit and resolvable rather than mysterious.

It is a poor recommendation for anyone else, and the failure is not the setup, it is the day something goes wrong. Resolving a merge conflict is not hard for me and is completely opaque to someone who has never seen one, and it will happen on a phone, on a train, when they wanted to write down one thing.

My rule now: recommend it only to people who would have thought of it themselves. Everyone else is better served by the boring drive folder plus the discipline of only writing on one device at a time.

Running the peer-to-peer route for three years, which is missing from the list, and the honest summary: it works, it is free, and it wants a machine that is always on.

Two laptops that are rarely awake at the same time will not sync, and you find out when the conflict files appear. Add a small always-on box and it becomes genuinely excellent.

"Every route is fine on desktop" is the sentence I would put at the top, because it explains why recommendations in this area are so contradictory.

Someone who writes at a desk and reads on the phone genuinely has a solved problem, and will tell you so with total sincerity. Someone who writes on the phone in a queue has a fragile mess. Both are describing the same setup.

The specific thing that breaks is background permission. Phone operating systems are hostile to apps doing work when not in the foreground - for good battery reasons, so a sync that is instant on a laptop happens on a phone whenever the system feels like it, or when you next open the app. That is the whole difficulty in one sentence, and no amount of choosing a better tool changes it, because it is the platform's decision, not the tool's.

Which is also why the paid services can charge: they have engineering dedicated to fighting that, and it is genuinely unglamorous work.

Conflict files are the tell that a route is not working, and people ignore them for months.

Went through three of these and ended up paying, and the maths was not what I expected.

The subscription is roughly the cost of a coffee a month. Over the eighteen months I spent avoiding it I lost: one evening to a conflicted-copy explosion that scattered duplicates through four years of notes, one afternoon setting up a mesh VPN, and an ongoing low-level uncertainty about whether what I was reading on the phone was current.

That last one is the part that does not show up in a comparison and is the reason I switched. Not the time, the doubt. A notes system you are slightly unsure about gets used slightly less, and I could feel myself checking the desktop before trusting the phone.

Not arguing nobody should self-manage this. Arguing that "free" should have the doubt priced into it, because for me that was the expensive line.

Four quirks that are one thing wearing four hats. That is the whole thread in one line.

The background-permission answer is the mechanism I was missing. I had written the phone problems up as four separate quirks and they are one thing wearing four hats.

Also fair on recommending version control too broadly, I have done that to someone and it did go exactly as described, on a train, with a merge conflict.

Adjusting my own summary: if the phone is a writing device, the paid service is buying you a fight with the operating system that you do not want to have. That is a clearer reason than "convenience".