DottieNote 1.0 was our first public release. The earliest version could already capture tasks, start focus sessions, review plans in a calendar, and organize items with simple color tags.
Tasks and focus
Version 1.0 supported task management with two focus modes: timed sessions and counting sessions. The first product loop was intentionally simple: write down a task, begin working on it, and leave behind a clear completion state.
Calendar and tags
The calendar view helped users review what was planned. Color tags made it easier to separate different types of tasks without turning the app into a heavy project system.
Later features such as voice input, Dottie Sticker, the planet atlas, and iCloud sync all built on this foundation.
Why 1.0 started here
The first version did not try to include every productivity method at once. For a planning and focus tool, the more important job was to make the basic path feel steady: capture the task, choose what to work on, complete a period of effort, and see the result afterward.
If those relationships are weak, later features have very little to stand on. Planet collection depends on reliable completion records. Dottie Sticker depends on a stable task entry point. Voice input needs a task model that can turn spoken language into something editable.
So 1.0 was the starting point for DottieNote. It did not rush to show everything the product might become. It focused on the most basic daily loop: capture, begin, complete.
The direction was already visible
Looking back, many later product decisions were already taking shape in 1.0. Timed and counting modes kept DottieNote close to action from the beginning. Calendar and tags helped organize tasks, but they did not replace the act of starting. The light interface and color system also made room for the more playful planet visuals that came later.
New capabilities continued to arrive in later releases, but the direction stayed the same. DottieNote is not trying to make users maintain a larger and larger system. It is trying to reduce the distance between thinking of a task and actually starting it.
A restrained first release
Version 1.0 did not include complex project management, heavy social mechanics, or a full productivity framework. It stayed close to tasks, time, and basic organization.
That restraint helped us learn from real use. Which entry points actually reduce the cost of starting? Which feedback makes people want to come back? The simpler the first version, the easier it is for later changes to follow real behavior instead of our assumptions.
From today, the value of 1.0 is not that it had many features. It is that it framed the right problem: how does a user capture a task, begin it, and know that the effort happened?
Action came first
If DottieNote were only a to-do list, 1.0 could have been even simpler: type a title, check it off, move on. But timed and counting focus were part of the core from day one. That shifted the product from "the task was recorded" to "the task can become action."
That difference shaped many later decisions. The planet atlas needed feedback after completion. Live Activities needed reliable timer state. Dottie Sticker needed a task that could be started from a real-world context. iCloud sync needed to respect both tasks and focus records.
The role of 1.0 was to put those basic relationships in place. Only then could later versions ask a fuller question: from the moment a task appears to the moment it is completed, how can the product support the user without getting in the way?
Later releases kept filling in the same path
When you look at later versions through the lens of 1.0, many features feel less sudden. Live Activities made focus time trustworthy outside the app. Dottie Sticker shortened the starting action. The planet atlas gave completion a more concrete form. iCloud sync let tasks continue across devices.
They all circle back to the same core loop. DottieNote's long-term work is to make capturing, starting, and completing feel more natural, more reliable, and easier to remember.