The most important reminder rule in GardenBot is simple: do not mark watering done when you only checked the plant. Mark the action you actually completed. If the soil is still wet, leave watering due and adjust the interval if that pattern repeats.
GardenBot helps by attaching care tasks to individual plants. Each plant can have care actions turned on or off. Enabled actions use intervals measured in days, weeks, or months, and GardenBot stores the schedule and last completed date so it can show due and overdue care.
Mental model: Plant -> enabled care actions -> interval -> last completed date -> due or overdue state.
A typical GardenBot reminder flow
The basic flow is straightforward:
- Add a plant.
- Choose or confirm the plant’s care actions.
- Turn actions on or off for that plant.
- Set intervals for enabled actions.
- Enable Daily reminders and allow iOS notifications.
- GardenBot schedules local reminder notifications for due care.
- Check the plant.
- Mark the right care action done or adjust the interval.
This is different from a calendar event because the task belongs to the plant record. The schedule, last completed date, and plant context stay together.
A practical example: if a pothos is due for watering and rotation on the same day, those are still separate care actions. You may water because the soil is ready, but skip rotation because the plant is not leaning. Keeping actions separate prevents one tap from accidentally rewriting the whole care history.
Mental model
| Layer | What it answers |
|---|---|
| Plant | Which plant is this about? |
| Enabled actions | Which care tasks apply? |
| Interval | How often should this action be checked? |
| Last completed | What actually happened last time? |
| Due or overdue | What needs attention now? |
Care actions GardenBot can track
GardenBot support materials describe care actions such as watering, checking, spraying, fertilizing, repotting, rotating, and pruning. Not every plant needs every action.
| Action | Example use |
|---|---|
| Watering | Track when the plant was actually watered |
| Checking | Record that the plant was inspected |
| Spraying | Track spraying if you already use it for a specific reason |
| Fertilizing | Avoid forgotten seasonal feeding |
| Repotting | Keep long-term care visible |
| Rotating | Reduce leaning toward a light source |
| Pruning | Track recurring cleanup or shaping |
The useful part is selectivity. A snake plant may not need frequent watering reminders. A fern may need more frequent checks. A pothos may need weekly checks and occasional rotation.
Do not treat spraying or misting as a universal humidity fix. Track it only when it is part of your actual care routine for that plant.
Example setups
Here are practical starting points. Treat them as check rhythms, not fixed watering orders.
| Scenario | Possible setup |
|---|---|
| Beginner with 5 mixed plants | Weekly checks for most plants, slower checks for snake plant or succulents |
| Frequent traveler | Review upcoming due tasks before leaving, avoid last-minute overwatering |
| Chronic overwaterer | Add checking tasks, leave watering due when soil is wet, lengthen intervals after repeated skips |
| Larger collection | Use separate actions so watering, pruning, rotating, and repotting do not collapse into one vague task |
| Pothos due for watering and rotation | Water only if soil is ready; rotate if it is leaning |
After a few weeks, adjust. If you keep skipping watering because the soil is wet, lengthen the interval. If a plant is dry before the reminder, shorten the check rhythm.
These examples are intentionally conservative. The schedule should become more accurate as you learn how the plant behaves in your room. For non-product schedule tuning, see how to build a houseplant watering schedule.
When not to mark care done
Mark the action you actually completed. If you looked at the plant but did not water it, mark a checking task done, not watering. If you watered but did not fertilize, do not mark fertilizing done. This keeps the next due date meaningful.
This distinction is small but important. Many plant-care systems become unreliable when every interaction gets recorded as watering. GardenBot works better when care history reflects what happened.
If you only inspected the plant, that observation is still useful. It tells you the reminder reached you and the plant did not need that action yet. Over time, repeated skips are a signal to change the interval.
If you do not use a checking task for that plant, simply do not mark watering done when you only looked at it. Leave the watering task for the day the plant is actually watered.
Local reminders and iOS behavior
GardenBot schedules; iOS delivers. GardenBot can schedule local iOS notifications for plant-care reminders, but delivery still depends on iOS notification permission, GardenBot reminder settings, plant notification settings, timezone, whether the plant is active under plan limits, and iOS behavior such as Focus modes or Low Power Mode.
If reminders do not arrive, check iOS Settings, Daily reminders in GardenBot, the plant notification setting, Focus modes, notification summary, Low Power Mode, whether the plant is active under plan limits, and whether the app has opened online recently to refresh data and rebuild reminders.
Common setup mistakes
| Mistake | Better setup |
|---|---|
| Marking watering done after only checking | Mark checking if used, or leave watering due |
| Enabling every action for every plant | Enable only actions that apply |
| Using the same interval everywhere | Tune intervals per plant |
| Too many notifications | Start with fewer reminders and add detail later |
| Ignoring iOS permission | Confirm notifications are allowed in iOS Settings |
Where GardenBot helps
GardenBot is useful when a generic calendar event is too broad. A practical case is a pothos that is due for watering and rotation: water only if the soil is ready, rotate only if the plant is leaning, and leave any unrelated actions untouched. That keeps the next due date meaningful.
For more detail, see Plant Care, Reminders, and Notifications, Plant care app vs calendar reminders, and why offline access matters in a plant care app.
For the product-level feature summary, see Plant Care Reminders.
FAQ
Does GardenBot water plants automatically?
No. GardenBot organizes reminders and care history. You still inspect the plant and choose the right action.
Can I turn care actions off per plant?
Yes. Each plant can have care actions turned on or off, and enabled actions use intervals.
What should I do after a reminder fires?
Inspect the plant, decide what actually happened, mark the exact action completed, and adjust the interval if the same pattern repeats. If you only checked the plant and do not use a checking task, do not mark watering done.
Will reminders arrive exactly on time?
Not always. GardenBot schedules local iOS notifications, but iOS controls delivery and can delay or suppress notifications depending on device state and settings.
What should I do if reminders stop?
Check notification permission, Daily reminders, plant notification settings, Focus modes, Low Power Mode, timezone, plan limits, and whether GardenBot has refreshed online recently.