Greg: Plant Identifier & Care reviews

When the engine works as intended it doesn't just fire scheduled reminders — it adapts: if the user waters more often and logs it, Greg shifts the next due date. For an audience that admits it kills plants through inconsistency, that feedback loop is genuine value: people describe finally solving the "over/under-watering" problem and seeing growth take off. This is the product's strategic hook: not a reference guide (there are many) but a living "water → log → schedule adapts" cycle that builds a daily habit.

Greg's most durable asset is a live community where questions about a specific plant get answered by real people within minutes, often with photos. It solves what an algorithm can't: the case-by-case read of "here's my sick philodendron, what now." For beginners afraid of killing a plant, the sense of a "close family" of growers worldwide creates a reason to return that isn't reducible to features. Strategically the community is a moat: a reference guide and recognition are easy to copy, a warm responsive crowd nearly impossible — and it's what holds the most loyal users.

Greg deliberately makes care un-scary: large legible type, cute illustrations, step-by-step instructions, and personal "human" names for plants. For the target beginner — "I'm a houseplant murderer" — this tone turns intimidating responsibility into play, and people explicitly say care became enjoyable. It's a working emotional-onboarding mechanism: the product sells confidence and delight rather than agronomy, setting it apart from dry reference guides. (The same names have detractors — experienced gardeners find them childish — so the device polarizes by segment.)

When a user's access or subscription breaks, it's live support (people name Erika in Concierge) that turns an enraged customer back around: people who posted an angry review update it to "great service, all resolved." This is an important compensating mechanism: against fragile authentication and outages, the human in support retains people who'd otherwise be lost. Strategically it's both a strength and a warning — support is patching product holes by hand, but as long as it works it converts the worst experience into loyalty.

Greg prints QR codes on physical plant tags at Home Depot, Walmart, and florists — a person scans it expecting care instructions for the exact plant already in their hand. Instead of an instant answer they land on an app download, sign-up, and a paid screen. The channel that was supposed to feel like "free help bundled with the plant" instead places a barrier at the precise moment help-expectation peaks, so abandonment happens before the product proves anything.

You can only add a plant by photographing it — no manual name entry, no database search, no upload from the camera roll, and the app won't even read the plant's own QR code. When photo recognition misses, the user hits a dead end: they know exactly what plant they have (the store tag is in their hand) yet physically cannot log it. Making the camera a mandatory gateway turns a known plant into an unsolvable task and ejects people who just wanted to keep a list.

Recognition makes gross errors on mass-market plants: it calls an alocasia a philodendron, green onions a lily, bamboo first a cactus then marijuana. Because identification is both the first screen and the only way to add a plant, accuracy functions as a trust test: the user arrives with a plant they can't name themselves and immediately catches the app in an obvious mistake. After that they no longer trust the watering schedule either, since it's built on that same (wrong) identification. Many compare it to Google Lens on the spot and leave for it.

The core promised value — smart watering reminders — actually hands out advice detached from conditions: it tells people to water succulents and aloes weekly (which drowns them), ignores that spring brings more sun and soil dries in 7 days, and overwaters by its own defaults. Users explicitly report dead plants from following the schedule. This is the most dangerous failure because it strikes exactly the beginner "plant murderers" the app exists for: instead of relieving anxiety it gives false confidence and asks them to snooze their own common sense.

Greg moved the basic watering reminder from free to paid — with no warning and no email to loyal users, many of whom had tracked 250–400 plants for years. People discovered the feature gone only when their plants were nearly dead. The mechanism is dangerous because it destroys the very habit retention rested on: a schedule that worked for years was the reason to open the app daily, and yanking it suddenly doesn't convert to a subscription — it pushes the most engaged users to hunt for an alternative, carrying resentment straight into reviews.

The free tier won't even let you mark a plant as watered — the lightest, most habit-forming micro-action that other trackers deliberately keep free as a hook. Users are openly surprised: they're used to competitors offering at least a free watering log, and Greg breaks the category norm. Strategically it's a miscalculation: by denying free users the one daily gesture, the product prevents the habit that would later justify a subscription from ever forming — it charges before it has earned anything through regular use.

The only sign-in button is "Continue with Google" — no email choice, no guest mode, no normal registration. This cuts off several segments at once: people unwilling to hand data to Google, people whose auth simply fails with a "check your internet" error, and people who refuse to use a Google account. Because it's the very first screen, any failure here is a 100% drop: the user never sees the product. Hanging the entire funnel on one external provider makes activation hostage to its single point of failure.

Greg has no problem-diagnosis: a user can't photograph a yellow leaf or a pest and get a read on what's wrong. Yet the "my plant is dying, help now" moment is the peak of willingness to pay and peak emotion. Users explicitly leave for apps that diagnose disease and name it as the deciding reason to cancel. The missing feature means Greg catches the user in the calm "keeping a list" mode but loses them at the exact moment they need it most and would pay.

The product is designed around US indoor plants: no real handling of in-ground plants ("no way to add details about a plant potted in full ground"), location isn't detected, imperial units by default, window advice ("<3ft from the window") for everything. This alienates a large and clearly interested segment — outdoor gardeners, irrigation techs, and metric-country users who explicitly ask in reviews for an outdoor version. The narrow lock to one scenario caps the market at exactly the people already in the app's comfort zone.

Paying users periodically have their subscription "lost": the app stops recognizing it and demands payment again, often after a phone change or every few months. The person is locked out of the watering schedule their whole care routine for dozens of plants depends on. This runs deeper than an ordinary bug: the mechanism strikes the core value precisely for those who already paid and wove the product into their routine, eroding trust in reliability — and for a habit product, reliable access is the product. Each occurrence pushes the most valuable user to look for a replacement.

For serious growers with dozens-to-hundreds of plants the product scales poorly: no grouping by room, type, or location — everything sits in one long list; you can't assign a plant a spot in the home; you can't back-date a watering you did yesterday (the schedule instantly desyncs). The paradox is that heavy users are the most loyal and paying, yet the interface is built for a beginner with five pots. The lack of collection organization repels exactly the segment that should have been the revenue core.

On top of care, Greg bolts on a game layer — XP points, rankings, "super groups," waitlists, social-network mechanics. For part of the audience this is needless noise: people openly don't get the point system and say it makes a simple task "competitive" and complicates getting to the info they need. The mechanism hurts the utilitarian segment that came for the specific job "when do I water" — the extra complexity raises the barrier to the core, and for busy users becomes a reason not to stay despite the useful substance.