When people hear "sync," they often think of accounts, servers, and cloud databases. But DottieNote does not begin with "upload everything first." It begins with the idea that a task tool must be reliable on the current device.
That is the point of local-first design. Your tasks, tags, focus records, and planet progress should first be fast, stable, and usable on the device in your hand. Even with poor network conditions, basic task creation, review, and focus should not fail immediately.
iCloud sync solves a different problem: how to continue that data across multiple Apple devices.
iCloud is an extension, not a prerequisite
DottieNote does not require an extra account for core use. For many people, a task tool that begins with login, setup, and waiting for sync increases the cost of starting.
When iCloud is enabled, related data syncs through Apple's iCloud and CloudKit systems. That process depends on your Apple ID, iCloud settings, network state, and device environment.
That is why the help center explains sync conditions clearly. This is not about passing responsibility to the system. It is about helping users know when to wait, when to check iCloud settings, and when to confirm local data first.
Turning sync off needs careful design too
Mature sync design is not only about turning sync on. It is also about turning it off safely. When users decide to disable iCloud sync, the app should protect local data as much as possible so one switch does not make tasks feel like they disappeared.
That is why DottieNote has continued fixing sync, storage warnings, and migration safeguards. Sync is not one button. It is a whole flow that needs to help users feel safe.
Local-first and iCloud sync do not conflict. Local-first protects core experience and data control. iCloud gives continuity across devices. DottieNote will keep maintaining them under the same product principle.
Why not start with our own account system?
A DottieNote account could have value. It could support broader cross-platform sync, subscription management, and support troubleshooting. But at this stage, introducing an account too early would also add costs: registration, login, password recovery, server maintenance, and more questions about data ownership.
We prefer to make the Apple ecosystem experience solid first. For iPhone users, iCloud is already part of identity and sync. If tasks, tags, and focus records can extend naturally through that system, there is no need to add another account layer just for sync.
This does not mean DottieNote will never support other sync options. It only reflects the current priority: make the device experience reliable first, then let multi-device use follow a system users already know.
Sync needs to be understandable
The stressful part of sync is that users cannot always see what is happening. If a task does not appear, is it the network, iCloud settings, storage, or an app state that has not refreshed?
DottieNote will keep making sync status easier to understand. This revision adds a later example: version 2.0.1, released on April 21, 2026, introduced the recheck action. We want users to have a clear next step when something goes wrong, rather than repeatedly closing and reopening the app.
Trust is the most important thing for a task tool. The quieter sync becomes when it works, the clearer it needs to be when it does not.
Local-first still needs recovery design
Reliable local data does not mean users will never meet problems. Device changes, enabling iCloud, disabling sync, system storage changes, and network instability can all affect task and sync state.
So DottieNote cannot stop at saying "data is stored on device by default." A fuller design needs to explain when data is local, when it enters iCloud, where to look when sync is unclear, and how local data is preserved when sync is turned off.
This kind of explanation may not look like a feature, but it directly affects trust. When people meet sync trouble, the scariest part is usually not waiting. It is not knowing whether their data is safe.
DottieNote will keep connecting iCloud status, the help center, and error messages. Sync should stay quiet when it works, and clear when users need help.