emealia docs · internal 2026-08-06

Where emealia actually stands

A cross-read of three sources that had drifted apart: the management documents (emealia-mgmt/), this documentation set, and the shipped implementation (emealia-app/). Everything below is verified against code and the implementation plan, not against intent.

Assessed 2026-08-06 · sources: 2026-08 competitor analysis, 2026-07-07 market analysis, 278-story implementation plan, frontend + backend source

212/278
stories done across 29 epics — 76%
18/18
daily-view epic complete, incl. contributions + weekly
of 10 coaching stories done — suggestions not delivered
2
human gates still unrun (G1 bands, G2 calibration)
€39.99
annual price vs. Yazio ~€83.90 · MFP $79.99+

Bottom line

The product is further along than any of its documents say, and its market is worse than any of its documents say. Those two facts pull in opposite directions and they define this moment.

On the build side: the core loop is complete. Free-text logging, honest ranges, band states, the no-failure guarantee, all-details, history, statistics, weight, day context, offline queue, trial + Stripe, GDPR export/erasure — shipped and tested. Two features the August competitor analysis flags as strategic and unmatched in the fieldnutrient contributions and multi-meal logging — are not roadmap items. They are in production. A third, the weekly nutrient view, which the same analysis lists as a "strong candidate" to scope, shipped as stories 2.11a–2.11c before the analysis was written.

On the market side: between the July and August analyses, MyFitnessPal absorbed Cal AI, Apple began building nutrition logging into the platform, and easy AI input stopped being a differentiator. The strategy documents, the landing page, and the pitch all still lead with easy. That is now the one claim the two largest distributors in the category can match for free.

The single most important correction

Stop leading with ease. Lead with the frame. "Meal tracking made easy" is a claim MyFitnessPal can now match. "Eat by feel, not by math" cannot be matched by anyone whose product is a number — and Apple, whose entire behavioural vocabulary is rings and goal closure, structurally will not ship it.

What changed, and what it means

1 · The build passed the documents

The implementation plan is the only source that reflects reality. This documentation set described a July product; emealia-mgmt/3-design.md still specifies a colour palette the app replaced weeks ago; the August competitor analysis assesses "feature additions" as if two of them were proposals. All three have now been reconciled here.

Claim in the older documentsReality in the code
Band contributions are a promising new addition to assessShipped core/nutrient_contributions.py, GET /nutrients/{n}/contributions, NutrientContributionPanel.vue — day and week windows, midpoint shares, top-N + "the rest"
Multi-meal logging is a new addition to assessShipped stories 18.7–18.9: one AI call segments a text into up to 8 meals, N drafts, one credit per batch, per-card confirm and discard
A weekly nutrient view is a "strong candidate — medium cost"Shipped GET /weekly, Today ↔ This-week tabs, and a last-7-days tab on All details
Design palette #1A201C forest-green groundReplaced Deep Oceanic Slate: #11161B ground, #1C242C surface, peach accent retained. This doc set now matches.
Suggestions layer "underdeveloped"Accurate — generation exists, delivery (story 4.5) is unbuilt. The one place the documents were not too pessimistic.

2 · The wedge moved

The July analysis treated Cal AI as proof that a low-friction upstart beats incumbents. That window closed by acquisition, not by competition. MyFitnessPal now owns both the largest food database and the best consumer AI-input funnel, and Apple is commoditising basic logging to zero for a very large installed base.

What survived intact is the frame — ranges instead of point numbers, bands instead of a budget, no red, no streaks, no verdict. Nobody credible competes there. Eight rows of the competitive feature matrix are uncontested, and those eight rows are the entire product thesis. Full analysis →

3 · Two scandals became free marketing

MyFitnessPal moved photo logging, recipe import and per-meal macro targets behind Premium in May 2026 and caught a consumer class action for still marketing itself as "free". Yazio's German list price reached €83.90/yr with rotating discounts and a trial available only on the web. Both write emealia's first two comparison pages for it, honestly. Marketing plan →

