One flatmate waters the plant. Another, seeing the reminder, waters it again. The third assumes somebody else has handled it. The plant would like the household to establish a communication protocol.
A shared plant-care log is a coordination hypothesis. It should not promise expert diagnosis or universal care schedules from a photograph.
Separate knowledge from coordination
Ask whether the household’s problem is knowing what a plant needs or knowing what another person already did. Those are different jobs. The first may require reliable horticultural expertise; the second may be addressed with a clear shared record.
A prototype could focus on user-defined tasks, last completion and a visible next check. Let people control the schedule rather than presenting a guessed interval as authoritative care advice.
Fit the physical moment
Test logging an action while standing beside the plant. Does the person know which record to open? Can they update it quickly? Would a label or a simple location name help more than an elaborate identification feature?
Include vacations and temporary handovers. The person caring for the plants for a week should understand the plan without learning an entire productivity system.
Challenge the business model
The coordination problem may be real and still too small for a separate paid app. A shared note might work well enough. Investigate repeated frustration and willingness to adopt before building reminders, image recognition and a marketplace.
A narrow pilot with a few households can reveal whether the record stays current after the novelty wears off. Measure missed or duplicate actions through participant reports rather than claiming a health outcome for the plants.
The interesting product lesson is that a personal utility changes when several people share the job. Sometimes the missing feature is not intelligence. It is a reliable answer to “Did you already do this?”