- What does it mean for synchronization to be "seamless?"
- How many project copies are being synced? Just two? More than two? How many more?
- Does one individual have control over all those projects? Or is collaboration with others involved?
- Does the program sync without your telling it to do so? If so, how does it make sure you don't shut down the computer before it's finished writing to the cloud (or other destination)?
- Assume one user controlling three copies, one Mac, one Windows, and one iPad. All copies start out in sync. Mac is updated and synced to the cloud. Windows get turned on and syncs with the Mac changes. iPad gets turned on out of range and cannot sync. iPad tells the user "can't sync." User wants to get more work done and makes edits anyway. Some of them unknowingly conflict with the Mac and Windows version. Then iPad is brought in range. What should happen? Should the conflicting edits be made to the Windows and Mac versions, wiping out existing changes (that would be one definition of seamless), or should the syncing iPad inform the user that there may be conflicts and should the user be engaged to make the merges of those changes before the sync actually begins (that's not seamless (at least by my definition), but I think it's necessary).
FYI, I use the Windows version, so I am not familiar with how syncing currently works on the Mac.