The Product Decision Behind “Stop watering every plant on Sunday” in GrowBook
I am using GrowBook's first month to test a decision that looked obvious while I was building it.
A weekly watering day sounds tidy.
Why I made the call
A schedule is useful as a prompt to check, not an order to pour water. I look at the soil, the weight of the pot and the plant itself before marking the task complete. Some plants keep a seven-day rhythm. Others change as the room gets warmer or the days get shorter.
What I am watching after launch
That is why GrowBook stores a separate interval for each plant instead of giving the whole collection one watering day. The reminder says which plant needs attention; the final decision still belongs to the person standing next to the pot.
Sunday is still on my calendar. It now means “check the plants,” not “pour water into every pot.”
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
Really good writeup, thanks for sharing it. What's the next thing you're planning to try here?
The reminder vs. instruction distinction feels like the right product boundary. Tracking skips and overrides alongside repeat use could show whether the context-aware intervals actually earn trust.
That’s the gap I’m noticing too. GrowBook records a completed task and lets you edit the interval, but it doesn’t currently capture “I checked and decided not today.” A thoughtful skip looks exactly like an ignored reminder.
A one-tap “check again in two days” action could capture that without turning plant care into paperwork. If people use it instead of disabling reminders, that would be a much stronger sign of trust than repeat opens alone.
That distinction matters a lot. “Skipped on purpose” and “ignored” look identical in the data otherwise. A one-tap “check again in two days” is a clean signal — and if people use it instead of turning reminders off, you’ve got real trust, not just opens.
Exactly. That one tap would help the user in the moment and give me a clean signal without asking them to explain themselves in a survey.
I’d keep it separate from the plant’s normal interval, though. GrowBook calculates the next due date from that recurring interval, and one unusually cool week shouldn’t permanently turn a seven-day schedule into nine. A separately logged defer would tell me much more than another app open.
I like the distinction between a reminder and an instruction here. The reminder tells you where to look, but the actual decision depends on context that can change over time.
It makes me think this principle applies beyond plant care too — good software can preserve the relevant context and surface it at the right moment, without pretending the context itself is the decision.
Exactly. GrowBook can remember that a pothos was watered seven days ago and put it in front of you at the right time. It can’t feel the soil or notice that the room has been hotter all week.
I want the app to handle the memory and timing, then get out of the way when human judgment starts. That boundary probably applies to a lot more than plants.
This is a nice product call because it respects the real-world decision.
A shared Sunday watering habit is tidy for the calendar, but it can quietly teach the wrong behaviour. Per-plant intervals make the reminder more useful because the app is prompting attention, not pretending every plant has the same needs.
I reckon the interesting metric is not just whether people come back twice, but whether they adjust the interval after using it. If someone changes a plant from 7 days to 10 or 4 after checking the soil, that is a strong sign the app is helping them learn the plant rather than just complete a task.
I think you’re right. An interval change is a better signal than a second visit. GrowBook already lets each plant’s care schedule move from 7 days to 10, 4, or whatever fits, and completing a task calculates the next date from that interval.
I’m not tracking those edits as a product metric yet, but repeated adjustments would show that someone is observing the plant and teaching the schedule, not merely clearing reminders. That’s much closer to the behavior I hoped the app would support.