What changed
We have completed the release of Tomato v0.2.1.
Following v0.2, we continued iterating quickly based on real usage feedback, with the goal of steadily reducing key experience issues without disrupting ongoing use.
Main focus of this update
- Addressed feedback gathered after the v0.2 release
- Improved stability across selected runtime paths
- Refined overall interaction continuity
- Continued building the engineering foundation for future releases
Why updates like this matter
A product rarely goes from "usable" to "something people want to keep using" through a single major release. More often, that happens through a series of smaller releases that continuously improve the experience.
The value of v0.2.1 is in moving Tomato one step further in that direction.
What's next
We will continue iterating quickly and push forward with the next round of releases based on real usage patterns.