emealia docs · internal 2026-09-11

Market & positioning — the full analysis

The complete internal analysis behind Market reality (which is the condensed, reader-facing synthesis). Rebuilt from scratch from independent and primary sources; every claim carries a source, a date and a confidence. Competitor detail appears here as analysis; the positioning recommendations stay self-standing (no “better than X”).

Built 11 September 2026 · scope: DE + US primary, EU secondary · supersedes prior competitor rounds

How to read this

Every load-bearing statement is tagged so you can see where it comes from and how sure it is. Nothing here is interpreted or embellished; where something is inference it says so, where a figure is missing it says “open”.

Source class
Amt official · Ak academic/peer-reviewed · U independent (press, test portal, professional body) · MF commercial market research · A vendor’s own claim · Aff affiliate/SEO comparison page (often a competitor itself — excluded for opportunity claims)
Confidence
confirmed multiple/primary · plausible one solid source · unconfirmed single weak source or rumour
Ground rules

What didn’t survive verification

Claims the prior material leaned on that did not hold up when checked. They are first because they are why the from-scratch rebuild was necessary.

emealia — fixpoints vs. degrees of freedom

The solution space. Fixpoints are hard limits (by instruction); degrees of freedom are deliberately open.

Fixpoints (non-negotiable)

  • No medical content, no medical app. No diagnosis, therapy or individual medical advice — deliberately not what a ChatGPT would do.
  • No invoicing / CRM platform (minimal at most). Not a practice-management tool.
  • Focus on the client-app core. A thin professional view is conceivable; not a second product.
  • Not a chat interface.
  • Official data first: BLS 4.0 + 4–5 official DBs (Souci·Fachmann·Kraut, Swiss, USDA Foundation, Canadian CNF, French, Chinese, OpenFoodFacts). Unknown foods → a labelled AI estimate (range), quarantined out of reference data, queued for human review.
  • The psyche promise stays: no judgement, no pressure. Weighing / search / barcode possible but not required.
  • MVP stays; new functions arrive normally or as optional add-ons.
  • Web app only (see §Discovery).

Open (“everything possible”)

  • Professional view for counsellors (diary / pattern / target-setting, no billing).
  • Pro features for users (anything beyond the core).
  • Price/model: subscription core; a credits option for DE against subscription fatigue.
  • Which “non-negotiables” end up canonical (no-red etc.).
  • Breadth of audiences (7×/day logger → evening quick-typer; losing weight, observing, families, medical edge-groups with official-standard hints; doctor/counsellor sharing via export or access).
The one structural tension

“Fits any everyday life” (broad capability) pulls against “sharp positioning that gets found” (focus). A position “for everyone” rarely pulls. The resolution to test: a broad product with a focused promise (relief / no judgement) that applies to all because it isn’t a segment feature. Decided on evidence in the positioning section — not asserted as a slogan.

Demand — market size

$113.6→267.4M
Germany, diet/nutrition apps 2024→2030 · CAGR 15.2% · iOS 61% of revenue (Grand View MF)
$673→1,314M
United States 2024→2030 · CAGR 11.6% · US = 31.5% of the world market (Grand View MF)
$2.1→4.6bn
World market 2024→2030 · CAGR 13.4% · North America 36.4% (Grand View MF, confirmed)
DE is small (~5% of the world market) but the fastest-growing market in Europe

Demand — willingness to pay

The central business risk, and the reason the credits idea addresses a real problem.

Demand — what the market actually searches for

Real German search volumes (Keyword Planner, Aug 2025–Jul 2026 U/Amt-adjacent, confirmed). The demand sits in mainstream vocabulary; emealia’s differentiators are barely searched.

~5,000 / mo~500~50~0 / no data
kalorienzähler · kalorienzähler kostenlos · kalorien zählen app · kalorien tracken · abnehm app · ernährungstagebuch abnehmen ohne kalorien zählen · calorie counter app · essenstagebuch ernährungstracker · food diary app · makro/macro tracker · nährwerte app · kalorienzähler ohne anmeldung · ernährungsberatung app · ernährung schwangerschaft app · intuitive eating app · achtsam essen app (−100% YoY) · essen ohne schlechtes gewissen food journal no calories (0) · kalorien zählen ohne wiegen · barcode scanner lebensmittel kalorien · diabetes ernährung app · ozempic ernährung app

