Never Lose Your Cross-Stitch Progress: Why Merge Sync Beats Overwrite
How per-stitch iCloud merge sync protects hours of marked progress — even offline, even across two devices.
You sit down with your needle, glance at the corner of a sky you spent three evenings filling in, and it's gone. The little marks that tracked every stitch have rolled back to where they were last week. Anyone who has lost cross-stitch progress on a device knows the specific sting of it — not the floss, not the fabric, but the record of where you were. This post is about why that happens, and how the right kind of sync makes it stop happening.
Why progress disappears in the first place
Most lost-progress horror stories come down to one quiet design decision buried inside an app: how it resolves a conflict. A conflict is simply two versions of the truth. You marked twenty stitches on your iPad on the couch. Earlier that day you marked ten on your iPhone at the doctor's office. Now both devices want to save, and the app has to decide what "your progress" actually is.
The lazy answer — and it is alarmingly common — is called last-write-wins at the record level. The device that syncs last simply replaces the whole project. If your iPhone's older snapshot lands after your iPad's newer one, the older one wins, and the newer stitches are erased without a warning, a prompt, or a trace. The app didn't crash. It did exactly what it was built to do. It just overwrote instead of merged.
Overwrite versus merge, in plain language
Picture two versions of a shopping list. Overwrite says: keep one list, throw the other away. Whichever arrives last is the list now. If the kept list is missing milk, milk is gone forever. Merge says: read both lists and combine them — milk from one, bread from the other — so nothing anyone wrote is lost. For cross-stitch, a stitch is an item on that list. Overwrite can lose stitches. A proper merge cannot.
The detail that makes merging safe is granularity. Stitchwork doesn't track "your project" as one big blob that has to win or lose as a whole. It tracks each cell on the grid individually. When two devices reconcile, the app compares cell by cell and keeps every cell that either device marked complete. There is no single version of the project that can stomp on another, because progress is assembled from the smallest possible pieces rather than swapped wholesale.
Why marking off is the safe kind of change
Here is the quiet elegance of stitch tracking: marking a stitch is additive. Across an afternoon, your edits are almost always "this cell is now done." That kind of change is order-independent — it doesn't matter whether the iPhone's mark or the iPad's mark is processed first, because the combined answer is the same either way: both cells are done. Stitchwork is built around that fact. It merges your marks together rather than forcing them to compete, which is exactly why the promise to never lose a stitch is one we can actually keep.
Offline on the couch, two devices, one project
Real stitching doesn't happen at a desk with perfect Wi-Fi. It happens on planes, in waiting rooms, in the garden, on the sofa with the router two floors away. So offline can't be an error state — it has to be the normal one. With Stitchwork you stitch and mark freely with no connection at all. Your marks are saved on the device the moment you make them.
When you're back online, those marks sync up through iCloud and reconcile with whatever your other device did in the meantime. Stitch on your iPad in airplane mode for an hour, then pick up your iPhone later — when both reconnect, the two sessions fold together into one accurate picture of the project. Nothing waits on a live connection, and nothing gets discarded for having been made offline.
Your patterns stay yours — and private
Sync raises a fair question: who can see all this? With Stitchwork, your patterns and your stitch progress live in your own iCloud account and move between your iPhone and iPad through Apple's CloudKit. We never see your patterns or your stitches — they aren't on our servers, and we have no window into them. To improve stability we do receive anonymous crash reports, which contain no pattern content; that's the full extent of what reaches us.
One honest caveat worth stating plainly: syncing relies on your iCloud and Apple's CloudKit working as intended, so it's provided as-is and depends on those services and your own iCloud setup. What we control — that your marks merge rather than overwrite, and that an older snapshot can never erase newer progress — we've built deliberately around protecting your work.
What this means for the way you stitch
The payoff is freedom from a small, constant anxiety. You can stitch on whichever device is in your hand, online or off, and trust that the count you see is the real one. No babysitting which device synced last. No keeping a paper backup of your place "just in case." The grid you marked is the grid that's saved.
If you've left a cross-stitch app before because hours of marked progress vanished, that wasn't carelessness on your part — it was an app that chose overwrite over merge. Choosing per-stitch merge sync is choosing software that treats your time at the hoop as something worth protecting. Import the charts you own, mark your stitches with both hands free of worry, and let the sync quietly do the one job it should never get wrong: keeping every stitch you've made.