The Product Decision Behind “When did I last water this plant” in GrowBook
This is the kind of product choice that does not show up in a launch screenshot.
Most of my plant mistakes do not begin with rare diseases or mysterious nutrients.
Why I made the call
Memory is unreliable because watering is a tiny task. I do it while making coffee, moving laundry or answering a message. Three days later, I remember touching the pot but not whether I watered it. A note with a date settles the argument in a few seconds.
What I am watching after launch
GrowBook keeps care history beside the plant, so I can see the last watering, fertilizing or repotting entry without digging through a general calendar. It is not expert advice. It is a record of what I did, which is often the missing piece.
The next time a leaf turns yellow, I would rather check a date than debate my own memory.
I am tracking whether people use this twice, not whether they say the screen looks nice.
GrowBook on Google Play: https://play.google.com/store/apps/details?id=com.yuntai.growbook
Curious how long it took before you saw the first real results?
The first useful result was immediate for me. Once I logged a watering, I stopped having the “was that Tuesday or last week?” argument with myself.
The product result takes longer. I want to see someone record care for the same plant across several cycles, not open the app once and disappear. It’s still too early for me to claim that pattern at any meaningful scale.
Interesting. How are you measuring whether it is working?
GrowBook doesn’t currently ship behavioral analytics, so I’m keeping the claim narrow. I’m looking for repeat care entries on the same plant, people leaving reminders enabled, and interval changes after they’ve checked the plant a few times.
The app already records that care history locally. Downloads and a good-looking first session tell me very little if nobody comes back to log the next watering.
回复中文参考：
Interesting approach. What was the hardest part to get right?
The hard part was keeping the action fast while making everything behind it stay consistent. One tap has to create a care-history entry, update the last-care date, calculate the next due date, replace the notification, and eventually sync.
Watering is such a small task that people won’t record it if the app turns it into a process.
This is useful. How are you finding your first users so far?
Mostly through posts like this and organic discovery on Google Play. I expected Reddit to be a bigger channel since the original idea came from a thread there, but I can’t currently post in some of the relevant communities.
So discovery is still slow and manual. I don’t have a repeatable acquisition channel yet.