The plant care app fields that make reminders work.
A plant care app has one real job: get you to look at a plant before it is too late, and remember what you found. The watering reminder is the part everyone notices, but a reminder is only as good as the record behind it: what the plant is, where it sits, what it grows in, and when you last checked. This page is one of our app examples, and it is about that record: the fields a plant care reminder app needs, the rules that turn them into a nudge worth trusting, and the point where a stock app stops fitting.
It covers houseplant watering apps, plant ID and care apps, how the reminder itself is delivered, and the moment a plant shop, a plant maintenance route, or a collector with three hundred pots needs something the store apps do not offer.
See what a plant care app needs to captureThe short version
One record per plant, and a reminder that asks you to check, not pour.
A plant care app stores one record per plant (species or nickname, light, pot, soil, last watered, last fed, last repotted, notes and photos) and runs a reminder engine on top. The engine should not promise that a monstera needs water every seven days, because no plant does. It should estimate an interval from the record, prompt a soil check when that interval is up, and adjust from what you log. The rest of this page is the fields, the rules behind them, how the reminder reaches the phone, and the kinds of people who outgrow the apps on the store.
The per-plant record
What a plant care app needs to capture.
Every plant app on the store, and every spreadsheet someone keeps instead, comes down to the same per-plant record. The fields fall into four groups, and each group feeds a different rule.
The plant itself
The baseline. A succulent and a fern in the same window want very different intervals.
- Species or common name, typed or from a photo ID
- A nickname, because three pothos need telling apart
- A photo, updated when something changes
- Date acquired, so the record has a start
Where it lives
Light is the biggest lever on how fast the mix dries, and it changes the moment the plant moves.
- Room, and which window it is near
- Light band: low, medium, high or direct sun
- Distance from the window, or across the room
- Warm and dry, or cool, as a note
What it sits in
Two identical plants in clay and in plastic dry out on different schedules.
- Pot material: unglazed clay, glazed or plastic
- Pot size relative to the plant
- Drainage hole, and whether it stands in a saucer
- Soil mix, and the date it was last repotted
What you did last
The log is what turns a generic care sheet into this plant's own schedule.
- Last watered, and what the soil check found
- Last fertilized, misted or cleaned
- Pests, treatments and health notes, with a photo
- The current interval estimate, and why it moved
Light, in numbers
Why the light field is a band, not a checkbox
"Bright indirect light" means a different thing at every window. University of Maryland Extension puts it in foot-candles: low light is 25 to 100, typical of north-facing windows or rooms lit artificially; medium-bright is 100 to 500, typical of east or west windows; high light is 500 to 1,000, typical of south-facing and some west-facing windows; and direct indoor sun is over 1,000. It also calls light "probably the most essential factor for healthy indoor plant growth". See the UMD light bands
An app does not need a light meter to use this. Window direction plus distance is enough to place a plant in a band, and the band is what the interval rule reads. That per-item shape, one record with a photo, a location and a service history, is the same one a home inventory app keeps; the difference is that a plant's record has to change a schedule.
The rules
Why "water every seven days" is the wrong reminder.
Clemson Cooperative Extension's watering factsheet is blunt about it: "The main cause of death of potted plants is over-watering." Its rule of thumb is to water when necessary, and it lists why there is no pat answer to how often: the species, its growth stage, its location, the type and size of its pot, the soil mix and the weather all move the number. A reminder that says "Water the fern" on a fixed calendar is the one kind of reminder that makes the most common mistake more likely. Read Clemson's HGIC 1459 on watering indoor plants
The better reminder says "Check the fern", and the app records what you found. Each field in the record feeds a rule, and the rules are not secrets; they are the same ones the extension services publish:
| Field | The rule it feeds | Source |
|---|---|---|
| Plant type | Plants with large or very thin leaves usually need water more often than succulents, whose fleshy leaves and stems store it. | Clemson HGIC 1459 |
| Light band | A plant in a warm, dry, sunny spot needs water more often than one in a cool, low-light spot. | Clemson HGIC 1459, UMD light bands |
| Pot material | Water evaporates through the sides of porous clay, so a clay pot needs watering more often than a glazed or plastic one. | Clemson HGIC 1459 |
| Pot size | A large plant in a small pot needs water more often than a small plant in a large pot. | Clemson HGIC 1459 |
| Growth stage | After a flush of growth or a heavy flowering, and while dormant, a plant needs less water. | Clemson HGIC 1459 |
| Soil check | Water when the mix is dry at the first finger joint, until it runs out of the bottom, then empty the saucer. | Clemson HGIC 1459 |
The incumbents know this. Planta's own site says its watering reminders use "over 30 parameters, along with local climate and weather data", which is a long way from a per-species interval. You do not need thirty parameters to do better than a calendar, though. Five fields and a logged check get most of the way, and the helper below shows how they pull against each other.
Try it
How often should this plant get a check?
Pick what matches one of your plants. The result is a starting cadence for soil checks, relative to a leafy houseplant in a plastic pot and medium light, and every push in either direction comes from the Clemson watering guidance cited on this page. It is not a watering schedule: the finger test still decides.
What kind of plant is it?
How much light does the spot get?
What is the pot made of?
How does the plant fit its pot?
What is it doing right now?
Starting cadence
0 of 5 answered. Pick one option per question to see a starting cadence.
Whatever the cadence, the reminder should ask for the finger test first: dry at the first joint means water until it runs out of the bottom, then empty the saucer; still moist means skip, and the app should stretch the interval.
Compare a pet care app, where a vaccine booster or a medication dose has a real due date and a plain calendar reminder is exactly right. Watering is the opposite case: the date is an estimate, the check is the fact, and an app that confuses the two trains people to pour on schedule.
The workflow
How a plant care reminder actually works.
Seven steps, and only two of them happen when you add the plant. The rest is the loop that runs for as long as the plant lives.
- 1
Add the plant
Species, typed or from a photo ID, plus a nickname and a photo. The species sets the baseline: fleshy leaves or thin ones.
- 2
Place it
Room, window direction, light band, pot material and how the plant fits the pot. This is where two identical plants stop being identical.
- 3
Set a starting interval
From the plant type and the placement, or from your own habit. It is an estimate, and the app should say so.
- 4
The reminder fires
"Check the fern", with the last-watered date in the body. Not "water the fern": the check comes first.
- 5
Log the check
Dry at the first joint: watered until it drained, saucer emptied. Still moist: skipped. One tap each, with a note field for anything odd.
- 6
The interval adjusts
Skipped twice in a row: lengthen. Dry well before the reminder: shorten. Dormant flag on: stretch. The estimate becomes this plant's own.
- 7
The record grows
Fed, repotted, a pest treated, a photo a month. The history is what makes the next reminder specific instead of generic.
Delivery
Local notifications, or a server?
On iOS there are two kinds of notification, and a plant care app usually needs the simpler one. Apple's UserNotifications documentation draws the line: for local notifications, the app creates the notification content and specifies a condition, like a time or location, that triggers delivery; for remote notifications, your company's server generates the push and Apple Push Notification service delivers it to the device. Both reach the user whether or not the app is running. See Apple's UserNotifications overview
| Local notification | Remote (push) notification | |
|---|---|---|
| Who creates it | The app, on the phone | Your server |
| Needs a server | No | Yes |
| Fires when the app is closed | Yes | Yes |
| Works with no internet | Yes | No |
| Reaches other people's phones | No | Yes |
| Right for | One person's plants, with the schedule computed from data on the phone | Shared plants, a shop messaging customers, alerts decided on a server |
For one person's houseplants, everything the reminder needs, the plant record, the interval and the last check, lives on the phone, so local notifications are the whole answer: no account, no server, nothing to host. The moment the same plants are shared, a household, an office plant service whose technicians split a route, a shop that wants to tell customers a delivery is in, the schedule has to live somewhere every phone can read, and that means a backend and push. That is a bigger design decision than it looks, and it is worth reading about push notifications in mobile apps before deciding which side of that line your app sits on.
Picking an approach
Which kind of plant care app do you actually need?
"Best plant care app" is the wrong question until you know which job you want done. The apps on the store, and the things people use instead of them, cluster into four types.
| Type | Built around | Reminder logic | Several people, one plant list | Fields you can add |
|---|---|---|---|---|
| Plant ID and care app | A photo, a species match and a care sheet | Per species, from the care sheet, where offered | No | No |
| Reminder-first care app | A per-plant schedule the app maintains for you | Adaptive, inside the app's own model | Sometimes, as a share feature | Only the fields the app offers |
| Spreadsheet or notes app | Whatever you type | None, unless you add calendar events by hand | Yes | Yes |
| Custom-built app | Your record and your rules | Whatever rule you define, local or push | Yes, with a backend | Yes |
Two well-known apps sit squarely in the first two rows. PictureThis describes itself as snap-a-photo identification with insights on disease prevention, treatment, toxicity and care, and its site offers the download for free. Planta is the reminder-first case: a schedule built from those thirty-plus parameters, a light meter, and Care Share for sharing plant care schedules with friends and family; its site listed Planta Premium at $3.99 a month, billed $47.99 a year, on 20 September 2026. See Planta's Premium pricing
Both are good at their row. Neither is built for the last row: fields the app never thought of, a rule you define, and a list a team works from. That is a different job, and it usually belongs to a business rather than a windowsill.
When to build your own
When a plant care app is worth building yourself.
The people who outgrow the store apps are rarely hobbyists with a dozen pots. They are a plant shop whose "plants" are stock, with batches, suppliers and a care card per sale; an interior plantscaping company whose technicians visit client sites on a route and log each visit with photos; a plant sitter juggling other people's watering notes; a collector with hundreds of pots tracking propagation batches and pest treatments by product and date; or a school, a community garden or a shared office where several people care for the same plants and the reminder has to stop once someone has watered.
What those cases share is a record and a rule that no vendor schema quite fits. Teams in that position end up building their own, which is what Newly is for: describe the plant record you actually keep, the rule that sets the interval, who shares the list and how a reminder should read, and it builds a real native app around your process instead of someone else's. Its docs describe the same split as the table above: a new app keeps its data on the phone with no server, and a backend comes in only when data has to be shared or synced. Practical limits to know before you start: it costs $25 a month with no free plan, the iOS app ships through App Store Connect after you connect your Apple Developer account, and v2 does not produce Android release builds.
Whatever you build with, write these down first. They are cheap to change on paper and expensive to change once the screens exist:
- The per-plant fields you actually keep, and which of them are required
- The rule that sets the first interval, and what is allowed to move it
- What one logged check records: watered, skipped, or something wrong
- Who shares the list, and what happens when someone else waters first
- How a reminder should read, and what time of day it should arrive
- Whether it has to work with no signal, in a greenhouse or a basement
Sources
Where the specifics came from.
Four things on this page come from a primary source rather than general consensus: the watering rules, the light bands, the notification split, and one vendor's price.
FAQ
Plant care apps, answered.
It keeps one record per plant (what it is, where it sits, what pot and soil it is in, and when it was last watered, fed and repotted) and turns that record into reminders. Good ones prompt you to check the soil rather than to water on a fixed day, log what you found, and adjust the next reminder from it. Many also identify a plant from a photo and attach a care sheet for the species.
Start with the record, not the reminder.
A plant care app lives or dies on what it knows about each plant and what it does with a logged check. Get those two things right, then look at what other people have built before you describe your own.