The gap list

Ordered by how much damage each does if it is not addressed. Everything here is actionable now.

#GapWhy it mattersSeverity
1 The public site advertised a 7-day trial the product does not offer. Six occurrences of "7 Tage" on the German landing page against a shipped UsageMeter of 30 AI credits. Corrected 2026-08-06 — the rebuilt landing page states the credit trial everywhere. The design doc's "7-day-trial CTA" copy standard still needs the same correction. A direct competitor is currently facing a class action over inaccurate "free" marketing. This was a legal exposure, not a copy nit — and it undermined the one-price-honest positioning the whole strategy rests on. Fixed
2 Contribution copy has no shipped guardrail. The feature is live; the ordering, labelling and "still estimating" rules exist as analysis, not as acceptance criteria. Attribution is one word away from blame. "71% of your fat came from the pesto pasta" is an accusation if the copy implies fault. This is the highest ED-safety risk surface in the product and it shipped without a written copy contract. High
3 Suggestions do not reach the user. GenerateDailySuggestion and the eligibility policy are built and tested; story 4.5 — persistence and delivery — is not. Daily tip open rate is a named KPI (≥15% at M3) and a kill condition. It cannot be measured, because no tip is delivered. Meanwhile every competitor is shipping an AI coach. High
4 Both human gates are unrun. G1 (5 testers understand bands unaided) and G2 (30 real meals, correction rate <40%). G1 is stated as required before the Today UI is finalised — the UI is finalised. G2 gates acquisition spend. Neither can be delegated to an agent. High
5 The medical / general-wellness disclaimer is blocked on counsel (H10). Research and draft EN/DE copy exist; sign-off does not. Launch blocker. Positioning as a general-wellness product rather than a medical device depends on wording nobody has approved. Blocker
6 EU AI Act Art. 50 has no line item. Transparency obligations became enforceable 2 August 2026. emealia complies in substance already — every estimate is labelled an estimate and shown as a range. It lacks the explicit disclosure placement at onboarding and at the meal-input surface. Cheap to fix, and a strong DE marketing argument next to DSGVO. Medium
7 Auth is documented two ways. Strategy says social-only, no email/password (founder decision 2026-07-08). The design doc's login-screen standard still says "email + Google + Apple together". Social-only is the anti-abuse mechanism behind the soft paywall. An email path reopens it. One of the two documents is wrong and the code should settle it. Medium
8 Three features nobody else has are not marketed. Contributions, multi-meal logging and the weekly view are invisible on the public site. "Log your whole day in one sentence" is verifiably unique in the field right now and directly answers the category's best-documented complaint. Zero build cost. Medium
9 Eating out, shared dishes and non-Western cuisines already work and are never claimed. Free text handles "the chicken tikka masala at the Indian place" natively; a database product structurally cannot. The structural failure mode of every competitor, answered by accident, unmentioned. In Germany the cuisine point reaches a large population no competitor addresses. Medium
10 Observability and AI-cost optimisation are thin. Epic 15 is 2/4; epic 21 is 1/8. "AI cost > €0.08/user/month" is a kill condition. Detecting it requires the instrumentation that is not finished. Medium

What is genuinely strong

01
The frame is uncontested
Ranges, no numbers on the main view, no red, no streaks, no verdict. Still nobody in the mainstream. Supported by Frech 2022 (precise ≈ round goals) and Levinson 2017 (73.1% of affected MFP users saw the app as contributing to their eating disorder).
02
Two features nobody has
Retrospective non-numeric contributions and true batch free-text logging. Both are consequences of the free-text architecture rather than bolt-ons, which is what makes them hard to copy.
03
Price and clarity
€39.99/yr against Yazio's ~€83.90 and MFP's $79.99–99.99. One plan, everything in it, no tiers — against a competitor in active litigation over exactly this.
04
Privacy posture as product
EU residency, a single processor DPA, no data sale, no ad SDKs. In Germany this is a purchase argument, not a footnote — and it appreciates as the platform layer gets more intimate.
05
Zero-cost intelligence
Contributions are deterministic arithmetic over data already in daily_summaries. No AI call, no tokens, no hallucination surface. Features that raise perceived intelligence while lowering COGS are rare.
06
PWA independence
No App Store cut, no review risk, no platform gatekeeper, instant deploys — and it covers Android, desktop, German-language nuance and EU residency, all outside Apple's centre of gravity.