Total for the tested set: 32,150 searches/mo (DE); competition on the top terms uniformly “high”. App Store landscape (your own survey): under “Kalorien” a dozen-plus apps, almost all titled “KI Kalorienzähler”; “Essen” is owned by food delivery; “Abnehmen” shows Oviva (DiGA) and weight-loss-for-women clusters.

Four findings that drive positioning
  1. Demand is concentrated in the mainstream words emealia de-emphasises; absolute volumes are small (top terms ~5,000/mo), consistent with a small market.
  2. “kalorienzähler kostenlos” is as large as the base term — a hard price signal, reinforcing the payment barrier.
  3. emealia’s differentiating vocabulary (no-counting / gentle) has almost no search demand → it is a conversion/retention argument, not a discovery channel.
  4. Medical edge-groups generate almost no search (pregnancy 50, diabetes/Ozempic ~0) → value-add and retention, not acquisition.

Demand — segments as jobs, not personas

Evidence-backed contexts, not invented characters.

Demand — retention & engagement reality

Why the category loses people, and the uncomfortable trade-off in the psyche stance.

first-month retention (media.market.us) vs ~3% by day 30 (Business of Apps); definitions differ, both hard
abandon within 2 weeks “if it’s too complex”
+40% / +70%
engagement lift from gamification / notifications

Ratings ≠ retention. Many apps hold 4.5★ and ~3% day-30 retention — ratings come from the minority who fit the method, not the majority who leave. The four documented quit-reasons (perfection pressure, logging fatigue, numbers without meaning, messy real life) are the real story; each maps to an emealia design choice (see §What emealia can stand on).

The uncomfortable trade-off

Gamification/streaks lift engagement (+40%). emealia’s “no streaks” deliberately forgoes a proven retention lever — it is not a free advantage. Retention must be earned another way (usefulness of the read-back, speed, trust, or a non-punitive engagement format — see §Engagement).

Value demand, honestly. The values (no pressure, no judgement) are in demand — visible in abandonment of harsh tracking, a whole anti-diet field, rising “gentle” downloads — but not in search, and already served by several. So they retain and convert; they don’t get you found. Diet plans also fail: ~60% regain, little effect past 24 months (Frontiers 2018 Ak) → supports “small nudge, not a plan.”

Competitive landscape — the segments

The whole field, not just the five emealia is measured against. Competitor claims are vendor material unless marked.

Mainstream trackers

PlayerMechanism / inputPrice / model (2026)Note
MyFitnessPal~20M crowdsourced DB; voice log; AI Coach; ChatGPT integrationFree capped at 5 entries/day + ads; Premium $79.99/yr ($19.99/mo); Premium+ $99.99/yr ($24.99/mo) — 2 sourcesReach (280M); crowdsource DB error-prone (~27% of entries, some >50% off, Nutrition Journal 2019 Ak); privacy suit pending; acquired Cal AI
Cal AI (now MFP)Photo-first estimationHard paywall, ~$29.99/yr>15M downloads <2yr, “tens of millions” ARR; grew via ~250 paid influencers (TheNextWeb 03/2026 U)
Yazio (DE)DB search + barcode; marketed as “AI calorie counter”~€83.90/yr list (heavy discounting/confusion; charged upfront)Market-leader perception DE; highest-rated in FET directory (4.7); AI oversold, not “just barcode” (check-app.de U)
LifesumDB + 2024/25 AI pivot~$44.99/yrHabit/plan focus; complaints on AI accuracy/price after pivot (Aff, not re-verified)
Lose It!DB search~$39.99/yrSimplicity; ~10% DB error (Aff)

Precision trackers

