What changed
Today, we are releasing Tomato v0.2.2.
This version continues the core direction of the v0.2 series: absorbing real feedback, acting on it quickly, and making Tomato more stable, smoother, and closer to being usable at greater scale within a short period of time.
Improvement areas in this release
- Continued reduction of the key issues affecting the experience
- Better overall product stability
- Improved consistency during ongoing conversations
- Further refinement of the core engineering pipeline
Why we continue to iterate quickly
At an early stage, speed is itself part of the product's capability.
Fast iteration is not about creating the appearance of momentum. It is about turning real feedback into real progress as quickly as possible.
What's next
We will continue advancing the v0.2 series and preparing Tomato for a more mature 1.0 stage.