Real exposures

  1. Discovery. No App Store means no store search, no charts, no default placement. 100% of acquisition is content, comparison SEO and creator outreach — and the "best app 2026" review ecosystem is largely owned by competing apps' own content marketing. This is the biggest go-to-market risk and no feature fixes it.
  2. Apple. Free native nutrition logging plus a paid AI coach, pre-installed, on the largest high-willingness-to-pay base. Everything generic is being commoditised.
  3. MyFitnessPal + Cal AI. The easy-input wedge is gone.
  4. The German payment paradox is unchanged. ~76% willing to use mHealth apps, ~27% willing to pay out of pocket, ~25% of German smartphone users already have a weight or nutrition app installed. Still the central bet.
  5. Coaching maturity gap. Not a breadth problem to solve — a restraint position to occupy. But right now there is neither breadth nor a delivered tip.
  6. No wearable or health-platform sync, and structurally limited options: HealthKit and Health Connect are native-only APIs, unavailable to a PWA at any price.

The next five moves

In order. The first three cost nothing to build.

#MoveCostOwner
1Fix the trial mismatch on the public sitedone 2026-08-06. Remaining: the same correction in 3-design.md's copy standardMinutesFounder
2Re-lead the positioning on the framedone 2026-08-06. The rebuilt landing page leads with "Eat by feel, not by math"; easy is now the third pillarDoneFounder
3Claim what is already truedone 2026-08-06. Whole-day batch logging, contributions, eating out, shared dishes and cuisine breadth all now have sections on the landing pageDoneFounder
4Run G1 and G2 — and add the contribution list to the G1 comprehension test. If testers read it as blame, the copy is wrong and shipping it as-is undoes the band work.Two sessionsFounder
5Ship the deterministic tip library as story 4.5's payload — 20 evidence-backed rules that cost nothing to run, cannot hallucinate, and are auditable under AI Act Art. 50~1 epicBuild

How this documentation is organised

01 — Product
What emealia is
The frame, the six non-negotiables, personas, the core loop, the screen inventory, and the "what we will not build" list.
02 — Features
Feature state, verified
Every surface with its actual status read from the code — contributions and multi-meal in depth, the suggestions gap, and what is deliberately absent.
03 — Market
The field, August 2026
Seven segments, a 22-row feature matrix, the science base, the German payment paradox, and the watchlist.
04 — Tip library
Suggestions without AI
Twenty deterministic, evidence-backed rules; the eight rules every tip must obey; deliberate exclusions; and the contribution → suggestion pipeline.
05 — Marketing
The go-to-market plan
Message hierarchy, the guilt-design comparison rubric, comparison SEO, the clean-creator strategy, launch sequence and channel economics.
06 — Design
Design system
The revised CI, the band system, typography, voice and tone, component patterns, motion — dark only, no light mode.
07 — Business
Business & operations
Pricing, unit economics, KPIs and kill conditions, infrastructure cost, compliance (GDPR, AI Act, MDR/HWG) and the open founder actions.
08 — Roadmap
Roadmap & decisions
Epic-by-epic completion, launch gates, the decision log, what will never be built, and the competitive watchlist.

Source repositories

SourceWhat it holds
emealia-app/Implementation monorepo — backend, frontend, and the 29-epic implementation plan that is the single source of truth for what gets built
emealia-mgmt/Strategy, design, onboarding and market-analysis documents
emealia-web/Public landing page, the interactive prototype, and this documentation set
Prototype9-screen clickdummy