PlayerMechanismPrice (2026)Note
CronometerSearch of lab-verified official DB (680,000+ foods: USDA, NCCDB, Canadian NF); labels source per entry; added AI photo logging Sept 2025 (Gold)Free tier (84 nutrients, verified DB, no ads); Gold $49.99/yr (2 sources), ~$9.99–10.99/moNutrient depth + official provenance with source label — exactly what is often attributed to emealia; slow/“cold”, point numbers not ranges
MacroFactorDB search + adaptive targets from weight trendNo free tier (7–14d trial); $11.99/mo, $71.99/yrAdaptive TDEE is the USP; no desktop
Cronometer’s logging time (your question, checked)

The “45 seconds” is a subjective reviewer impression, and sources disagree: one says ~45 s per meal, another 45–90 s per food item (2–5 min/meal). Only defensible: the search-select-verify flow is noticeably heavier than free text; the exact seconds are not citable as fact.

AI / photo / free-text native

PlayerClaimEvidence status
Welling“2.6 s avg log, 95.6% accuracy over 15,000 meals”; built for non-Western/mixed mealsAll self-reported; no independent verification found A (unconfirmed)
Kalory AIOne-time ~$5, no subscriptionApp Store listing A
SnapCaloriePhoto + depth sensor, ~16% mean errorReview figure Aff

Segment fact: photo-AI error is structurally 0.10–38.3% by meal, 25–35% for mixed dishes (Nutrients 2024 Ak). “Easy AI logging” is table stakes, owned by the largest distributors. None of the checked players shows uncertainty as a range or holds the no-red/no-verdict stance — a design difference, to be re-checked against specific candidates rather than asserted as “nobody.”

German professional / desktop software

SoftwareVendorPlatformPrice (one-time)
PRODINutri-ScienceWindows desktop (client-protocol web widget only; DB: BLS 4.0+3.02, Expert + Souci·Fachmann·Kraut, USDA, AFCD)295–1,995 € + 99–459 €/yr updates
Nutri-GuideNutri-SciencePCfrom ~215 €
EBISproebispro.dePC~400 €
Diät2000 / OptiDiet / DGExpert / …variousPC150–1,500 €

Built for professionals; no consumer product, no free-text/conversational input. — FET e.V. U (confirmed).

Professional platforms (cloud, for counsellors)

PlatformWhat it doesPrice
FoodzillaMeal planning, white-label client app, client mgmt, booking, telehealth, payment processing, per-client targetsfrom $37/mo, free trial + free version; 4.3/5 (47) — GetApp U
NutriumMeal planning, client mgmt, appointments, billing/invoicing, client app, secure messaging, HIPAAfrom $35/feature/mo; 4.2/5 (38) — Capterra U
Cronometer ProDietary analysis for professionals / clinics / researchnot public (“contact vendor”); 4.5/5 (11)

Consequence for a professional view: the bar is high (full planning + app + billing + telehealth from ~$35–37/mo). emealia’s thin, non-clinical layer wins only by staying deliberately simpler — consistent with the “no invoicing/CRM” fixpoint.

Programme / coaching & DiGA (sell a programme, not a tool)

Market saturation & the AI-app bubble

new App Store apps expected 2026 (557k in 2025, record); driven by non-coders using AI tools (TechSpot U)
App Store downloads growth H1 2026 — more apps, flat demand (Sensor Tower)
calorie-counter apps in one directory; “limited differentiation”; paywalls $71.99–299.99/yr

Who is behind it: largely “vibe-coded” apps built on Cursor, Lovable, Replit, Bolt by people with little coding background; Apple is throttling (review times 7–30+ days, update blocks, removals). Quality evidence: audits of 26 AI-built apps found 23 had zero tests, 17/21 no error tracking, 12/14 no rate-limits — problems mostly invisible (security, no tests), not on-screen (axonbuild U). The distinction that matters is engineering discipline, not “built with AI.” A technical founder who adds the invisible infrastructure (tests, auth, rate-limits, error tracking) is on the right side of that line; being AI-assisted is not itself the risk.

