Risk: automatic spread of errors
(If we periodically back up the files in the iCloud Drive QuickPlan folder to other places, manually or via third-party backup apps, there is no critical risk to access iCloud drive project files directly, we can skip the following risk section.)
iCloud Drive acts as a shared folder on the internet, with the capability to automatically sync changed files to all the involved iOS and macOS devices. We feel good when using iCloud Drive to synchronize files - as we don't need to care about how to transfer the updated files from one device to another device. iCloud Drive helps us to synchronize the files automatically - it sounds good. But there is a risk caused by this iCloud behavior if we can't use the service well.
For example, we have an important file on iCloud Drive, which can be accessed on multiple devices using the same iCloud account. Incidentally, we changed the file on one device incorrectly, and we find there is no backup to restore it from the changing.
We may think we can find the old version from another device. However, before we realize the problem, iOS / macOS may already complete synchronizing the incorrect changes to other devices AUTOMATICALLY. iCloud synchronization is coordinated by iOS and macOS systems, not by the apps. After the app saved the project file on iCloud Drive, the OS systems and iCloud serve will take control of when and how to transfer the file to other devices.
You may wonder why QuickPlan could take control as it's the designed behavior of iCloud Drive, and the users like it. The user (and the app) has no control over it. Although most of the time, this risk is not very critical, the right work approach will be better to help us to mitigate the risk.
Manually back up the iCloud files on the device or using third-party tools to automatically back up iCloud Drive files periodically.
On the macOS device, we can access the iCloud Drive folder directly. It's easy to copy the files to another folder on the same device or another device. We can upload the files to a cloud storage service easily, as some of the 3rd cloud storage services provide the app to map a local folder to a remote folder. For example, we can install Dropbox for the macOS app and config a folder that will automatically sync with a folder on Dropbox.
Our practice is to back up the iCloud Drive folder to another folder on the device daily manually or using a tool. Back up to one folder one day, keeping the last x days, and upload the backup to Dropbox by week.
If you don't like to back up the iCloud Drive files. For the important files on iCloud Drive, to avoid losing your work by incorrect actions, we suggest to.
On macOS devices, copy the iCloud Drive file to another folder, then to change the copied one. After changed and CHECKED, copy the changed one back to iCloud Drive.
On iOS devices, QuickPlan supports to copy project document from iCloud to the device, and also supports to copy from device to iCloud Drive.
Some users may expect to edit the same project (open from iCloud Drive directly) on multiple devices at the SAME time, and the changes should be reflected on other devices automatically. We want to emphasize here that editing the same project on multiple devices at the SAME time is impossible via iCloud Drive
Because tasks in the project schedule are in a TREE structure, there are tight relationships between them. For example, the date constraint relationships via the task links, the parent-child via task group hierarchy relationships.
Editing two or more task items at the same time will cause severe logic problems. Following are some cases which may cause logic problems when operating on two devices at the same time: