You open your laptop to finish yesterday’s draft. It’s gone. Or worse: it’s there, but the last three paragraphs you wrote on your phone have vanished. The culprit isn’t user error—it’s how productivity apps handle sync conflicts when you edit the same document on two devices without waiting for the cloud to catch up.
This happens more often than most solo operators realize, and the mechanics vary by app. Some tools silently overwrite. Others create duplicate conflicted copies you’ll never see unless you go looking. A few delete outright.
How sync conflicts actually happen
Most productivity apps—Notion, Obsidian, Apple Notes, Evernote, Bear—use eventual consistency models. When you edit a document on your phone, the app saves locally first, then pushes changes to the server when connectivity allows. If you open the same document on your laptop before that sync completes and start editing, both devices now hold divergent versions.
What happens next depends on the app’s conflict-resolution logic:
- Last write wins: The most recent save overwrites everything else. Apple Notes and Notion default to this. If your laptop autosaves two seconds after your phone, the phone edits disappear.
- Conflicted copy creation: Obsidian and Evernote generate a duplicate file with a timestamp suffix (e.g., Draft (conflicted copy 2026-07-07)). The original keeps the laptop version. Your phone edits live in the copy—if you notice it exists.
- Operational transformation: Google Docs and Dropbox Paper merge character-level changes in real time. This works well for collaborative editing but can still produce nonsense if two devices edit the same sentence simultaneously while offline.
Notion’s block-based architecture adds a wrinkle. If you edit different blocks on different devices, they merge cleanly. Edit the same block, and last write wins for that block only. You can lose a paragraph while the rest of the page survives.
When sync fails silently
The worst-case scenario isn’t a visible conflict—it’s when the app gives no indication anything went wrong.
Apple Notes, in particular, has a reputation for this. If you edit a note on your iPhone, lock the screen before it syncs (usually 5–10 seconds), then open the note on your Mac and keep typing, the Mac version often wins. The iPhone edits vanish with no warning, no conflicted copy, no recovery option unless you’ve enabled iCloud backups and know to check Recents.
Obsidian with third-party sync plugins (Syncthing, Dropbox, iCloud Drive) can hit the same problem. If the file system syncs mid-save, you get a corrupted Markdown file—usually just the YAML frontmatter survives, and the body text turns into a jumble of merge markers. Obsidian’s built-in Sync service ($8/month for solo use) includes conflict detection, but the free version paired with file-based sync does not.
How to avoid losing work
The safest rule: never edit the same document on two devices within a 60-second window. Most apps sync within 10–30 seconds under good connectivity, but lag on slow networks or when backgrounded on mobile.
Practical steps:
- Wait for the sync indicator. Notion shows a small checkmark in the top right when saved. Obsidian’s Sync plugin shows a cloud icon. Apple Notes has no reliable indicator—assume 15 seconds minimum.
- Search for “conflict” monthly. If your app creates conflicted copies, they pile up invisibly. Obsidian users can run a vault-wide search for
conflictin filenames. Evernote buries them in the same notebook as the original. - Enable version history where available. Notion keeps 30 days of page history on the free plan (unlimited on paid). Obsidian Sync keeps 90 days. Apple Notes has no built-in versioning—use Time Machine or iCloud.com’s file recovery if you’re on Mac.
- Draft in single-device contexts when stakes are high. If you’re writing a client proposal or a product launch email, keep it on one device until it’s done. The productivity gain from cross-device access isn’t worth the risk of losing three hours of work.
The tools that handle this best (and worst)
Google Docs remains the gold standard for conflict-free editing. Real-time operational transformation means you can edit on your phone, close it mid-sentence, open your laptop, and pick up exactly where you left off. The tradeoff: slower performance on long documents and no offline editing beyond basic text entry.
Obsidian with paid Sync is the best option for Markdown users. Conflicts generate visible banners and preserve both versions. The $8/month cost is reasonable if you edit across three or more devices regularly.
Apple Notes is the riskiest for operators who rely on it. No conflict detection, no version history you can trust, no export-and-compare workflow. If you use it, treat it as ephemeral—fine for grocery lists, bad for anything you can’t afford to lose.
Notion splits the difference. Block-level merging works well most of the time, but when it fails, the lack of a conflicted-copy safety net means you’re dependent on page history. Check the changelog obsessively if you draft across devices.
If you’ve lost work to sync conflicts in the past 90 days, reply and tell me which app and what happened. I’m collecting examples for a follow-up piece on recovery workflows.