Consequence (fact, not judgement)

Visibility is the bottleneck, not the feature. Another “AI calorie counter” without sharp, defensible differentiation disappears into the noise regardless of its quality.

The “unserved niche” premise — on the stand

Prior analyses claimed an empty middle (“numbers without judgement / nutrient focus, that nobody does”). It does not hold.

Verdict: there is no empty niche. What emealia might hold is only the specific combination for a specific person; every single building block is occupied. “We do what nobody does” is false and must not be used.

Data-source reality

Correction, important for positioning.

“Official data” is not a differentiator: Cronometer uses USDA/NCCDB/CNF and labels the source per entry (in its free tier); German professional tools rest on BLS. Crowdsourced DBs (MFP) are the exception at the low end, not the rule. The BLS is licensable (~€100 download / ~€2,000/yr server; Max Rubner Institut, ~15,000 foods × ~130 values). Whether a German consumer tracker uses BLS as its base (as emealia does) is unconfirmed — Yazio/FddB run their own DBs (to verify). emealia’s edge, if any, is the combination (BLS-German accuracy + labelled estimate for unknowns + ranges + speed + no judgement) — each part contested.

Position maps & gaps

Where the field sorts. This is the mapping, not the recommendation.

Evaluation framework

The five verdicts (sensible / desirable / realistic / unrealistic / only-with-budget) are not mutually exclusive — a position can be realistic + desirable + only-with-budget at once. So positions are scored on independent axes; verdicts are derived combinations. Growth is not the top goal — sustainability for one person is.

AxisQuestion
Demand-fitReal demand? Discovery- or retention-relevant?
Differentiation / defensibilityDunford: real alternative, what emealia has that they don’t, “so what”, does it hold vs competition?
Category clarityUnderstood instantly, without teaching a new category?
Marketing pullDoes the message solve a heard problem?
FindabilityServes searched vocabulary / clears the discovery bottleneck?
Buildable & operable (solo)Buildable and sustainably operable by one person (support, content, review queue, regulation)?
Founder-market fitMatches what the founder credibly embodies?
MonetisabilityPays despite the DE barrier?
Unit-economics plausibilityLTV:CAC ≥ ~3:1 under realistic organic acquisition (weighting sustainability over scale)?
Retention / PMF signalReason to believe people stay (against the 3% norm)?
RiskRegulation (MDR), ED-safety, overclaim, platform dependence

The bear case (ungeschminkt)

What works against emealia
  1. Small market; visibility is the bottleneck, not the product. 799+ apps, >1M new/yr, +2% downloads. Distribution is exactly a solo founder’s weakness.
  2. The presumed differentiation is partly occupied. Official data + source label = Cronometer (free). Easy AI logging = MFP/Cal AI, maybe Apple. Cronometer even added photo logging.
  3. The differentiation that remains has no search demand. What gets found ≠ what differentiates.
  4. Germany won’t pay. <50% willing; “kostenlos” a top term; capable free tiers (Cronometer) give official data + nutrients free.
  5. Retention is brutal (~3% D30); the core mechanism (weekly read-back pays off) is unproven.
  6. Distribution asymmetry. Cal AI grew on ~250 paid influencers and six-figure monthly burn; a solo founder can’t mirror that. Build-in-public brings followers, not customers.
  7. Platform risk. Apple may build native logging; it is also throttling the flood — both hit small entrants harder. (For a web app, the App-Store angle is moot, but a native Apple feature still shifts habits.)

Sober probability: a broad consumer position against Yazio/MFP is unrealistic solo. A narrow, sustainable niche is possible but not likely without sharp focus and without several open bets landing.

Position candidates — scorecard

+ advantage/met · o neutral/partly · – disadvantage/not met. Verdicts are combinable.

