Risk: Automatic Error Propagation

(If we regularly back up the files in the iCloud Drive QuickPlan folder to other locations, manually or via third-party backup apps, there is no critical risk from directly accessing iCloud Drive project files. We can skip the following risk section).

iCloud Drive functions as a shared internet folder, automatically syncing file changes across all connected iOS and macOS devices. Using iCloud Drive for file syncing is convenient—eliminating the need to manually transfer updated files between devices. Automatic file syncing via iCloud Drive is beneficial. However, this behavior introduces risks if not managed correctly.

For example, we have an important file on iCloud Drive that we can access on multiple devices with the same iCloud account. Suppose a file is modified incorrectly on one device, and there is no backup to restore the original version.

We might assume the previous version exists on another device. However, before the issue is realized, iOS/macOS may have already automatically synced the incorrect changes to all other devices. iCloud synchronization is managed by the iOS and macOS operating systems, not by individual apps. Once the app saves a file to iCloud Drive, the OS and iCloud service systems control the timing and method of transfer to other devices.

Users may wonder why QuickPlan cannot intervene, but this is the intended, user-preferred behavior of iCloud Drive. Neither the user nor the app has direct control over this system-level process. While generally not critical, this risk can be mitigated with appropriate workflows.

• Manually back up iCloud files to the device or use third-party tools for automatic backups of iCloud Drive on a regular basis.

  On a macOS device, we can directly access the iCloud Drive folder. Files can be easily copied to another folder on the same or a different device. Files can also be uploaded to other cloud storage services, many of which allow mapping local folders to remote ones. For instance, the Dropbox app for macOS can be configured to automatically sync a local folder.

  A recommended practice is to back up the iCloud Drive folder to a separate local folder daily, either manually or via a tool. Back up daily to a folder, keep the last x days, and upload the backup weekly to Dropbox.

• If backing up iCloud Drive files is not preferred. we recommend precautions to avoid data loss due to operational errors for important files.

  On macOS, copy the file from iCloud Drive to a local folder before editing. Once modified and verified, copy the file back to iCloud Drive.

  On iOS, QuickPlan supports copying project documents between iCloud and the device.

Notes:

Users may expect to edit the same project (opened from iCloud Drive) on multiple devices simultaneously, with changes automatically propagating to other devices. However, editing the same project on multiple devices concurrently via iCloud Drive is not possible.

Since project tasks exist within a TREE structure, they function in close relationship with one another. Examples include date constraint relationships via task links and parent-child relationships via task group hierarchies.

Editing multiple task items simultaneously can cause significant logical conflicts. Possible scenarios causing logic issues when editing on two devices simultaneously include:

• (On device A), add a task to a task group; (On device B), the same task group is removed.
• (On device A), assign a project member to a task; (On device B), the project member is removed from project resources.
• (On device A) move a task to change the date; (On device B) move another task that is the successor of the moving task on device A.
• (On device A) we find that project data has changed unexpectedly. For example, the task work is "automatically" updated to an unexpected value. We are confused and suspect an error, while in reality, someone else has changed the task work on device B.