DottieNote 1.1 arrived 4 days after the first release, refining timer behavior and the reliability of flip-to-focus.
Timer reset fix
This release fixed an issue where resetting a task could unexpectedly return the timer to one minute. The fix prevented a carefully chosen focus duration from being changed without the user intending it.
Flip-to-focus refinement
The trigger conditions for flip-to-focus were also refined. When a user placed the phone face down to begin focusing, the app became less likely to misread the gesture.
These changes were small, but they directly affected the reliability of starting a focus session every day.
Small releases can build trust
For a focus tool, the timer is a basic promise. When users set a duration, they expect the app to start, pause, resume, reset, and finish according to that duration. Even a small issue like resetting to one minute creates another moment of doubt before starting.
That extra check may seem minor, but it breaks the flow a focus tool needs most. Users come to the app to enter a task quickly. They should not have to inspect the timer for a strange default value before trusting it.
Version 1.1 handled exactly this kind of early detail: easy to overlook, but likely to show up in daily use.
Flip-to-focus should feel safe
Turning the phone face down to begin a focus session can feel like a small ritual. But it depends on a reliable trigger. If the trigger is too sensitive, users may start a session by accident. If it is too unreliable, they will stop trusting the gesture.
That is why 1.1 refined the flip behavior. This was not a release about adding a new trick. It was about making an existing way to begin feel safer.
The same thinking later shaped DottieNote's approach to Dottie Sticker and NFC. Any faster entry point has to be stable first. The shorter the path, the less tolerance users have for failure.
Early polish shapes the product feel
A release like 1.1 may not change someone's first impression of the product, but it can affect whether they keep using it. Timer reset behavior, flip detection, button response, and similar details combine into the feel of the app.
When the most common actions are stable, users can relax. When even the basic timer needs to be checked again and again, no amount of nice visual design can fully make up for it.
That is why DottieNote keeps recording small fixes in public updates. We want users to see that the everyday parts of the product are being maintained seriously.
Reliable timing comes before later feedback
Later features such as Live Activities, planet unlocks, Apple Health integration, share cards, and focus history all depend on one thing: the focus state has to be accurate.
If starting, resetting, or restoring a timer cannot be trusted, every downstream piece of feedback becomes questionable. Users do not need to know how the internal state works. They need to know that the time they set will not change unexpectedly, and that a flip gesture will not be misunderstood.
Small fixes are worth writing down
Many products compress this kind of work into "experience improvements." But if someone has actually seen a timer reset itself, or had a focus gesture trigger unreliably, they know it is more than a line in a changelog.
Writing the fix clearly is a way to acknowledge the real friction users met. For an early app, that kind of communication is part of building trust.
The value of 1.1 was that it removed small doubts early, before they became reasons to leave. DottieNote has always needed to be more than novel. It also needs to take everyday reliability seriously.