PositionDemandDiff.PullFind.SoloMonet.Reten.Verdicts (combinable)
P1 · “real numbers / official sources”+oo++oosensible as a findability anchor, not as differentiation
P2 · “without pressure / no judgement”–/+++ (post-click)–+o+sensible + desirable as a promise; unrealistic as discovery
P3 · everyday flexibilityooo–+ooproduct property, weak as standalone position
P4 · “companion, not scoreboard”–o+ (tone)–+—obrand voice, not discovery
P5 · consumer×professional (thin)–o––o/–o+add-on/retention; full tool unrealistic/only-with-budget
P6 · medical edge-groups–o–––o+add-on/retention; medical build forbidden
P7 · family/household?oo–ooofeature; market unproven — verify first
P8 · privacy / no data sale– (search)+o–+—+trust pillar (worth most in DE), not a category
P10 · “deficit view, warm not cold”o+o–+o+secondary differentiation feature
P-niche · everyday-fit + real reason + founder-fito (community)++–+o+sensible + desirable + realistic; slow/organic acquisition
Broad brand vs Yazio/MFP+–o+–o–desirable but unrealistic / only-with-budget

Input modality — text vs. chat (evidence, not creed)

emealia’s “not a chat” stance, tested against HCI evidence.

Direct answers to the critical questions

Is there an “unserved niche” / does everyone use a calorie budget?

No (see §premise). No-counting and nutrient-focus are occupied, growing fields. Only the specific combination + person is open; don’t claim an empty category.

Are emealia’s values actually in demand (not just evidence-based)?

Yes, but hidden (abandonment, anti-diet field), not in search, already served, and hard to monetise; plus the gamification trade-off. They retain/convert; they don’t acquire.

Does the “parents logging in the evening” segment exist? Is batch-logging a USP?

No evidence of a sized/searched segment. Batch/meal-prep is a convenience feature; “evening-parent-logger” is a design persona. A feature, not a positioning — verify with interviews.

Nutrient focus on the home screen — demanded?

Exists (Cronometer/FiberUp/Proto); small search but viable niches. A chooseable focus is a sensible cheap feature (fits the deficit view), not a differentiator — if one, protein.

Suggestions & contributions — what do others offer, what’s missing?

Suggestions are broad (MFP AI Coach/meal plans, MacroFactor adaptive targets, Noom coaching, Foodzilla plan generation) — emealia is behind here, not ahead. emealia’s framing is deliberately a small nudge, not a plan (plans fail); that demand must be verified. Contributions ≈ Cronometer’s per-food nutrient breakdown; the band-contribution view is a UX novelty, not a new capability. The clearest unmet wish is “accurate and simple and not anxiety-inducing” — the contested no-counting/accuracy space.

What emealia can stand on — its own provable claims

Absolute claims demonstrable by a self-test — no comparison needed. This is the recommended way to position, given “no better-than-X.”

Claim 1Speed you can time

“Write down your whole day in a sentence.”

Measure and publish the seconds for an evening entry / a restaurant meal — an absolute number. Answers the top quit-reason (logging fatigue). Honest caveat: “fast and calm,” not “fastest possible” (voice exists).

Claim 2Approximate, but grounded

“Rough numbers from real national food data — and it tells you when it’s a guess.”

Provable in the product; the label is visible. Quality is in the data — the part to protect from overclaim.

Claim 3No judgement, by design

“It never turns red on you.”

Provable because it simply never does it; maps to the perfection-pressure quit-reason.

Claim 4Privacy as a product value

“No ads, nothing sold, data in the EU.”

Worth paying for in DE/EU specifically (privacy premium); much less in the US. A reason to weight markets.

Recommended architecture (with the caveats)

Found as a calorie tracker · convinced by calm, honest, judgement-free logging against German data · kept by usefulness + trustNot one slogan — three layers, because discovery and differentiation are separate jobs.

Engagement without the harm

Discovery for a web-only product

Web app → App-Store findability is irrelevant; channels differ, and the keyword demand matters more (Google is the front door).

Founder & privacy as trust — not growth

