385 lines
19 KiB
TypeScript
385 lines
19 KiB
TypeScript
export type CompetitorSlug = 'picturethis' | 'plantum'
|
|
|
|
export interface ComparisonThesis {
|
|
title: string
|
|
greenlens: string
|
|
competitor: string
|
|
}
|
|
|
|
export interface ComparisonCategory {
|
|
title: string
|
|
greenlens: string
|
|
competitor: string
|
|
whyItMatters: string
|
|
}
|
|
|
|
export interface EmergencyScenario {
|
|
symptom: string
|
|
greenlens: string
|
|
competitor: string
|
|
}
|
|
|
|
export interface ComparisonFaq {
|
|
question: string
|
|
answer: string
|
|
}
|
|
|
|
export interface CompetitorProfile {
|
|
slug: CompetitorSlug
|
|
name: string
|
|
metaTitle: string
|
|
metaDescription: string
|
|
heroSummary: string
|
|
heroVerdict: string[]
|
|
disclaimer: string
|
|
lastVerified: string
|
|
competitorSnapshot: string
|
|
greenLensPositioning: string
|
|
whyPeopleCompare: string[]
|
|
theses: ComparisonThesis[]
|
|
categories: ComparisonCategory[]
|
|
greenLensBestFor: string[]
|
|
competitorBestFor: string[]
|
|
emergencyScenarios: EmergencyScenario[]
|
|
faqs: ComparisonFaq[]
|
|
}
|
|
|
|
export const competitorProfiles: Record<CompetitorSlug, CompetitorProfile> = {
|
|
picturethis: {
|
|
slug: 'picturethis',
|
|
name: 'PictureThis',
|
|
metaTitle: 'GreenLens vs PictureThis',
|
|
metaDescription:
|
|
'Compare GreenLens vs PictureThis for plant emergencies, next-step diagnosis, pricing friction, and care guidance. See when GreenLens is the better fit.',
|
|
heroSummary:
|
|
'PictureThis is one of the best-known plant ID apps on the market, but GreenLens is built for a different moment: when your plant already looks wrong and you need the next correct action, not another generic care checklist.',
|
|
heroVerdict: [
|
|
'Choose GreenLens if your real question is what to do next about yellow leaves, soft stems, or a sudden decline.',
|
|
'Choose PictureThis if your priority is broad plant identification and a large reference library first.',
|
|
'Do not assume a rigid watering calendar is safer. For stressed plants, that habit often creates the next mistake.',
|
|
],
|
|
disclaimer:
|
|
'Pricing, trials, and feature gates can change by market and over time. This page reflects the current research summary used for GreenLens landing content.',
|
|
lastVerified: 'April 10, 2026',
|
|
competitorSnapshot:
|
|
'PictureThis is the category leader for mainstream plant ID. It is commonly associated with a large botanical database, fast scan-to-name results, and an aggressive subscription flow that many users describe as frustrating during onboarding.',
|
|
greenLensPositioning:
|
|
'GreenLens is the plant ER angle: situational triage, calmer next-step guidance, and a clearer path from symptom to action when a plant suddenly starts struggling.',
|
|
whyPeopleCompare: [
|
|
'They can identify a plant, but still do not know what to do after the scan.',
|
|
'They want help with emergencies, not just an encyclopedia in their pocket.',
|
|
'They are tired of paywall pressure before they feel confident about the diagnosis.',
|
|
],
|
|
theses: [
|
|
{
|
|
title: 'Subscription pressure vs calmer triage',
|
|
greenlens:
|
|
'GreenLens is positioned to get users to the situation first and the decision second, without making the panic moment feel like a billing funnel.',
|
|
competitor:
|
|
'PictureThis is widely known for aggressive paywalls and hard-to-dismiss upgrade prompts before trust is fully earned.',
|
|
},
|
|
{
|
|
title: 'Calendar reminders vs situational judgment',
|
|
greenlens:
|
|
'GreenLens frames care around what changed, what the soil feels like, and what happened in the last 14 days.',
|
|
competitor:
|
|
'PictureThis leans on scheduled care reminders that can encourage overwatering when symptoms are misread.',
|
|
},
|
|
{
|
|
title: 'Generic suggestions vs the next right step',
|
|
greenlens:
|
|
'GreenLens focuses on one clear next move: check the soil, stop fertilizing, review the recent change, or isolate the cause.',
|
|
competitor:
|
|
'PictureThis disease and health guidance often lands on broad advice such as more light or more fertilizer, even when the user needs sharper triage.',
|
|
},
|
|
],
|
|
categories: [
|
|
{
|
|
title: 'Plant emergencies',
|
|
greenlens:
|
|
'Built around fast triage for visible problems like yellow leaves, mushy stems, droop after repotting, or sudden decline.',
|
|
competitor:
|
|
'Strong at telling you what the plant is, less convincing when the real problem is deciding the safest next intervention.',
|
|
whyItMatters:
|
|
'A stressed plant does not need more content. It needs the next low-risk action that prevents the owner from making things worse.',
|
|
},
|
|
{
|
|
title: 'Identification and plant database',
|
|
greenlens:
|
|
'Useful when identification is part of the rescue flow, but not positioned as the largest encyclopedia in the category.',
|
|
competitor:
|
|
'This is the core PictureThis strength: broad species coverage and fast recognition backed by a very large library.',
|
|
whyItMatters:
|
|
'If naming the plant is the end goal, PictureThis is strong. If naming the plant is just step one, GreenLens has a clearer story.',
|
|
},
|
|
{
|
|
title: 'Care philosophy',
|
|
greenlens:
|
|
'Situational care. The app should ask what changed recently and whether the soil or environment actually supports the next move.',
|
|
competitor:
|
|
'Calendar-driven care plans and reminders that can feel tidy, but often miss the context that matters most for beginners.',
|
|
whyItMatters:
|
|
'Strict calendars are one of the easiest ways to overwater a plant that already shows stress.',
|
|
},
|
|
{
|
|
title: 'Diagnosis output',
|
|
greenlens:
|
|
'Prioritizes a smaller number of concrete interventions with clearer sequencing and less noise.',
|
|
competitor:
|
|
'Often returns generic advice that sounds plausible but does not reduce uncertainty enough for first-time plant owners.',
|
|
whyItMatters:
|
|
'The user is not buying a list of possibilities. They are trying to avoid the wrong action today.',
|
|
},
|
|
{
|
|
title: 'Pricing and trust',
|
|
greenlens:
|
|
'Paid features still exist, but the brand story is fairer and more transparent than hiding the choice behind manipulative UI.',
|
|
competitor:
|
|
'PictureThis is frequently criticized for paywall-first moments, especially around trials and dismiss states.',
|
|
whyItMatters:
|
|
'Trust matters more when someone is already anxious about killing a plant.',
|
|
},
|
|
{
|
|
title: 'Beginner clarity',
|
|
greenlens:
|
|
'Designed to calm the situation down and turn a messy symptom into a single next step.',
|
|
competitor:
|
|
'The app gives users a lot of information quickly, which is helpful for reference and less helpful for triage.',
|
|
whyItMatters:
|
|
'Beginners rarely need more detail first. They need a better decision path.',
|
|
},
|
|
],
|
|
greenLensBestFor: [
|
|
'People dealing with a plant that looks wrong right now and want the safest next step.',
|
|
'Beginners who need triage, not a full plant encyclopedia.',
|
|
'Users who distrust manipulative subscription flows and want clearer product positioning.',
|
|
],
|
|
competitorBestFor: [
|
|
'Users who mainly want broad plant identification from a very large reference database.',
|
|
'People who enjoy an all-purpose plant encyclopedia and do not mind more aggressive upsell patterns.',
|
|
'Plant owners whose first question is what the plant is, not how to stabilize it.',
|
|
],
|
|
emergencyScenarios: [
|
|
{
|
|
symptom: 'Yellow leaves after a recent move',
|
|
greenlens:
|
|
'GreenLens frames the issue around the recent change, environment shift, and whether watering behavior also changed.',
|
|
competitor:
|
|
'PictureThis may still identify the plant correctly, but the next-step guidance is more likely to stay broad and less situational.',
|
|
},
|
|
{
|
|
symptom: 'Soft stems or signs of overwatering',
|
|
greenlens:
|
|
'GreenLens emphasizes checking moisture and stopping instinctive “care stacking” before adding fertilizer or another routine task.',
|
|
competitor:
|
|
'A calendar-driven reminder model can push users toward the exact behavior that created the problem.',
|
|
},
|
|
{
|
|
symptom: 'Sudden decline with unclear cause',
|
|
greenlens:
|
|
'GreenLens narrows the response to the next safest action instead of overwhelming the user with a long diagnosis tree.',
|
|
competitor:
|
|
'PictureThis is more useful as a reference layer than as a focused emergency workflow.',
|
|
},
|
|
],
|
|
faqs: [
|
|
{
|
|
question: 'Is GreenLens more accurate than PictureThis for plant identification?',
|
|
answer:
|
|
'GreenLens does not need to win the encyclopedia race to be the better choice in a plant emergency. PictureThis is still stronger if broad ID coverage is your main requirement. GreenLens is stronger when the real job is choosing the next action after the scan.',
|
|
},
|
|
{
|
|
question: 'Why compare GreenLens and PictureThis if both use AI?',
|
|
answer:
|
|
'Because they optimize for different outcomes. PictureThis is strongest as a mainstream identification and reference app. GreenLens is framed around triage, situational care decisions, and calmer guidance when something is already going wrong.',
|
|
},
|
|
{
|
|
question: 'Does GreenLens replace watering calendars?',
|
|
answer:
|
|
'It replaces the idea that a calendar alone is enough. GreenLens emphasizes what changed, what the soil feels like, and whether a plant is showing stress before another routine task is triggered.',
|
|
},
|
|
{
|
|
question: 'Does GreenLens also have paid features?',
|
|
answer:
|
|
'Yes. GreenLens includes paid functionality such as subscriptions and AI-related credits. The difference in this comparison is the positioning: the diagnosis moment should feel clearer and fairer, not like a hidden-dismiss billing trap.',
|
|
},
|
|
],
|
|
},
|
|
plantum: {
|
|
slug: 'plantum',
|
|
name: 'Plantum',
|
|
metaTitle: 'GreenLens vs Plantum',
|
|
metaDescription:
|
|
'Compare GreenLens vs Plantum for plant diagnosis, care workflows, pricing friction, and beginner clarity. See why GreenLens is the better plant ER choice.',
|
|
heroSummary:
|
|
'Plantum markets itself as a high-accuracy, all-in-one plant care assistant. GreenLens is the sharper choice when the user does not want an all-in-one system right now, but a clear answer to what to do next for a struggling plant.',
|
|
heroVerdict: [
|
|
'Choose GreenLens if you want triage, not another stack of care hacks and tasks.',
|
|
'Choose Plantum if you want a broader all-in-one assistant with more expansive care reporting.',
|
|
'If the plant is already in trouble, clarity beats completeness.',
|
|
],
|
|
disclaimer:
|
|
'Pricing, feature limits, and diagnosis depth can change by region and plan. This page reflects the current research summary used for GreenLens landing content.',
|
|
lastVerified: 'April 10, 2026',
|
|
competitorSnapshot:
|
|
'Plantum, formerly NatureID, competes on AI precision, plant disease reports, and the promise of being a full care assistant. It often looks more detailed than GreenLens at first glance, but that detail can turn into checklist overload for beginners.',
|
|
greenLensPositioning:
|
|
'GreenLens is the anti-actionism option: diagnose the situation, reduce noise, and recommend the next lowest-risk step instead of flooding the user with tasks.',
|
|
whyPeopleCompare: [
|
|
'They want help with a sick plant but do not want to decode a long report.',
|
|
'They are looking for a realistic alternative to rigid plant journals and task stacks.',
|
|
'They want a tool that helps them decide, not just one that generates more plant-care output.',
|
|
],
|
|
theses: [
|
|
{
|
|
title: 'Actionism vs next-step clarity',
|
|
greenlens:
|
|
'GreenLens reduces the problem to the next clear intervention instead of rewarding users with a longer checklist.',
|
|
competitor:
|
|
'Plantum can feel thorough, but the volume of advice often creates urgency and overreaction rather than confidence.',
|
|
},
|
|
{
|
|
title: 'Plant ER vs all-in-one care assistant',
|
|
greenlens:
|
|
'GreenLens is strongest when the user is already worried and needs triage first.',
|
|
competitor:
|
|
'Plantum is built as a broad assistant with journals, tasks, and deeper care material around each plant.',
|
|
},
|
|
{
|
|
title: 'Situational care vs rigid task systems',
|
|
greenlens:
|
|
'GreenLens emphasizes recent change, soil condition, and symptom severity over routine schedules.',
|
|
competitor:
|
|
'Plantum still leans on structured care workflows that can miss whether the current advice matches the actual state of the plant.',
|
|
},
|
|
],
|
|
categories: [
|
|
{
|
|
title: 'Diagnosis depth',
|
|
greenlens:
|
|
'GreenLens goes narrower and sharper: fewer steps, stronger sequencing, more focus on what to do now.',
|
|
competitor:
|
|
'Plantum often presents a more detailed health report and a denser care framework around the diagnosis.',
|
|
whyItMatters:
|
|
'Detail can look impressive while still failing the anxious beginner who needs one confident decision.',
|
|
},
|
|
{
|
|
title: 'Beginner usability',
|
|
greenlens:
|
|
'Built to calm the situation down and reduce the chance of stacking too many fixes at once.',
|
|
competitor:
|
|
'Plantum can overwhelm newer plant owners with too many care hacks, checks, and supporting explanations.',
|
|
whyItMatters:
|
|
'In plant care, too many “helpful” tasks often create the next error.',
|
|
},
|
|
{
|
|
title: 'Care tracking model',
|
|
greenlens:
|
|
'GreenLens frames care around evidence from the plant and the recent environment, not routine by default.',
|
|
competitor:
|
|
'Plantum includes journals and care tasks, but the structure still tends to pull users into predefined care systems.',
|
|
whyItMatters:
|
|
'A system is only useful if it matches the current state of the plant.',
|
|
},
|
|
{
|
|
title: 'Pricing friction',
|
|
greenlens:
|
|
'GreenLens can still monetize advanced AI help, but the value story is clarity and fairness at the decision point.',
|
|
competitor:
|
|
'Plantum typically gates deeper diagnosis and larger plant management needs behind subscription pressure.',
|
|
whyItMatters:
|
|
'People comparing alternatives often feel they are paying for complexity before they see clear help.',
|
|
},
|
|
{
|
|
title: 'Plant identification',
|
|
greenlens:
|
|
'Identification supports the diagnosis flow, but GreenLens is not positioned as the broadest species database.',
|
|
competitor:
|
|
'Plantum markets strong identification depth, often with claims around tens of thousands of species and very high accuracy.',
|
|
whyItMatters:
|
|
'If you mainly want a broad AI plant assistant, Plantum stays credible. If you need triage, GreenLens is easier to justify.',
|
|
},
|
|
{
|
|
title: 'Outcome for stressed plants',
|
|
greenlens:
|
|
'The product story is built around the next right move: inspect moisture, review the last change, and avoid reactive care stacking.',
|
|
competitor:
|
|
'Plantum can generate a more comprehensive response, but not always a more usable one under stress.',
|
|
whyItMatters:
|
|
'The best care plan is the one a worried beginner can actually follow correctly.',
|
|
},
|
|
],
|
|
greenLensBestFor: [
|
|
'Plant owners who want a practical rescue workflow instead of a bigger care system.',
|
|
'Beginners who get overwhelmed by long disease reports and plant-care checklists.',
|
|
'Users who care more about the next safe action than a full assistant dashboard.',
|
|
],
|
|
competitorBestFor: [
|
|
'Users who want a richer all-in-one plant assistant with more structured care content.',
|
|
'People who are comfortable interpreting longer reports and broader care workflows.',
|
|
'Plant owners who want journals, tasks, and a deeper “care assistant” feel around every plant.',
|
|
],
|
|
emergencyScenarios: [
|
|
{
|
|
symptom: 'Yellow leaves with no obvious cause',
|
|
greenlens:
|
|
'GreenLens narrows the response to what changed recently and what the safest next check is before the user starts “doing more.”',
|
|
competitor:
|
|
'Plantum is more likely to send the user into a broader diagnostic and care framework that feels complete but slower to act on.',
|
|
},
|
|
{
|
|
symptom: 'Soft stems or soggy soil',
|
|
greenlens:
|
|
'GreenLens keeps the focus on stopping the wrong behavior first instead of layering more plant-care tasks on top.',
|
|
competitor:
|
|
'Plantum can provide extensive advice, but more depth is not always better when the likely issue is already over-care.',
|
|
},
|
|
{
|
|
symptom: 'Multiple symptoms after a repot or environment shift',
|
|
greenlens:
|
|
'GreenLens frames the situation around the recent change event and next low-risk step.',
|
|
competitor:
|
|
'Plantum offers more reporting, but that can still leave the user deciding among too many actions at once.',
|
|
},
|
|
],
|
|
faqs: [
|
|
{
|
|
question: 'Is GreenLens less powerful than Plantum because it is simpler?',
|
|
answer:
|
|
'Not for the job GreenLens is trying to do. Plantum offers a wider assistant model. GreenLens intentionally narrows the workflow so a stressed plant owner gets to the next decision faster.',
|
|
},
|
|
{
|
|
question: 'Who should still choose Plantum over GreenLens?',
|
|
answer:
|
|
'Choose Plantum if you want a more expansive all-in-one care assistant, broader reporting, and a more structured plant-management experience around each plant.',
|
|
},
|
|
{
|
|
question: 'Why does GreenLens emphasize triage instead of full care plans first?',
|
|
answer:
|
|
'Because the biggest beginner mistake is often reacting too fast with too many fixes. GreenLens is designed to reduce that risk by sequencing the next step more clearly.',
|
|
},
|
|
{
|
|
question: 'Does GreenLens ignore long-term care tracking?',
|
|
answer:
|
|
'No. GreenLens still supports ongoing care and collection management. The difference is that the comparison pages prioritize its emergency and decision-support value over the promise of being an all-in-one assistant for everything.',
|
|
},
|
|
],
|
|
},
|
|
}
|
|
|
|
export const competitorOrder: CompetitorSlug[] = ['picturethis', 'plantum']
|
|
|
|
export function getCompetitorBySlug(slug: string): CompetitorProfile | undefined {
|
|
if (slug === 'picturethis' || slug === 'plantum') {
|
|
return competitorProfiles[slug]
|
|
}
|
|
|
|
return undefined
|
|
}
|
|
|
|
export function getPeerCompetitors(currentSlug: CompetitorSlug): CompetitorProfile[] {
|
|
return competitorOrder
|
|
.filter((slug) => slug !== currentSlug)
|
|
.map((slug) => competitorProfiles[slug])
|
|
}
|