MononoMori 2.0.1 Update: The Details You Don't See
MononoMori 2.0.1 brings subtle yet impactful improvements, including pinch-to-zoom for the AI camera, visual feedback for AI states, visual noise reduction in Memory Forest, and the new 'Cost per Day' metric. These micro-refinements elevate the user experience from usable to delightful.
Hi, I’m Windmori.
I thought I would finally get some rest after launching version 2.0. As it turns out, the real, time-consuming work only begins after release.
People often think of software development as a process of constantly adding new features—designing a new page, implementing a new module, or integrating some shiny new AI capability. While those are important, lately I’ve realized that what truly elevates an app from “usable” to “delightful” is rarely the flashy headlines. Instead, it’s the quiet details that users might not even consciously notice.
Turns out, camera zoom isn’t that simple
Recently, I’ve been refining the shooting experience of our AI Magic Camera. When I first built it, I thought the flow was simple enough: open the camera, snap a photo, and get the recognition results. But real-world usage quickly revealed a friction point: objects don’t always sit nicely right in front of you.
Sometimes they are placed high up, tucked away in tight corners, or simply too small. Having to constantly step forward and backward just to frame the shot was a frustrating experience.
To solve this, we’ve added pinch-to-zoom gestures and quick focal length switching. The feature itself isn’t complex, but the real effort went into blending the zoom gestures, focal transitions, and the AI recognition pipeline so seamlessly that the entire experience feels completely natural.
Making something feel “natural” is often the hardest thing to design.
The biggest challenge with AI isn’t incorrect recognition—it’s uncertainty
This update also polishes several details of the AI cutout workflow.
In real-world scenarios, AI sometimes fails to identify a clear object, a network request gets stuck, or the image boundaries are slightly off. These aren’t necessarily bugs, but if the app doesn’t say anything, users are left wondering, “Is it broken?”
Lately, I’ve spent a lot of time on things I once thought were secondary: adding banner notifications, implementing timeout protections, polishing transition animations, and adjusting the margins of the cropped area. These changes are tiny on their own, but they share a single goal: keeping the user informed of exactly what the app is doing.
Most of the time, people don’t mind waiting. What causes anxiety is not knowing how long the wait will be.
Tuning “Information Density” and Visual Noise Reduction
Another question I’ve been reflecting on is: how much information should a screen actually display?
In the past, I had a habit of throwing all the data onto the screen. I eventually realized this is classic “developer thinking”—as developers, we know why every single field exists, but users rarely care.
With this in mind, I redesigned the “Memory Forest” list by removing some of the clutter. For instance, I removed the explicit date text from the memory cards. It’s not that the date is unimportant; it’s just that it was taking up valuable visual attention while rarely being read.
Instead, I integrated the month and day as a subtle background watermark. The information is still there, but it no longer competes with the content itself. Sometimes, good design isn’t about making additions; it’s about knowing what needs to disappear.
A new feature I unexpectedly love: Cost per Day
If I had to pick my favorite small addition in this update, it would probably be the new “Cost per Day” metric.
When we buy something, we usually only remember its initial price tag. We rarely ask ourselves: How many times did I actually use it? How long has it accompanied me?
If you buy a 30,000 yen pair of headphones and use them for three years, their daily cost is incredibly low. On the flip side, impulsive purchases—even cheap ones—that end up forgotten in a closet after a few days are actually very expensive.
I find this number incredibly grounding. It doesn’t judge whether something was expensive or cheap; it simply reminds you of the things that have truly entered your life and brought you value.
An extra detail: I realized that seeing this number every day might cause subtle anxiety or even trigger impulsive counter-behaviors. To prevent this, I chose to place this metric inside the item’s detail page rather than on the main dashboard. It’s there when you want to look, but otherwise, it stays quietly out of the way.
Final Thoughts
The longer I build products, the more I believe in one thing: the overall experience is shaped by the details that go unmentioned.
Whether a button feels easy to reach, whether the wait screen makes you feel anxious, whether the interface feels cluttered, or whether a transition animation disrupts your thoughts—these things don’t make it onto the App Store screenshots. Most users won’t write in to thank you for them. Yet, the moment they are missing, everyone notices.
The 2.0.1 update is exactly that kind of release. There are no earth-shattering features, but there are dozens of micro-improvements that I personally appreciate using every single day.
I hope these subtle refinements make your time in the “Forest” feel just a little more comfortable.