Genuine asset

  • Real founder-market fit (Hashimoto, hard pregnancy, postpartum iron deficiency, overwhelmed by conflicting advice).
  • Women’s health is large, underserved, investable (~$1T gap by 2040; funding grew even in a down market — Morgan Stanley U).
  • A named person vs an anonymous, tool-generated flood is a trust and durability signal.
  • Privacy premium makes “no ads / no data sale” a paid-for value in DE.

Not a growth engine

  • Build-in-public brings followers, not customers (Indie Hackers U).
  • Doesn’t fix discovery or the payment barrier alone.
  • Being AI-assisted is fine only with the invisible engineering the flood skips (tests, auth, rate-limits). Founder’s technical background makes that possible, not automatic.

Markets

Core
Where the values are worth paying for.
DE / DACH & privacy-conscious EUPrivacy premium, German-data accuracy, fastest-growing EU market. Web app makes multi-country cheaper.
Plausible
Second, not first.
CanadaBilingual, official CNF data already held, less saturated than the US.
Hardest
Largest but least suited to a paid solo product.
United StatesBiggest market, lowest privacy WTP, most saturated, most free-tolerant.

Monetisation & price

Tracker cluster ~€5–10/mo (Cronometer Gold $49.99/yr [2 sources], MacroFactor $71.99/yr, MFP Premium $79.99 / Premium+ $99.99, Yazio ~€83.90). Programme cluster (Noom ~$70/mo, Alma $199/yr) is irrelevant. emealia (subscription + credits, no free-forever) competes fairly on price with the paid tiers; the harder competition is the free tiers — a capable free tier gives official data + nutrients at no cost, and “free” is a top search term. The real question is what the paid experience gives that a free tier doesn’t (calm speed, no judgement, German-data accuracy, privacy), and whether credits + try-without-payment-data lowers the German barrier. Unproven; test early. At ~3% D30 retention and a small niche, unit economics are fragile without proven retention — and growth is not the goal; sustainability (retention × pay-rate) is.

Second strand: a free tracker, paid AI

A hypothesis to run in parallel to the “paid, no free-forever” assumption: because emealia will hold a curated official database, the plain tracker — manual search + barcode logging against that database, with emealia’s calm ranges, no judgement, German data and privacy — could be offered free, while the AI free-text flow, estimation and suggestions sit behind subscription or credits. Is that sensible, especially in Germany?

near-zero
marginal cost to serve a database-search log, vs. a real per-log LLM cost for AI free-text — the split matches cost to price
2–8%
typical freemium free→paid at 30 days (well-run apps; >5% is strong; AppsOps 2026) — DE likely at the low end
+15–25%
more 12-month revenue from freemium vs. a hard paywall (Adapty 2026); hard paywall wins immediate starts, freemium wins LTV and suits daily-habit trackers

Why it is sensible

  • Cost aligns with price. The AI flow carries a real per-log cost; database search is ~free to serve. Giving away the zero-cost part and charging for the expensive part is structurally sound.
  • It fits Germany. “kostenlos” is as large a search term as the base term; a genuinely useful free tier enters the “free calorie tracker” consideration set — a real discovery asset for a web app with no ad budget — and a fair, no-trap free offer is on-brand where privacy and fairness are valued.
  • It fits the model evidence. Freemium/limited-free suits strong daily-habit trackers and yields ~15–25% more 12-month revenue than a hard paywall (Adapty). Since growth is explicitly not the goal and sustainability/LTV is, that trade favours a free tier.
  • The values travel for free. No judgement, ranges, official German data and privacy are design and data — not AI — so the free tier still carries emealia’s stance, not a hollow tracker.

Why it can backfire

  • It hides the one differentiator. The fast free-text AI is emealia’s edge and its answer to the #1 quit-reason (logging fatigue). A manual-search free tier is exactly the slow experience people quit — undifferentiated, and weaker than a leading free tier on database depth. First impression: “just another calorie counter.”
  • It exposes the database-miss wall. The AI estimate exists precisely to rescue “your dinner isn’t in here.” Remove it from the free tier and free users hit that wall — the worst possible first experience — on exactly the foods a curated database won’t cover.
  • Conversion is the hard part, more so in DE. Freemium converts in low single digits; a large manual-logging free base can mean infrastructure and support load with little revenue.
  • It can cannibalise the best-fit payers. The disciplined “observe my nutrition” user — arguably emealia’s most aligned — may happily log manually for free and never need the AI.
  • Users can’t feel the magic before paying — a weak conversion trigger for the very thing that sells the product.

The pivot: don’t hide the magic — let people taste it (credits)

The failure mode above comes from putting all AI behind the wall. The benchmark evidence points the other way: freemium works when users can sample the core before the paywall. The credits model resolves it — free tier = unlimited manual database tracking + a bucket of free AI credits so the fast free-text flow is actually felt; then a subscription or more credits for continued/heavy AI. This caps AI cost (credits bound the spend), gives the differentiator a chance to convert, and is maximally on-brand for Germany (“free to use, AI when you want it” — no subscription trap).

Where each version lands (verdicts are combinable)

It does not remove the core monetisation bet — it reshapes it: the question becomes “do enough free users, having tasted the AI, pay for more?” That is testable early with the credits mechanic, and should be tested before a free tier is committed to.

What emealia must do (build / change / reduce)

The three bets everything rests on

  1. Does the weekly read-back teach anyone anything? (retention core — 5 interviews)
  2. Do credits + try-without-payment-data carry the German payment barrier against strong free tiers?
  3. Is there a warm way in — a niche community or women’s-health media route?

Honest verdict

Themes to validate, not assume

Near-primary evidence: what users say (Sept 2026 update)

Added after a review-mining pass and a check of emealia’s own feedback files. Google Trends was attempted directly via the browser and returned HTTP 429 (automated access blocked); the Keyword Planner volumes above are the stronger source in any case (absolute, not relative).

emealia’s own feedback files are development notes, not market evidence

The alpha/prototype/product feedback in the repo is the founder’s own build-and-design log and bug reports (draft→logged flow, band-vs-number decisions, the suggestion box, favourites for re-logging) — valuable for product intent, but not end-user demand data. The primary-market question (do target users have the pain, want the relief-not-precision frame, and pay?) remains open and needs interviews.

Unmet needs, from competitor reviews

Recurring signalWhere seenReading for emealia
Database inaccuracy is the #1 trust complaintReddit synthesis; MyFitnessPal forumsConfirms accuracy/provenance as a felt need — but it must be shown, not claimed
Feature-bloat resented — “jack of all trades, master of none”; search got slower; peripheral features (scores, podcasts, coaching) crowd the coreCronometer forumStrong support for a calm, focused, fast core; the direction to protect is restraint, not more features
Paywalls on basic tracking + clunky UIReddit synthesisThe free-tier/price tension again; a calm, clear UI is valued
Speed / effortless logging valued; voice explicitly wished forReddit synthesisReinforces fast entry as the felt need — and that voice is a demanded modality (a real check on any “text is fastest” claim)
Community/accountability valued by someReddit synthesisA lever emealia’s no-social/no-pressure stance forgoes — a conscious trade-off, not an oversight
One-size-fits-all disliked; personalised goals valuedReddit synthesisSupports a chooseable focus / personalised targets (already in the product intent)

Net: the felt needs are accurate, fast, simple, fairly priced, personalised — and bloat is actively punished. This lines up with the four quit-reasons and argues for depth over breadth: refine the core, resist feature accretion, prove accuracy and speed. The two demanded things emealia deliberately omits — voice and community — are trade-offs to make consciously, not gaps to fill by reflex.

Data-source check: Yazio (the DE market leader)

Yazio runs a large mixed database with a per-country “Food Database Country” setting and ~6.1% average deviation from lab measurement (mid-table); it does not advertise official-source (BLS) provenance or per-entry source labels. So emealia’s BLS-first, source-labelled base remains a plausible German-accuracy differentiator against the market leader — still to be confirmed by a direct food-by-food comparison, not asserted. — Yazio Help Center / calorie-trackers.com 2026 U/A.

Sources