Trace Consumer App Launch Research Report

First substantial draft for James review.

Date: 2026-06-15

Decision Core (read this first)

The one-page version. Everything below is evidence for these eight decisions.

1. Position as "food logging for people managing something real," not an AI calorie tracker. The scan is commoditized (Cal AI and the scanner long-tail anchor around ~$20-42/yr); the condition lens is the entire pricing argument for $79.99. (§4A, §7)
2. GLP-1 is the US wedge — but it's organic-only and never weight-loss-framed. Meta/TikTok block paid GLP-1 ads, and TikTok now suppresses GLP-1 weight-loss content organically too. Lead with the free companion + nutrition. (§6.1)
3. Paid UA cannot lead. Measured COGS → ~90% margin → a derived payer-CAC ceiling of ~$20–25 US ($10–15 in APAC), implying a ~$1 CPI. Organic, creator seeding, ASO, and referral carry the launch. (§5)
4. Attribution is the real pre-spend blocker. Events already ship; source is hardcoded organic and there's no MMP. Ship creator codes + vanity URLs before any seeding. (§5.6)
5. The shipped sample-meal demo is the pre-paywall proof — optimize it (make it condition-relevant), don't replace it with a paywall-first flow. (§11)
6. Highest-EV single experiment: lengthen the trial 3 → 5–9 days (~+12pts trial-to-paid). Worth more than any creative. (§2.3, §5)
7. Asia is a real, differentiated opportunity but a sequence, not a launch. Singapore first proof market → Korea → Taiwan → Vietnam; mainland China is out of scope. Trace's live Asian-food recognition (Gemini 3 Flash Preview, D66) is its strongest non-US asset — validate breadth per market first. (§2A, §22)
8. In APAC the wedge order inverts (T2D / gout / NAFLD / sodium lead; GLP-1 follows) and the economics tighten — confirm prevalence + price tiers before committing budget. (§8, §5.4a)

Top open items before spend: (a) confirm live prod provider + spot-test Asian staples per market; (b) wire attribution; (c) verify per-market price tiers; (d) secure a credentialed RD/MD reviewer (gates SEO + store credibility + claims); (e) run the trial-length test.

Caveats

• This is a first-draft strategic report, not a finished board memo.
• Numbers from app-intelligence vendors, founder interviews, and press releases are directional unless explicitly audited. Where a claim is self-reported or estimated, it is labeled.
• The strongest sources used here are benchmark reports and primary company announcements. Startup case studies are useful for tactics, but they should not be treated as universal laws.
• Trace-specific recommendations respect the product rule that Trace interprets running totals, not individual meals. No recommendation here requires per-meal good/bad verdicts, shame language, or unsafe medical claims.

1. Executive Summary

The consumer app market in 2025/2026 is not rewarding "more apps." It is rewarding sharper wedges, lower-friction first value, better paywall economics, and distribution that is native to existing user behavior. The best launches do not ask users to understand a system. They show one vivid product proof quickly, then let the broader system reveal itself after activation.

For Trace, the most important implication is this:

Do not launch as a generic AI calorie tracker. Launch as food logging for people managing something real, then prove it in the first scan by turning a meal into Updated Running Totals.

Strongest Findings

1. Non-game consumer apps are where the money is moving. Sensor Tower's 2026 market coverage reports that global IAP and paid-app consumer spend hit about $167B in 2025, with non-game apps surpassing games in IAP revenue for the first time. That supports Trace's overall category timing: subscription willingness is real, but competition is intense. Source: Sensor Tower State of Mobile 2026.

2. Subscription funnels are sharply bifurcating. RevenueCat's 2026 report says hard paywall apps monetize far faster than freemium apps, with median Day-60 revenue per install of $3.09 for hard paywall apps versus $0.38 for freemium apps. That does not mean every app should hard-paywall everything; it means the free surface must be deliberately designed rather than allowed to become an accidental parallel product. Source: RevenueCat 2026 subscription benchmarks.

3. Health & Fitness can convert, but only if the funnel is strong. RevenueCat's category benchmarks show Health & Fitness with a median download-to-trial rate around 6.9% and median trial-to-paid around 37.7%, with top-quartile trial-to-paid above 51.4%. The gap between median and top quartile is the difference between paid UA being impossible and paid UA being plausible. Source: RevenueCat State of Subscription Apps.

4. The first session matters brutally. RevenueCat reports that 55.4% of three-day trial cancellations occur on Day 0. If Trace asks for a trial, the user must reach first real value immediately after purchase or trial start. Source: RevenueCat 2026 subscription benchmarks.

5. AI is a hook, not a moat. 2025/2026 AI apps can acquire attention, but generic AI positioning is decaying quickly. The stronger pattern is AI hidden inside a specific workflow: Cal AI for meal photo logging, Tiimo for reducing planning overwhelm, ChatGPT for general utility, Perplexity for answer search. Trace should lead with the user outcome, not "AI-powered nutrition."

6. The best launches have a 5-10 second proof. Cal AI's proof is photo -> calories/macros. Yuka's proof is scan product -> instant score. Runna's proof is goal -> training plan. Trace's proof should be photo -> Updated Running Totals -> "now I know where my day stands."

7. Creator fit beats creator size. Cal AI, Ladder, Simple, and many health apps grow by entering content behaviors that already exist: "what I eat in a day," workout plans, GLP-1 updates, grocery swaps, race training, PCOS meals. Trace should not pay generic lifestyle influencers first. It should recruit creators whose audiences already discuss food decisions through a specific health lens.

8. GLP-1 is one of the strongest current health-app demand waves. Simple publicly tied 2025 ARR momentum to personalized weight loss, AI, and GLP-1 support. Trace already has a free GLP-1 companion; this can be an acquisition wedge, but paid conversion should still attach to the nutrition core. Source: Simple press release via Fitt Insider.

9. Trust is the product in sensitive categories. Tea and Neon show how viral growth can become a liability when privacy, consent, or data security fails. Health data is more sensitive than most consumer app data. Trace should make privacy, no training on user photos, account deletion, and clinical humility visible in the launch story. Sources: TechCrunch on Tea removal, TechCrunch on Neon data exposure.

10. Web-to-app funnels are important, but risky if they overpromise. RevenueCat and growth practitioners keep highlighting quiz/web funnels for subscription apps because they improve education, segmentation, and attribution. For Trace, web-to-app is useful for GLP-1, high BP, PCOS, and cholesterol audiences, but copy must avoid diagnosis, treatment claims, and "one weird trick" framing. Source: RevenueCat on web-to-app funnels.

11. App Store customization is underused leverage. Apple supports up to 70 custom product pages, and Google Play supports custom store listings. Trace should not send GLP-1, PCOS, high-BP, and generic wellness traffic to one generic listing if it can avoid it. Sources: Apple Custom Product Pages, Google Play Custom Store Listings.

12. The CAC ceiling is derivable, not a guess — and it is low. Because COGS is measured ($0.0036/scan, ~$8/paying user/year all-in, ~90% gross margin), the only unknown in the LTV math is renewal. At a 60/40 annual/monthly mix the blended payer LTV is ~$49 (conservative) to ~$70 (mid), so the real target is payer CAC ≤ ~$20–25 (3:1), tolerate ~$35 only with proven renewal, and treat ~$50 as the year-one breakeven wall. Back-solved, that demands a ~$1.20 CPI — which is why paid UA cannot be the primary engine. See §5.

13. The measurement spine already exists; attribution does not. The events for first scan, scan_result_viewed (running totals), Food Ideas, second scan, paywall, and cancellation-by-day all ship today. The blocker is install attribution: source is hardcoded 'organic' and there is no MMP, so no install can be tied to a creator or campaign. Wiring attribution — not adding events — is the pre-spend dependency. See §5.6.

14. The highest-probability launch wedge is likely GLP-1 plus nutrition steadiness. It has current demand, creator density, willingness to pay, and a natural bridge from free companion to paid food logging. The caveat: avoid becoming a weight-loss promise app. The healthier message is protein, fiber, hydration, micronutrient awareness, and day-level clarity.

15. The report's recommended launch thesis:
    "Trace is nutrition intelligence for people managing something real. Snap a meal, see how it changes today's running totals, and make the rest of the day easier to understand."

16. GLP-1 is an organic-only wedge — paid amplification is impossible. Meta and TikTok restrict prescription-drug-adjacent and weight-loss advertising, so GLP-1 creative cannot be boosted (Spark Ads inherit ad review). GLP-1 must run on creator seeding, organic UGC, ASO, and owned web content. Paid spend belongs to the non-GLP-1 wedges (heart-health, cholesterol, PCOS). See §6.1.

17. The pre-paywall proof already ships. Onboarding renders a free sample-meal demo with running-totals output before the paywall. The launch job is to make that demo condition-relevant and measure its drop-off — not to invent a paywall-first flow (which earlier drafts wrongly recommended). And because a real scan costs ~1¢, gating real scanning is a conversion choice, not a cost one. See §5.5 and §11.

18. The wedge and the free tier are the same people. The GLP-1 companion is free forever, so the highest-intent acquisition segment is also the easiest to satisfy without paying. Acquisition (GLP-1, organic) and monetization (food-logging core, more likely heart-health/cholesterol/PCOS) are different segments; the bridge between them must be designed explicitly. See §8.

19. Platform and geography are under-specified; Asia changes the plan. The app ships Android-ready and on iOS, in five locales (EN, zh-CN, zh-TW, KO, VI), yet much of the plan still reads like a US-iOS launch (Apple custom pages, Apple Search Ads, TikTok/Meta paid). Asia is not one market: Singapore is a small, high-trust, high-income health market; Korea is Kakao/Naver/ YouTube/Instagram-first and highly localized; Vietnam is Zalo/TikTok/Android and much more price-sensitive; Taiwan/Thailand are LINE-led; mainland China is a separate regulatory and app-store project. Treat Asia as a launch architecture decision, not a translation task. See §2A.

20. The whitespace is real but narrow, and Trace is a premium tracker. No competitor combines condition-lens + running-totals + no-judgment — Cronometer is "measurement not interpretation," the scanner pack is cheaper, and the coach/clinic pack is much more expensive. At $79.99/yr Trace is in-line with MyFitnessPal Premium, above Cal AI/Lose It/Cronometer, below MFP Premium+, Foodvisor, some Lifesum IAPs, and far below Noom. The condition interpretation is the entire pricing argument, the differentiation is a positioning moat (not technical), and Noom/MyNetDiary/Foodvisor are moving toward the AI nutrition lane. See §4A.

21. The single highest-EV experiment is trial length, not marketing. A 3-day trial converts at ~25.5% (≤4-day cohort); a 5–9 day trial converts at ~37.4% — roughly +12 points and a halving of the effective CPI requirement. That one test moves the economics more than any creative or copy change. See §2.3, §5, §13A.

22. Asian-food recognition is a live, shipped differentiator — Trace's strongest non-US asset. Production runs the model chosen specifically because the prior one failed on Asian foods (Gemini 3 Flash Preview, benched on Korean gimbap/banchan — D66, §2A.0). In exactly the markets Trace already localizes (zh-CN/zh-TW/KO/VI), the calorie-first pack is tuned on Western plates. The caveat: the bench was 6 photos; breadth across SEA/Taiwanese cuisine is unvalidated, so spot-test each market's staple dishes before launching on it.

23. APAC changes the economics and the wedge order, not just the channels. Lower local prices + ~$35 APAC payer LTV drop the CAC ceiling to ~$10–15 (§5.4a), making organic the only path there; and the US GLP-1-first wedge order likely inverts toward T2D / gout / NAFLD / sodium in Asia (§8) — confirm with sourced prevalence data before committing budget. Singapore is the recommended first APAC proof market (§2A).

2. Market Landscape

2.1 The 2025/2026 App Market

The macro market is mature, but not dead. The easiest downloads are gone; the most valuable apps are those that convert attention into paid habit.

Sensor Tower reports global IAP and paid-app consumer spend around $167B in 2025, up about 10.6%, and notes that non-game apps surpassed mobile games in IAP revenue for the first time. That matters because Trace is not trying to win in a novelty market. It is entering a mature subscription market where users already pay for apps that solve recurring, personal problems.

Source: Sensor Tower State of Mobile 2026.

The market implication:

• Users are willing to subscribe when the app solves a persistent problem.
• Distribution costs are high because every category is crowded.
• Generic app-store presence is not enough.
• The winning apps compress first value into a demo-friendly moment.

2.2 Subscription App Trends

RevenueCat's 2026 benchmark work is especially relevant because Trace uses RevenueCat and has a subscription model.

Key subscription patterns:

• Hard paywalls produce faster monetization than freemium in RevenueCat's data.
• Apps are becoming more aggressive about monetizing early.
• Trial cancellation is front-loaded, especially on three-day trials.
• AI apps monetize strongly but can churn quickly when the novelty fades.
• Category winners are pulling away from median performers.

Sources:

• RevenueCat State of Subscription Apps
• RevenueCat 2026 subscription benchmarks

Trace implication:

Trace can justify a narrow free tier if the paid loop is immediately legible. But if users hit a paywall before experiencing any product-specific value, they will compare Trace to every free calorie app and every AI demo they've already seen.

The ideal first-session design is not "browse a dashboard." It is:

1. Choose concern / goal lens.
2. Understand that Trace watches the day, not a single meal.
3. Start trial or use a sanctioned sample/demo flow.
4. Complete first scan.
5. See Updated Running Totals.
6. Receive one calm, relevant next action.

2.3 Health & Fitness Subscription Benchmarks

RevenueCat's category data shows Health & Fitness as a strong subscription category, but the install-to-paid funnel is still thin.

Useful benchmark anchors:

All figures below verified against the source 2026-06-15 unless noted.

This table should shape Trace's expectations. Two corrections to the looser reading:

1. The 37.7% trial-to-paid does not apply to Trace. That is the blended median across trial lengths; the ≤4-day cohort converts at ~25.5%, and Trace ships a 3-day trial. Use ~25–30% as the honest planning input (this also feeds the CAC ceiling in §5). The single highest-EV monetization experiment is testing a 5–9 day trial (~37.4% cohort) — worth more than any copy tweak.
2. AI is a hook with a retention tax. AI-forward apps earn ~41% more per user but churn ~30% faster. Trace's AI scan is the front door, but leading the brand with "AI" inherits the churn penalty — another reason (beyond §4.12) to lead with the user outcome, not the AI.

2.4 Paid UA and Creative Trends

AppsFlyer reports global app install ad spend of ~$65B in 2024 (ex-China), up ~5%, projected to ~$95B in 2025 — with non-gaming as the growth driver (non-gaming up ~8% in 2024 while gaming fell ~7%). (Correction from an earlier draft that mis-stated this as "$78B in 2024"; $78B is a 2025 figure, and the 2024 ex-China number is ~$65B — verified 2026-06-15.) Trace is entering a paid market where mature subscription apps, AI apps, fintech, ecommerce, and games all compete for the same high-quality attention.

Sources: AppsFlyer install ad spend, Business of Apps

Liftoff's 2025 Mobile Ad Creative Index emphasizes UGC as a major differentiator for top apps, reporting that top apps used UGC more heavily than non-top apps. The exact uplift should be treated as report-specific, but the direction matches what is visible across Cal AI, fitness apps, and social apps: polished brand ads are rarely the first growth engine.

Source: Liftoff 2025 Mobile Ad Creative Index

Trace implication:

• Early creative should look native to creator feeds.
• Screen recordings should be obvious and fast.
• Founder-led or expert-led content can work, but the first paid tests should still be judged by cost per trial start and activated payer quality.
• "AI magic" ads should be paired with trust language. Health users need confidence, not just surprise.

2.5 Web-To-App Funnels

Web-to-app funnels are common in health, fitness, fasting, language learning, and mental wellness because they let teams segment the user before the App Store or paywall. RevenueCat's web-to-app writing highlights education, quiz funnels, and attribution as core advantages.

Source: RevenueCat on web-to-app funnels

For Trace, web-to-app can be useful for:

• GLP-1 users: "Are you getting enough protein/fiber through the week?"
• High BP: "Where sodium adds up across a normal day."
• PCOS: "Understand meals through protein, fiber, and glycemic load."
• Cholesterol: "See saturated fat and fiber as running totals."
• Gout: "Track purine-relevant patterns without food fear."

The danger is that quiz funnels can become manipulative. Trace should not manufacture a diagnosis or make the user feel broken. The better pattern is a calm "nutrition lens setup" that ends in a personalized App Store page or onboarding path.

2A. Asia / APAC Market Context

2A.0 Product Readiness — The Asian-Food Advantage Is Live, But Lightly Validated

The entire APAC thesis rests on one product fact: does Trace actually recognize Asian dishes? It does, and it ships. Production runs Gemini 3 Flash Preview — the deployment config sets AI_PROVIDER=gemini and GEMINI_MODEL_OVERRIDE=gemini-3-flash-preview (.do/app.yaml), a model chosen specifically because the prior model failed on Asian foods (D66). The 2026-04 bench cleared Korean gimbap-with-Spam (a prior "salmon" misread) and decomposed Korean banchan reasonably, at ~$0.0036/scan.

Two caveats keep this honest:

• The bench was 6 photos, Korean/Western-skewed. Gimbap and banchan were tested; laksa, cai fan, pho, jjigae, dim sum, bubble tea were not, and "lumping appeared on multi-bowl photos" (a strict-decomposition prompt rule was added to mitigate). Breadth across SEA/Taiwanese cuisine is unvalidated.
• Action before each market launch: spot-test that market's 10–15 staple dishes (the per-country lists below) and close any coverage gaps. The advantage is real; its breadth per cuisine is an open, testable question — not an assumption to launch on blind.

(Note: the committed apps/api/.env defaults to anthropic — that is the local dev default. The DigitalOcean deployment config is the production source of truth, and it runs Gemini. The §5 COGS figures use the Gemini production rate accordingly.)

2A.1 Quality Review: The Current Draft Is Too US-Weighted

The current report is useful on CAC, subscription funnel mechanics, Cal AI, creator seeding, GLP-1 ad restrictions, and Trace's own unit economics. But it still has a major geography flaw: it treats "consumer app launch" as if the default launch environment were North America.

That creates several blind spots:

• Channel bias: the report overweights TikTok, Meta, Apple Search Ads, and Apple custom product pages. In Korea, KakaoTalk, Naver, YouTube, Instagram, and community/search surfaces matter more than a TikTok-first assumption. In Vietnam, Zalo and Facebook/TikTok matter. In Taiwan/Thailand/Japan, LINE is a distribution surface, not just a messaging app.
• Platform bias: the report talks like iOS is the main launch substrate, but the project history points to Android-first testing and Google Play launch work. Asia often makes Android more important for reach, while high-income iOS-heavy pockets still matter for payer quality.
• Pricing bias: US Health & Fitness CAC/LTV benchmarks do not transfer cleanly. RevenueCat's 2025 geography data says Asia-Pacific has meaningful subscription potential, with median first-year payer LTV near $35, but that is below the US/Canada ceiling implied in many paid-UA discussions. Source: RevenueCat State of Subscription Apps 2025.
• Food-data bias: Asian food is harder for photo logging than a US meal-prep plate. Shared dishes, hawker meals, soups, sauces, rice/noodle bases, banchan, kopi/bubble tea, curries, hotpot, and mixed plates make "scan accuracy" a localization problem, not merely an AI problem.
• Trust bias: Singapore, Korea, Taiwan, Vietnam, and China each have different trust anchors. US-style founder direct-response is not enough. Government health programs, clinician/dietitian review, local food databases, local-language store listings, and messaging-app referrals become part of conversion.
• Regulatory bias: zh-CN localization does not mean "launch China." Mainland China requires separate app-store distribution, ICP/app filing, PIPL/data compliance, and digital-health caution. Treat it as a future standalone project, not part of a normal App Store / Google Play rollout.

The report should therefore split "Asia" into market clusters rather than add a generic localization paragraph.

2A.2 APAC Is Large, But The Opportunity Is Uneven

AppsFlyer's 2025 Asia app-marketing report says Asia's app economy grew 150% over six years and that 2024 user-acquisition spend in the region neared $70B. The same report frames the market as moving from volume-led acquisition toward performance-driven growth, with India, Indonesia, and the Philippines seeing accelerating UA investment and more focus on monetization, re-engagement, and fraud protection. Source: AppsFlyer State of App Marketing in Asia 2025.

That sounds bullish, but the practical Trace takeaway is more careful:

• APAC can produce huge install volume.
• Subscription ARPU and payer LTV vary sharply by country.
• Android reach can be high while paid subscription economics are weaker.
• Fraud and attribution quality matter more in some emerging markets.
• Local channels matter more than global channel assumptions.

For Trace, Asia should not be one launch. It should be a sequence:

1. Singapore: best first APAC proof market. English-friendly, high-income, existing SGD pricing, strong public-health/nutrition context, multilingual population, small enough for qualitative learning.
2. South Korea: high-potential paid market because KR pricing and Korean localization already exist, but it needs local channel strategy and Korean food/data confidence.
3. Taiwan / Hong Kong / Chinese-speaking diaspora: good zh-TW/zh-CN leverage without mainland China's distribution complexity. LINE matters in Taiwan.
4. Vietnam: strong localization asset and massive social/messaging reach, but likely lower subscription ARPU. Treat as content/community learning before paid scaling.
5. India: huge English-speaking health market and strong nutrition-app case studies, but intense incumbency from Healthify, Android/fraud pressure, and lower price tolerance. Not a first paid launch unless Indian food coverage is excellent.
6. Mainland China: do not include in the first launch plan. It is a separate regulatory, app-store, hosting, data, and partnership project.

2A.3 Country And Channel Snapshot

Sources: DataReportal Singapore 2025, DataReportal Singapore 2026, DataReportal South Korea 2026, DataReportal Vietnam 2026, DataReportal Taiwan 2026, LY Corporation LINE global data, Kakao/DataReportal Korea 2025.

2A.4 Singapore: Best First APAC Proof Market

Singapore is probably Trace's best first non-US proof market.

Why it fits:

• Internet penetration is extremely high: DataReportal reported 5.61M internet users at the start of 2025, or 95.8% penetration, and 5.16M social media user identities, or 88.2% of the population. Source: DataReportal Singapore 2025.
• TikTok has meaningful adult reach: DataReportal's 2026 report says TikTok's ad tools showed 3.80M users aged 18+ in Singapore in late 2025, reaching 75.4% of adults. Source: DataReportal Singapore 2026.
• Singapore has a strong public-health nutrition context. HPB's Healthy 365 app is familiar to residents, and the LumiHealth program showed that digital health nudges can reach meaningful scale. The Straits Times reported about 885,000 residents, around 25% of Singapore's adult population, use Healthy 365 monthly. MOH later stated LumiHealth engaged more than 377,000 Singaporeans before ending on 31 May 2026. Sources: Straits Times on LumiHealth/Healthy 365, Singapore MOH on LumiHealth.
• Nutrition labeling is an active public-health topic. Singapore's Nutri-Grade requirements are expanding beyond beverages to key sources of sodium and saturated fat, including salt, sauces, seasonings, and instant noodles from mid-2027. Sources: MOH sodium/saturated fat Nutri-Grade announcement, HPB Nutri-Grade page.

Trace implication:

Singapore may not be the biggest market, but it is a strong validation market for exactly the kind of day-level nutrition clarity Trace wants to own:

• sodium in sauces, soups, hawker food, instant noodles;
• saturated fat and sugar in beverages/desserts;
• diabetes/high-BP/cholesterol concern framing;
• English-first launch with zh-CN/zh-TW useful for segments;
• S$79.99 annual pricing already intentionally set about 25% cheaper than US in real terms.

Singapore launch wedge:

"A food log for the nutrients that add up quietly: sodium, sugar, saturated fat, fiber, and protein - through your own health lens."

Singapore channel stack:

1. TikTok/Reels creator demos with hawker meals and home-cooked local dishes.
2. WhatsApp referral sharing, because family and friend groups are the native health-discussion surface.
3. Dietitian/health-coach credibility, especially around diabetes, high BP, and cholesterol.
4. SEO/content around Singapore food examples: "sodium in hawker meals," "how sauces add up," "protein on GLP-1 in Singapore meals."
5. Google Play first if Android is already the build path; iOS custom pages when Apple assets are ready.

Singapore product requirement:

Trace must recognize and explain local meals well enough for trust:

• chicken rice;
• nasi lemak;
• laksa;
• fish soup;
• economic rice / cai fan;
• prata;
• kopi/teh variants;
• bubble tea;
• instant noodles;
• soy/fish/chili sauces;
• mixed rice and shared dishes.

If the first Singapore user scans cai fan and Trace treats it like a generic "rice bowl," the launch loses the trust advantage.

2A.5 South Korea: High Potential, But Needs Korea-Native GTM

South Korea is digitally mature, subscription-capable, and already localized in Trace, but it should not be treated as "translate US TikTok ads into Korean."

Market facts:

• DataReportal's 2026 Korea report says 50.6M people used the internet at the end of 2025, or 97.9% penetration, and 49.3M social media user identities, or 95.4% of the population. Source: DataReportal South Korea 2026.
• KakaoTalk is the daily communication substrate. DataReportal's 2025 Korea report cites Kakao earnings presentations showing almost 48.9M monthly active users in Korea, equivalent to 94.7% of the population. Source: DataReportal South Korea 2025.
• YouTube is very large: Google's ad resources indicated 43.4M YouTube users in Korea in early 2025. TikTok's adult ad reach was much smaller at 7.18M users aged 18+. Source: DataReportal South Korea 2025.
• Wegovy launched in Korea in October 2024, and Korean biotech/health press described strong GLP-1 demand in 2024/2025. Sources: BioWorld on Wegovy Korea launch, Korea Biomedical Review on GLP-1 demand.

Trace implication:

Korea is not a TikTok-first market for Trace. It should be:

• Kakao share/referral support;
• Naver Blog/Cafe and Korean SEO for food/condition content;
• YouTube Shorts and Instagram Reels for demos;
• Korean dietitians, pharmacists, obesity-clinic-adjacent creators, and health educators;
• store metadata and screenshots written natively, not translated.

Korean positioning should avoid both sterile medical language and Western "wellness" vagueness. Stronger:

"Scan a meal and see how today's sodium, protein, fiber, and calories are adding up for your goal."

Food/product requirements:

• rice/noodle base detection;
• soups/stews (jjigae/guk/tang);
• banchan handling without overcounting;
• kimchi/sauce sodium nuance;
• fried chicken, tteokbokki, gimbap, bibimbap;
• coffee and convenience-store meals;
• shared plates.

Pricing note:

KRW 89,000 annual may be plausible for motivated users, but only if Trace's Korean proof is strong. A US-style broad health claim will not justify top-tier pricing against local expectations.

2A.6 Vietnam: Huge Reach, Lower Subscription Certainty

Vietnam matters because Trace already ships Vietnamese, but it should not be treated like a near-term paid subscription mirror of the US.

Market facts:

• DataReportal's 2025 Vietnam report says there were 76.2M adult social media user identities at the beginning of 2025. Source: DataReportal Vietnam 2025.
• DataReportal's 2026 Vietnam report says Zalo had 78.3M monthly active users and TikTok had 76.1M users aged 18+ in late 2025. Source: DataReportal Vietnam 2026.
• AppsFlyer's Vietnam report uses a dataset of 13.6B installs from 2017-2025 and frames Vietnam as moving from scale to value. Source: AppsFlyer State of App Marketing in Vietnam 2025.

Trace implication:

Vietnam is an excellent content/community market and a weak first paid-sub market unless pricing and payment expectations are localized. The right early goal is probably:

• learn food-recognition gaps;
• build Vietnamese content/SEO;
• test Zalo/TikTok creator traffic;
• collect qualitative feedback;
• avoid scaling paid subscription ads until payer CAC and annual-plan acceptance are proven.

Vietnam wedge:

"Understand how rice, noodles, sauces, drinks, and protein add up through the day."

Distribution:

• Zalo share/referral support matters more than a copyable code alone.
• TikTok creator content can work, but attribution will be difficult.
• Facebook groups and YouTube creators may matter for older chronic-condition users.

2A.7 Taiwan, Thailand, And The LINE Cluster

Trace has zh-TW today and no Thai locale yet, so Taiwan is more actionable than Thailand. But the broader lesson is the same: LINE is a distribution surface.

Market facts:

• DataReportal's 2026 Taiwan report says Taiwan had 22.3M internet users at the end of 2025, or 96.7% penetration, and 18.1M social media user identities. Source: DataReportal Taiwan 2026.
• LY Corporation reports LINE had 193M global MAU as of 31 March 2026, including 100M in Japan, 22M in Taiwan, and 54M in Thailand. Source: LY Corporation global LINE data.

Trace implication:

For Taiwan:

• Build Traditional Chinese store metadata and screenshots.
• Add LINE share/referral support.
• Use Taiwanese food examples, not mainland/Singapore Chinese examples.
• Treat diabetes, high BP, cholesterol, and weight-health as likely stronger wedges than GLP-1-first until local demand is verified.

For Thailand later:

• A Thai locale is required before any serious launch.
• LINE and TikTok are likely key channels.
• Food complexity is high: sauces, soups, curries, rice/noodle bases, shared dishes, drinks.

2A.8 India: A Useful Case Study, Not A First Launch

India is important because it has one of the strongest Asian nutrition-app case studies: Healthify.

Healthify claims 40M+ users on Google Play and has built around AI coaching, nutrition tracking, Indian food coverage, and human/AI coaching. Its App Store listing highlights a catalog of 20,000+ Indian foods, and the company announced a $20M round in 2024 (LeapFrog-led) to support US expansion and AI capability. (Earlier draft said "$45M"; the cited source reports $20M — verify if a larger total round figure is meant.) Sources: Healthify Google Play, Healthify App Store, LeapFrog/Healthify funding announcement.

Healthify's lesson is very specific:

In Asia, food database localization is not a nice-to-have. It is the product.

Healthify became credible in India because it knew Indian foods. Trace cannot enter India with a generic US/Western food understanding and expect the condition lens to save it.

AppsFlyer's India 2025 report also warns that India is not just "cheap growth": installs have expanded 816% since 2017, but growth is flattening; UA spend declined 15% with Android cutbacks while iOS budgets increased 17%; fraud risk is explicitly called out. Source: AppsFlyer State of App Marketing in India 2025.

Trace implication:

India is a later market unless Trace deliberately builds:

• Indian food data and portion logic;
• UPI/local payment thinking outside pure IAP, if web-to-app ever expands;
• lower local pricing;
• diabetes/metabolic-health claim controls;
• creator/dietitian credibility.

2A.9 Mainland China: Do Not Accidentally Launch There

Trace's zh-CN locale is useful for Singapore, Chinese-speaking diaspora, and possibly Hong Kong/Taiwan-adjacent audiences, but it should not be interpreted as mainland China readiness.

Reasons:

• Google Play is not the normal Android distribution path in mainland China; distribution involves local Android app stores and/or platform ecosystems.
• China has app filing/ICP requirements and strict personal-information/data rules. Linklaters notes China's app filing regime required apps and mini programs connected to the internet to complete filings, with review by MIIT beginning from April 2024. Source: Linklaters on China app filing.
• Digital health apps face additional legal caution. CMS's China digital-health guide notes restrictions around physicians relying on digital health apps for diagnosis/treatment and AI/automated prescription generation. Source: CMS digital health apps and telemedicine in China.
• Health/sports app privacy compliance is under scrutiny. A 2026 JMIR mHealth paper evaluated privacy-policy compliance among 286 mobile sports and health apps in mainland China against PIPL and related guidance. Source: JMIR mHealth China sports/health app privacy study.

Trace implication:

Mainland China should be explicitly out of scope for the first launch plan. If it becomes a target later, it needs a local legal/regulatory plan, data-hosting decision, Chinese app-store strategy, WeChat/Douyin/Xiaohongshu content plan, and probably local clinical/nutrition partnership.

2A.10 Asia-Relevant Case Studies To Add To The Mental Model

Healthify

Healthify is the most relevant Asia nutrition-app case. It proves that local food data can be a moat: Indian foods, AI logging, coaching, and a freemium/sub business can scale in a large Asian market. The lesson for Trace is not to chase India immediately; it is to treat local food recognition as launch-critical in every Asian market.

Speak

Speak is not health, but it is one of the best Asian subscription-app lessons. It started with a very specific pain in Korea/Japan/Taiwan: English speaking practice. TechCrunch reported in 2023 that Speak had become a top-downloaded education app in Korea with over 100,000 subscribers and had helped around 3M people in Korea learn English. Forbes later reported in 2025 that Speak had 15M downloads globally. Sources: TechCrunch on Speak, Forbes on Speak.

Trace takeaway:

• Pick a painful local job.
• Build localized proof before global positioning.
• AI is acceptable when it clearly replaces a high-friction human alternative.
• Korea/Japan/Taiwan users will pay for a specific personal-improvement outcome if the product feels native.

LumiHealth / Healthy 365

Singapore's LumiHealth and Healthy 365 show that health apps can get mainstream participation in Singapore when they are credible, gamified, and backed by trusted institutions. But they also show Trace should not compete as a generic "be healthier" app. HPB already owns that. Trace should position as the personalized food/nutrition layer that a general public-health app does not provide.

Sources: LumiHealth closure, Healthy 365 HealthHub, GovTech Healthy 365.

DeepSeek

DeepSeek's January 2025 app spike shows that a Chinese/Asian app can break global charts when the value proposition is materially cheaper or better. TechCrunch reported DeepSeek reached No. 1 in the US App Store and 51 other countries. Source: TechCrunch on DeepSeek.

Trace takeaway:

DeepSeek was not a creator-led health launch; it was a capability shock. Trace will not replicate that. But the strategic lesson is real: if the product proof is strong enough, origin geography matters less. For Trace, the proof must be condition-aware interpretation, not just scan extraction.

RedNote / Xiaohongshu

RedNote's 2025 US spike around TikTok uncertainty is useful because it shows the power of community behavior, shopping/review culture, and creator migration. The Verge reported RedNote topped the US App Store amid the TikTok ban moment, and described Xiaohongshu as having 300M+ MAU. Source: The Verge on RedNote.

Trace takeaway:

Xiaohongshu/RedNote is especially relevant for Chinese-language wellness and food content. If Trace later tests Chinese-language creator content, the format should look more like lifestyle proof and review culture than US direct-response ads.

2A.11 Asia-Specific Trace Launch Recommendations

1. Declare the first APAC market. Recommendation: Singapore first, Korea second if Korean food-recognition trust is good enough.
2. Do not call this an Asia launch. Call it "Singapore APAC proof," then "Korea localized test," then "Taiwan/zh-TW test."
3. Add messaging-app referrals before Asia scale. WhatsApp for Singapore, KakaoTalk for Korea, LINE for Taiwan/Thailand/Japan, Zalo for Vietnam.
4. Build local-food demo libraries. Each market needs 20-30 common meals for sample screens, creator scripts, and scan QA.
5. Localize store metadata before paid spend. The app is localized; the store listing must be too.
6. Adjust CAC expectations downward outside US/Canada. APAC subscription LTV can be real, but do not apply US payer-CAC ceilings blindly. Use country cohorts.
7. Use public-health context without pretending to be public health. In Singapore, reference the same nutrient concerns users already see in Nutri-Grade culture - sodium, sugar, saturated fat - but avoid implying HPB endorsement.
8. Lead Asia with high-BP/cholesterol/diabetes-adjacent nutrition clarity more than GLP-1 alone. GLP-1 is strong in Korea and affluent Singapore, but the broader Asian chronic-health wedge may convert more steadily.
9. Mainland China is out of scope. zh-CN helps diaspora/Singapore; China requires separate legal, distribution, data, and partnership planning.
10. Treat food recognition as marketing. In Asia, "it recognizes my actual food" is not a technical detail. It is the trust hook.

3. Case Study Matrix

This matrix is deliberately cross-category. Trace should learn from nutrition apps, but also from AI, social, productivity, and subscription apps that solved distribution, trust, or retention problems.

Sources used across the matrix include TechCrunch on Cal AI, Business Insider on Cal AI, Simple / Fitt Insider, Ladder funding release, RevenueCat Ladder interview, Strava acquiring Runna, Yuka, Apple 2025 App Store Awards, TechCrunch on Clyx, TechCrunch on Tea, TechCrunch on Neon, Business Insider on Cluely, Appfigures on ChatGPT mobile spend, and Rork Wrestle AI case study.

4. Deep-Dive Case Studies

4.1 Cal AI

Cal AI is the most obvious comparator because it sits near Trace's category: food photo logging, AI, consumer subscription, TikTok-native demo. But the lesson is not "be a calorie tracker." The lesson is "make the value visible in seconds and distribute through content behavior that already exists."

Verified / reported facts:

• MyFitnessPal acquired Cal AI in 2026.
• TechCrunch reported Cal AI had 15M+ downloads and $30M+ annual recurring revenue before acquisition.
• Business Insider reported that Cal AI scaled with a tiny team and heavy creator/influencer execution.

Sources:

• TechCrunch: MyFitnessPal acquired Cal AI
• Business Insider: tiny team scaled to millions

Why it worked:

• The product proof is almost absurdly simple: take a food photo and get calories/macros.
• The demo fits TikTok/Reels without explanation.
• It attaches to existing creator formats: meal prep, weight loss journeys, gym routines, "what I eat in a day."
• It gives direct-response advertisers a clear conversion event: install, start trial, scan food.
• It attacks the incumbent pain point of manual logging friction.

What likely does not transfer to Trace:

• Body-transformation language.
• Per-meal judgments.
• Macro/calorie-only positioning.
• Fitness-bro tone.
• Any implication that a photo estimate is clinically precise.

What Trace should adapt:

• Compress the first demo to one product loop.
• Build creator briefs around real meals, not feature recitations.
• Make the CTA specific: "scan your next meal," not "try an AI nutrition app."
• Treat first scan as the acquisition event, not merely onboarding completion.
• Use paid ads to amplify the best organic creator proofs, but judge them by activated trial/payer quality.

Trace translation:

Cal AI's demo is "photo -> calories."

Trace's demo should be:

"photo -> Updated Running Totals -> what matters for my day changed."

The receipt matters because it proves Trace is not just another macro app. It shows the app's core philosophy: the meal is neutral; the day is what matters.

4.2 Simple

Simple is useful because it shows that broad health-app demand is currently clustered around AI, weight management, personalization, and GLP-1 support.

Reported facts:

• Fitt Insider carried a Simple press release claiming $160M ARR in 2025.
• The company positioned its growth around personalized sustainable weight loss, AI, and GLP-1 support.

Source: Simple reaches $160M ARR

Why it worked:

• Weight loss remains a huge paid demand category.
• Fasting and meal timing create repeat use.
• AI coach framing makes personalization feel dynamic.
• GLP-1 support rides a fast-growing user need.

Trace relevance:

Trace already has a free GLP-1 companion, which is strategically valuable. The question is not whether GLP-1 should be in the launch. It should. The question is whether GLP-1 should be the entire brand.

Recommendation:

• Use GLP-1 as a first wedge and lead magnet.
• Monetize nutrition intelligence, not the deterministic dose companion.
• Avoid weight-loss promise copy.
• Position around steadiness: protein, fiber, hydration, micronutrient awareness, and "where my day stands."

4.3 Ladder

Ladder is a better lesson for creator strategy than for nutrition mechanics. It does not just run influencer ads; it productizes coaches and teams. The creator is not a billboard. The creator is part of the user's identity and retention loop.

Sources:

• Ladder funding release
• RevenueCat interview with Ladder

Why it worked:

• Strength training has a clear recurring habit.
• Users affiliate with a coach/team, not just an app.
• Coaches bring trust and distribution.
• Community and programming help retention.

Trace relevance:

Trace probably should not build social teams now. But it can borrow the idea of creator-led "lenses." A dietitian, GLP-1 creator, PCOS creator, or high-BP meal prep creator can introduce Trace as the tool they use to make a day legible.

Potential Trace adaptation:

• "Trace with [Creator Name]: 7 days of protein/fiber steadiness on GLP-1."
• "High BP week: see where sodium adds up without panic."
• "PCOS breakfast week: scan and watch protein/fiber/running totals."

This is not a full creator platform. It is creator-led onboarding and content programming.

4.4 Runna

Runna's lesson is the power of a dated, emotionally real goal. Strava acquired Runna in 2025 to deepen training support in a running market where people were recording huge volumes of activity and setting event goals.

Source: Strava to acquire Runna

Why it worked:

• Running has clear events: 5K, 10K, half marathon, marathon.
• The training plan has a timeline and outcome.
• The app fits an existing identity and community.
• Users come in with urgency.

Trace relevance:

"Eat healthier" is vague. "Your first month on GLP-1," "lower-sodium week," "cholesterol reset," "PCOS breakfast rebuild," and "gout-friendly weekend" are much more launchable.

Trace should package launch experiments around moments:

• First GLP-1 month.
• First week after a high BP reading.
• First grocery reset after cholesterol labs.
• First week trying to increase protein without eating huge meals.
• First week after a gout flare, with careful non-diagnostic language.

4.5 Yuka

Yuka proves that consumer scanning can become a habit when it happens at the point of decision. Its product scanner gives instant clarity in a grocery aisle. The company states it has 80M users globally.

Source: Yuka company site

Why it worked:

• The action is already happening: shopping.
• The scan gives immediate clarity.
• The output is easy to discuss and share.
• The app's independence story supports trust.

Trace relevance:

Trace is also scan-based, but the scan context is different. Yuka is pre-purchase and product-centric. Trace is post-meal or meal-time and day-centric.

What to adapt:

• Make the scan feel consequential immediately.
• Use visual clarity, not dense tables.
• Make independence/privacy part of trust.

What to avoid:

• Red/green moralized scoring.
• Per-meal risk levels.
• Oversimplified health labels.

Trace can learn from the immediacy without copying the judgment model.

4.6 Flo

Flo is relevant because it scales in a sensitive health category where trust, privacy, and lifecycle utility matter. The exact metrics vary by source and period, but public reporting consistently frames Flo as one of the largest women's health apps, with a major valuation and large active user base.

Source: Flo Health company/newsroom

Why it worked:

• It solves a recurring, intimate, high-frequency need.
• It has lifecycle expansion: period, fertility, pregnancy, symptoms, education.
• It has strong habit loops and notifications.
• It invests in trust and credibility because the category demands it.

Trace relevance:

Trace also handles sensitive health-adjacent data: conditions, body stats, meal photos, nutrition, medication context. Privacy and clinical humility should not be buried. They are part of conversion.

Launch implication:

Trace store pages, onboarding, and paywall should visibly state:

• Estimates, not diagnosis.
• Photos/logs are private.
• Not used to train third-party AI.
• Targets can be tuned with a clinician.
• The app interprets running totals, not individual meals.

4.7 BetterMe / Noom / Web-To-App Health Funnels

BetterMe and Noom represent a mature performance-marketing pattern: web quiz, personalized plan, app install, subscription. This pattern is common because it lets a company educate users before app install, create perceived personalization, and segment landing pages by audience.

Source: RevenueCat web-to-app funnel overview

Why it works:

• It converts cold traffic with more context than an app-store page can hold.
• It gives the user a personalized reason to install.
• It enables audience-specific messaging.
• It can improve ad attribution and email/SMS capture.

Trace adaptation:

Build lightweight web-to-app flows, but make them calm:

• "Set up your nutrition lens."
• "What are you managing right now?"
• "Which nutrients should Trace watch more closely?"
• "See the app page built for your lens."

Avoid:

• Fake diagnosis.
• Countdown pressure.
• "You are at risk" scare copy.
• Impossible outcome claims.

4.8 Tiimo

Tiimo won Apple's 2025 iPhone App of the Year. It is not a health app, but it is very relevant because it shows how an app can win by being specific, humane, and accessible rather than loud.

Sources:

• Apple 2025 App Store Awards
• Tiimo App Store listing

Why it worked:

• It serves neurodivergent users with visual planning.
• AI reduces friction rather than becoming the entire pitch.
• The design signal is caring and specific.
• Apple/editorial teams like inclusive, polished, purposeful apps.

Trace relevance:

Trace's restraint can be a competitive advantage. It should not sound like a bro-science calorie app. It should feel like a smart, calm tool for adults who are tired of generic advice.

4.9 Partiful and Clyx

Partiful and Clyx are social/event apps, but their launch lessons are useful. Partiful made a mundane workflow feel culturally fluent. Clyx raised funding on the idea that people want more IRL social connection, using local density rather than universal cold-start.

Sources:

• Business Insider on Apple Invites and Partiful
• TechCrunch on Clyx

Why they matter:

• Brand tone can be a growth mechanic.
• Utility spreads when it is embedded in social behavior.
• Dense communities beat generic distribution.

Trace relevance:

Trace is not social, but it can launch into dense communities:

• GLP-1 creators and groups.
• PCOS nutrition communities.
• High-BP/heart-health meal-prep communities.
• Gout support communities.
• Dietitian audiences.

Do not launch to "people who eat food." Launch to communities where the pain is already named.

4.10 Tea and Neon

Tea and Neon are warning signs. Both achieved attention in 2025 by touching sensitive data and social incentives. Both became trust stories when privacy or policy issues surfaced.

Sources:

• TechCrunch on Tea removal
• TechCrunch on Neon exposure

Trace relevance:

Trace should treat trust work as launch work:

• Data safety form accurate.
• Privacy policy understandable.
• Health app declaration clean.
• Account deletion obvious.
• AI/photo handling explained.
• No manipulative user incentives around sensitive data.

The worst Trace failure mode is not low virality. It is a viral trust issue.

4.11 Cluely

Cluely used controversy and founder-led content as distribution. It is a useful example of attention engineering, but a poor model for health.

Source: Business Insider on Cluely

What transfers:

• Founder-led content can create attention faster than brand accounts.
• A sharp point of view beats a bland feature list.
• Narrative matters.

What does not transfer:

• Ragebait.
• "Cheating" framing.
• Anything that makes users ashamed or defensive.

Trace founder-led content should be calm but opinionated:

• "Most food trackers judge meals. Trace looks at the day."
• "A single meal is not a diagnosis."
• "People managing real conditions need better than generic calorie math."

4.12 ChatGPT and Perplexity

ChatGPT mobile and Perplexity show two versions of AI utility:

• ChatGPT brought an existing mass habit into mobile and monetized broad utility.
• Perplexity narrowed AI into answer search.

Sources:

• Appfigures on ChatGPT mobile spend
• Perplexity official site

Trace relevance:

Trace cannot win by saying "we use AI." Users already have AI. Trace wins by being the nutrition workflow that general AI does not want to responsibly own: photo meal logging, deterministic nutrient extraction, running daily totals, concern-specific nutrient lenses, and safe interpretation.

4A. Direct Competitive Landscape (2025/2026)

Sections 3–4 are cross-category lessons. This is the head-to-head field — the apps a Trace user would actually compare against — and it changes two things: it exposes Trace's price position and it locates the one piece of genuine whitespace. All scale figures verified 2026-06-15; self-reported vs measured is labeled. (Full teardown + URLs in the notes file.)

4A.1 Price-and-philosophy map

Read this table once and the price problem is more specific: Trace is expensive versus scanner apps and low/mid classic trackers, roughly in-line with MFP Premium, below MFP Premium+, Foodvisor, some Lifesum IAPs, and far below Noom/coach/clinic programs. The scan does not justify $79.99; Cal AI and the scanner long-tail anchor photo logging closer to $20-42/year. Only the condition-lens interpretation justifies $79.99, which makes the interpretation the entire pricing argument, not a feature.

4A.2 Cronometer — the one philosophical neighbor (measurement, not interpretation)

Cronometer is the only competitor that shares Trace's "not calorie-first" stance: it tracks up to 84 nutrients and lets a user hand-set custom targets (a CKD user can set potassium/phosphorus ceilings; a diabetic can set a glucose range). But there is no automated condition lens — the user must already know their clinical targets, set them manually, and read the raw numbers themselves. Cronometer is a measurement instrument; Trace is an interpretation instrument. That is the cleanest one-line statement of Trace's differentiation. Where Cronometer wins: nutrient breadth, data credibility, a real clinical/B2B channel, and a ~15M-user base (self-reported). Trace's edge is the deterministic "here's what your running totals mean for your condition today, in plain language" layer Cronometer expects you to perform yourself.

4A.3 The calorie-first pack — wrong philosophy, right virality

MFP, Cal AI, Lose It!, Lifesum, and MacroFactor are all weight/calorie/macro-first with no medical-condition interpretation. They matter for two reasons: (1) they prove photo-scan is a commoditized front door (MFP Meal Scan + Cal AI, Lose It! "Snap It") — building the launch story on "we scan meals" walks into their strength; and (2) Cal AI is the go-to-market lesson, not the product lesson — TikTok creator-led scan demos + sequenced paid scaled it to ~15M downloads / ~$35M ARR (measured-ish; see notes). Trace borrows the motion, not the calorie-first model.

The one place Trace's scan is not commoditized: Asian food. The pack is built and tuned on Western plates. Trace deliberately runs the model chosen for Asian-dish accuracy (Gemini 3 Flash Preview, benched on Korean gimbap/banchan — D66, §2A.0), which is a genuine product edge in exactly the markets Trace is localized for (zh-CN/zh-TW/KO/VI). Caveat: this is a claimed edge until tested head-to-head — the high-value, cheap experiment is to scan the same tray of laksa / cai fan / banchan / pho through Trace vs Cal AI vs MFP and publish the comparison (which doubles as §13A.7 creative). Don't assert the edge in store copy until that comparison exists.

4A.4 The GLP-1 field — the wedge's actual competitors

• Shotsy is the direct precedent for "free GLP-1 wedge → paid upgrade" (~100K downloads measured; its own "1M+" claim is self-reported and unreliable). Critically, Shotsy paywalls the medication-level curves — the exact feature Trace gives away free — and upsells deeper dose tracking, not nutrition. Trace's bridge target (free companion → paid nutrition) is therefore differentiated, not a copy.
• Noom is the one to watch. Its GLP-1 Companion already ships protein-focused meal logging + "Muscle Defense™" — the closest thing to Trace's muscle-preservation/protein angle — but it is weight-loss-outcome framed, coaching-heavy, and bundled with its own drug business.
• Caloria (endocrinologist-built, "metabolic steadiness" for GLP-1/PCOS/ perimenopause) is the closest philosophical match but tiny (~20K downloads, self-reported).
• Telehealth-bundled players (Embla ~€150/mo+Rx, Voy £94–239/mo incl. Rx, Found $349–699/mo) are a different business — the app is a retention wrapper around a prescription, nutrition is human coaching. Not chasing a free nutrition wedge.

Is "nutrition steadiness on GLP-1" owned? No — it is contested but open. No one combines (1) GLP-1-native positioning, (2) non-weight-loss-promise framing, (3) deterministic protein/fiber/hydration/micronutrient interpretation (not just logging), and (4) side-effect-aware eating in one approachable product. That is Trace's lane. Noom is moving toward it and is the credible threat.

4A.5 Whitespace verdict — real, but narrow, and not a moat

The unoccupied position — condition-lens + running-totals + no-judgment — is genuine: it sits in the gap between Cronometer (right philosophy, no interpretation) and the calorie-first pack (right virality, wrong philosophy). But be skeptical about how much it protects:

1. It is a positioning moat, not a technical one. The condition logic is a content/clinical asset, not defensible IP. MFP (220M users + Cal AI's engine) or Cronometer (credibility + clinical channel) could bolt on condition presets if the segment proves valuable. Trace's lead is time and focus, not lock-in.
2. It is a niche of a niche. The user who knows they have gout/PCOS/CKD, wants nutrition help, and will pay $80/yr is a fraction of the calorie-counter TAM. This is a focused, higher-ARPU wedge — not a Cal-AI-scale land grab.
3. Distribution is the hard problem, not product. Cal AI's value was legible in 3 seconds; Trace's (interpretation, not a number) is harder to dramatize in a 15-second video. The product whitespace is real; whether Trace can demo the interpretation in creator-native format is the open question (see §13A.7).

4A.6 Market sizing — anchor on the medication base, reject vendor numbers

No credible GLP-1-app market-size or user-count figure exists. Size the opportunity off the medication base instead: ~6% of US adults used GLP-1s in 2024; ~25–30M US adults have tried them (KFF-derived). Treat any "$Xbn weight-loss app market / 280M users" figure as unverifiable vendor-report data, and ignore "GLP-1 companion nutrition market" reports — they measure protein powders and shakes, not software.

4A.7 Pricing research update — what the 2026 competitor sweep changes

The current pricing sweep changes the conclusion from "Trace is top of the range" to a more useful diagnosis:

1. Commodity scanner anchor: Cal AI and the scan-only long-tail create a low mental anchor: roughly $20-42/year for photo -> calorie logging. If Trace's paywall reads like an AI scanner paywall, $79.99 feels 2-4x too high.
2. Classic tracker band: Lose It!, Carb Manager, YAZIO, Cronometer, MyNetDiary, and MacroFactor mostly sit around $40-72/year. Trace is above most of this band, but not wildly outside it.
3. Premium tracker / AI nutrition band: MyFitnessPal Premium ($79.99), MFP Premium+ (about $99.99), Foodvisor (about $83.99), Lifesum's higher IAPs (about $99-119.99), and MyNetDiary Premium Plus ($14.99/mo) make Trace's $79.99 defensible if the product feels closer to "condition-aware nutrition intelligence" than to "cheap scanner."
4. Coach / clinic / GLP-1 band: Noom Weight (about $209/year or $70 monthly) and Noom/GLP-1 programs at $99-129+/mo are much higher, but they include coaching, behavior programs, or medication adjacency. Do not claim Trace is "cheap versus Noom" unless the copy makes clear that Trace is self-serve nutrition interpretation, not a care program.

The pricing tactic issue is annual math. Trace's current $9.99 monthly and $79.99 annual means annual is 8.0 months of monthly, a 33% discount:

This is the one pricing lever worth testing after the core paywall copy is right. Three viable experiments:

• Keep $79.99 annual, raise monthly to $14.99. Annual becomes a stronger 56% discount while staying below MFP's $19.99 monthly and near Foodvisor. Risk: more monthly sticker shock and fewer low-commitment subscribers.
• Keep $9.99 monthly, test $69.99 annual. This makes annual 42% off and moves Trace closer to Cronometer/MacroFactor. Risk: lower CAC ceiling and a weaker premium signal.
• Keep both prices, but improve annual justification. Put the condition-lens value before price: "running totals for the nutrients your profile is watching" beats "unlimited scans." This is the lowest-risk first test because it does not change revenue architecture.

Asia changes the answer again. Singapore's S$79.99 annual is roughly a US$59 price point, and Korea's KRW 89,000 is roughly US$65; those are already closer to Cronometer/MacroFactor than to the US $79.99 anchor. But RevenueCat's 2026 geography data shows India/SEA Google Play yearly medians around $14.64 and IN/SEA first-year payer LTV as the lowest major region. That means:

• Singapore can plausibly be a premium APAC proof market; do not generalize that to Vietnam or India.
• Korea can support paid pricing if Korean food trust and Korean-native copy are excellent, but it should not be a translated-US paywall.
• Vietnam/India should be treated as content, food-data, referral, or lower-tier experiments until annual-plan acceptance is proven.
• APAC CAC ceilings remain ~$10-15 payer CAC for a healthy 3:1 ratio even when local pricing looks affordable, because payer LTV is lower.

Bottom line: keep the strategic price frame as premium tracker pricing, not scanner pricing and not coach pricing. Trace is selling a condition-specific interpretation layer on top of logging. Every paywall, creator script, and store screenshot needs to make that value visible before the user compares the price to Cal AI.

5. CAC and Funnel Economics

5.1 The Core Formula

For paid acquisition:

payer CAC = CPI / (install-to-trial rate * trial-to-paid rate)

For example:

$3.00 CPI / (15% install-to-trial * 40% trial-to-paid)
= $3.00 / 0.06
= $50 payer CAC

This is why paid UA can feel either impossible or exciting. Small changes in activation and trial quality create huge CAC differences.

5.2 Unit Economics We Can Pin Down (the cost side is not a guess)

Most launch CAC analysis is hand-waving because the analyst cannot price the product they are buying users for. Trace is the opposite case: the cost of serving a user is measured, not estimated, so the CAC ceiling can be derived rather than asserted.

Price (current, shipped):

• Monthly: $9.99/month
• Annual: $79.99/year, annual pre-selected, 3-day trial once per user

Store cut — use 15%, not 30%, as the planning base. A pre-$1M developer qualifies for Apple's Small Business Program (15%) and Google Play's 15% rate on the first $1M/year. Trace will be under that threshold at launch, so 15% is the realistic blended take rate. Model 30% only as the "graduated past $1M / not enrolled" sensitivity.

Cost of goods sold — measured from production, not modeled. Per api_call_logs (109 real scans, Apr–Jun 2026) at the production provider (Gemini 3 Flash, $0.50/1M in, $3.00/1M out): a meal scan costs $0.0036. Per Pro user per year:

Add non-AI infra (Neon, Upstash, R2 photo storage at 30-day retention, push, email, error/analytics SaaS) at an estimated ~$1–3/active user/year. All-in COGS is ~$5–11/paying user/year — call it $8 median. Against ~$68 annual net revenue, that is a ~88–90% gross margin. (AI COGS is measured; the non-AI allocation is a labeled estimate pending a real infra-cost-per-MAU pull.)

The consequence: in the LTV math below, COGS moves the answer by single dollars. The only variable that materially moves the CAC ceiling is retention. We can compute everything except churn — so the launch job is to measure churn early, not to refine cost assumptions.

5.3 LTV Scenarios (the one real unknown is renewal)

Year-one contribution per paying user, net of store cut and $8 COGS:

Extending past year one with renewal scenarios (annual) and average-lifetime scenarios (monthly):

Blended payer LTV at an assumed 60% annual / 40% monthly mix (annual is pre-selected and trial-gated, so it should dominate):

Every number here is firm except the renewal/lifetime column. That is the spread to close with data, and nothing else.

5.4 The Derived CAC Ceiling

CAC ceiling = blended payer LTV ÷ target LTV:CAC ratio. (CAC here is per paying user, matching the §5.1 formula's output — not per install.)

So the defensible guidance is target payer CAC ≤ ~$20–25, tolerate up to ~$35 only with proven annual mix and renewal, and treat ~$50 as an absolute ceiling — not the "$50–80 risky / $80+ too high" the looser version implied. At conservative renewal, a $50 payer CAC is already a losing ~1:1 ratio.

Back-solving to CPI shows why paid UA mostly cannot carry the launch. At an optimistic 13% install→trial × 40% trial→paid, payer CAC ≈ CPI × 19, so a $23 target needs a ~$1.20 CPI. But §2.3 shows a 3-day trial converts at ~25.5%, not 40% — so the realistic multiplier is CPI ÷ (0.13 × 0.26) ≈ CPI × 30, and a $23 payer-CAC target then demands a ~$0.78 CPI, which is unattainable on paid social health traffic ($2.50–$5.00 typical N. America CPI). The unit economics independently confirm the channel conclusion in §6: organic, UGC, creator-seeding, and ASO must carry the launch; paid is amplification of proven creative, not a primary engine. (And the cheapest way to relax this constraint is the §2.3 trial-length experiment — a 5–9 day trial roughly halves the effective CPI requirement.)

Reference scenario table (payer CAC = CPI / (install→trial × trial→paid)):

The "do not scale" rule, now anchored:

• Do not scale any paid channel until renewal/lifetime is observed — it is the only input the ceiling depends on. D7 retention, first-week scan count, Day-0 cancellation timing, and annual/monthly mix are the leading indicators.
• Judge creators by retained payer CAC, never install volume — which requires attribution that does not yet exist (§5.6).

5.4a APAC Variant — the Ceiling Is ~30–40% Lower

Everything above assumes US pricing and US benchmarks. In the Asian markets §2A sequences, the ceiling is materially tighter on both sides of the ratio:

• Lower price realization. Local tiers run below the US $79.99 — Singapore ~S$79.99 (≈US$59), Korea ~KRW 89,000 (≈US$65), Vietnam lower still. (These tiers are asserted in §2A and should be confirmed against the actual configured App Store / RevenueCat price points — see §2A pricing note.)
• Lower payer LTV. RevenueCat's 2026 geography data puts global first-year payer LTV around the low-$20s, with IN/SEA among the weakest regions (especially Google Play). Its price medians also show IN/SEA Google Play yearly pricing around $14.64, not a Western $40-80/year baseline.

For premium Singapore/Korea cohorts, combine the two and APAC blended payer LTV lands roughly $30–45; broader IN/SEA Android cohorts can be lower. The 3:1 CAC ceiling therefore falls to ~$10–15 (vs ~$16–23 US). The practical consequences:

• Paid UA is even more impossible in APAC than the US — organic, creator seeding, ASO, and messaging-app referral (Kakao/LINE/Zalo) are not a preference there, they are the only viable acquisition path.
• Vietnam specifically (§2A.6) likely will not support a US-style annual subscription at acceptable CAC early; treat it as a content/community and food-data-learning market, not a paid-sub scale market, until annual-plan acceptance is proven.
• COGS does not move (~$0.0036/scan globally), so APAC gross margin holds at ~90% — the constraint is price realization and churn, never cost.

5.5 Cost Is Not A Reason To Gate The Proof

A direct corollary of $0.0036/scan: letting a cold user run 2–3 real scans before the paywall costs about one cent. The current hard-paywall-before-real- scanning stance is therefore a conversion decision, not a cost decision, and should be tested as one. Trace already ships the cheaper version of this — the free sample-meal demo (§11) — but the COGS data means a "few free real scans then paywall" variant is economically free to A/B. The only question is which converts better, not which is affordable.

5.6 The Measurement Spine Exists — Attribution Is the Gap

The event catalog is already built, not a launch to-do. The mobile app emits first_scan_completed, scan_result_viewed, close_gaps_viewed, second_scan_completed, paywall_viewed, condition_selected, and cancellation_* (carrying days_since_trial_start) — see apps/mobile/src/utils/analytics.ts. The composite activation metric below is computable today:

activated trial rate =
trial starters who complete a scan + view scan_result (running totals)
within 30 minutes

What is missing is the one thing every CAC-by-creator claim in §5.4 and §6 depends on: install attribution. The source property on funnel events is hardcoded to 'organic' (IntroCarouselScreen.tsx — "paid + referral sources will hook in when attribution lands"), and there is no MMP (Branch/Adjust/ AppsFlyer) in the app. Until that lands, no install can be tied to a creator, campaign, or App Store custom-page ID.

This is the true pre-spend blocker, and it bites hardest exactly where the only viable GLP-1 channel lives (organic UGC — the least attributable traffic). The launch dependency is therefore not "instrument events" but:

• Ship an MMP or, at minimum, creator codes + per-wedge vanity URLs + App Store custom-page-ID capture, so source stops being a constant.
• Wire campaign / creator / custom-page-ID through to the existing events.
• Only then is the §6 "judge creators by payer CAC" plan executable.

6. Launch Channel Analysis

6.1 Hard Constraint: GLP-1 Cannot Be Paid-Advertised

This reshapes the entire channel plan and was understated in the looser version. GLP-1 medications (Ozempic, Wegovy, Mounjaro, Zepbound) sit inside the most restricted ad categories on the major paid platforms:

• Meta requires prior written permission + geo-restriction to run prescription-weight-loss ads (Health & Wellness ad standard) and restricts before/after / negative-body-image weight-loss creative. A 35-state-AG coalition (Dec 2025) is pressing Meta to tighten further — the direction of travel is more restrictive, not less.
• TikTok prohibits weight-management and prescription-drug ads, and bans products using "GLP" in branding/title; Spark Ads inherit ad review, so a strong organic GLP-1 video becomes ineligible the moment it is boosted.
• New and load-bearing: TikTok's May 2026 guidelines suppress weight-loss- medication and weight-loss content organically, not just in paid. This is the single biggest recent risk to a GLP-1 launch — it means even un-boosted creator videos framed around GLP-1 weight loss can be down-ranked. (Sources: Meta Health & Wellness ad standard; STAT, Dec 2025; Rolling Stone on TikTok's May 2026 guidelines — see notes file.)

The practical rule (now stricter — doubly constrained):

GLP-1 is organic-only AND must never be framed as weight loss. Distribute through creator seeding, non-paid UGC, ASO, owned web content, and partnerships — never paid amplification — and frame every asset around nutrition, protein, hydration, side-effect-aware eating, and the free companion, never weight loss, never the medication by name. Paid is out (ad review); weight-loss-framed organic is also now down-ranked.

One pragmatic exception worth a small, controlled test: Trace does not advertise a drug — it is a free nutrition companion. A nutrition-steadiness ad that never names a medication and never makes a weight-loss promise may clear Meta/TikTok review where a "GLP-1 weight loss" ad would not. Run a tiny policy-probe campaign before writing paid off the non-GLP-1 wedges entirely; do not bet the launch on it.

Two consequences that thread through the rest of the plan:

1. Paid amplification belongs to the non-GLP-1 wedges. Heart-health/sodium, cholesterol/fiber, and (carefully) PCOS can run paid creative if framed as nutrition awareness, not weight loss or treatment. GLP-1 paid is off the table; do not budget for it.
2. Attribution matters most precisely where it is weakest. Organic UGC has no click and no UTM, so the only way to measure GLP-1 creator performance is creator codes and per-creator vanity URLs (§5.6). Without them the #1 wedge is un-measurable — ship code-based attribution before seeding.

Priority order (reordered for the organic-first reality):

1. Creator seeding (organic, code-tracked) in GLP-1 and condition communities.
2. ASO and custom store listings/pages (always-on, not ad-reviewed).
3. Web-to-app landing pages for top wedges (owned, fully attributable).
4. Apple Search Ads / non-GLP-1 paid amplification of proven organic creative.
5. Partnerships and affiliate only after conversion/retention proof.
6. APAC market-specific share rails before scaling outside English-speaking audiences: WhatsApp in Singapore, KakaoTalk in Korea, LINE in Taiwan/Thailand, Zalo in Vietnam.

6.2 The Channel Table Is US-Shaped — APAC Maps Differently

The table at the top of §6 is built on TikTok / Meta / Apple Search Ads / Apple custom pages — a US/Western stack. In the markets §2A sequences, the dominant surfaces and the priority order both change:

Three cross-cutting consequences:

• Messaging-app referral replaces the copyable code. Kakao / LINE / Zalo / WhatsApp are the native health-discussion surfaces; a §13A.5 referral that only copies a code underperforms a native share into the dominant messenger.
• Google Play custom store listings outrank Apple custom product pages in Android-heavy APAC — invert the §10 / §13A.2 emphasis per market.
• The §6.1 GLP-1 rule still holds globally, but in Korea the GLP-1 organic channel is YouTube / Naver / Kakao, not TikTok — and Korea's GLP-1 demand is real (Wegovy launched Oct 2024, §2A.5), so the wedge is viable there, just routed through different surfaces.

7. Positioning Analysis For Trace

Option A: "AI Calorie Tracker"

Pros:

• High demand.
• Easy to understand.
• Cal AI proved the demo can convert.
• Paid creative is straightforward.

Cons:

• Crowded and commoditized.
• Direct comparison to Cal AI, MyFitnessPal, Lose It, Cronometer.
• Pulls Trace toward calorie/macro/body-transformation language.
• Undersells concern-specific running totals.

Verdict:

Use "AI meal scan" as a feature, not the launch position.

Option B: "Nutrition Clarity For Chronic Health Concerns"

Pros:

• Strong differentiation.
• Speaks to high-intent users.
• Matches Trace's product philosophy.
• Less likely to attract pure calorie-app comparison.

Cons:

• Medical claims risk.
• Harder to explain in a 5-second ad.
• Some users may find "chronic" heavy.

Verdict:

Strategically strong, but needs careful language. Better user-facing phrase: "food logging for people managing something real."

Option C: "GLP-1 Nutrition Companion"

Pros:

• Strong current demand.
• Trace already has free GLP-1 companion.
• Creator ecosystem is dense.
• Paid nutrition need is real: protein, appetite, hydration, fiber, muscle preservation concerns.

Cons:

• Could narrow brand too much.
• GLP-1 platform policies and medical claims require care.
• Weight-loss framing can pull the product away from its broader mission.

Verdict:

Best first acquisition wedge. Do not make it the only brand identity.

Option D: "Photo Meal Logging With Running Daily Totals"

Pros:

• Product-true.
• Clearer than chronic-health language.
• Differentiates from per-meal judgment.

Cons:

• "Running totals" may sound too rational, not emotional.
• Users may not know why they need it until they see it.

Verdict:

Use in product demos and store screenshots. Pair with a sharper audience hook.

Option E: "Personalized Nutrition Without Diet Culture"

Pros:

• Trust-building.
• Good for wellness and GLP-1 users who dislike shame.
• Clear contrast with calorie apps.

Cons:

• Can be too soft for paid ads.
• "Without diet culture" is a philosophy, not a product proof.

Verdict:

Use as supporting trust copy, not the primary acquisition hook.

Recommended Positioning

Primary:

Food logging for people managing something real.

Expanded:

Snap a meal. See how it changes today's running totals for the nutrients your body is actually watching.

Audience-specific variants:

• GLP-1: "Stay oriented on protein, fiber, hydration, and nutrients through the day."
• High BP: "See where sodium fits into today's total."
• Cholesterol: "Track saturated fat and fiber as the day unfolds."
• PCOS: "Understand protein, fiber, and glycemic load without meal judgment."
• Gout: "Track the day through your nutrition lens without fear labels."

8. Audience / Wedge Analysis

The Wedge Order Inverts in APAC (verify prevalence before committing)

The priority table above is US-shaped, and GLP-1's #1 rank is a US artifact: GLP-1 penetration is far higher and the creator ecosystem far denser in the US than in most of Asia (Korea, where Wegovy launched Oct 2024, is the main APAC exception). For an APAC launch the order likely flips toward the metabolic conditions, for two reasons:

• Different disease burden. Type 2 diabetes, gout/hyperuricemia, NAFLD/fatty liver, and hypertension are widely reported as more prevalent in East/Southeast Asian populations than in the West (gout notably high in Taiwan; T2D high across China/Korea; NAFLD rising sharply region-wide). §2A.7 already concludes that Taiwan should treat diabetes/BP/cholesterol as stronger wedges than GLP-1-first.
• Public-health tailwind. Singapore's Nutri-Grade sodium/saturated-fat push (§2A.4) makes sodium/BP/cholesterol the culturally salient wedge there.

Working APAC wedge order (directional): Singapore → sodium/BP, cholesterol, T2D; Korea → GLP-1 (viable) + T2D; Taiwan → gout, T2D, BP; Vietnam → general metabolic/T2D.

Honest gap: the specific Asian condition-prevalence figures behind this were the one research stream that did not complete this pass. Treat the APAC wedge order as a hypothesis to confirm with sourced prevalence data (per market) before allocating creator/launch budget — do not lock it in on directional reasoning alone.

Recommended First Wedge: GLP-1

Why:

• Current market momentum is strong.
• Users have new routines and uncertainty.
• Food volume, protein, hydration, fiber, and side-effect concerns are daily.
• Trace's free GLP-1 companion creates a trust-building entry point.
• Paid food logging has a clear upgrade path.

Positioning:

A calmer way to keep nutrition steady on GLP-1.

Avoid:

• "Lose more weight."
• "Prevent muscle loss" as an absolute claim.
• Medication-specific medical advice.
• Dose recommendations.

The GLP-1 Wedge Paradox (resolve before committing the budget)

There is a structural tension the wedge analysis must confront: the GLP-1 companion is fully free forever (D93), so the wedge audience and the free tier are the same people. A GLP-1 user can get dose logging, reminders, and level curves indefinitely without ever touching the Pro-gated nutrition core. That makes the highest-intent acquisition segment also the easiest to satisfy for free — the classic free-tier-sprawl risk (§12), applied to Trace's actual product rather than in the abstract.

This does not kill the wedge, but it changes the job:

• Acquisition and monetization are different segments. GLP-1 is the cheapest, densest top-of-funnel (free companion + organic creators), but the paying customer is more likely the heart-health/sodium, cholesterol, or PCOS user whose value is in the gated food-logging core.
• The conversion bridge must be explicit. What, specifically, pulls a free GLP-1 companion user into a paid nutrition trial — a protein/fiber gap they can only close with scanning? A weekly running-totals view the companion teases but the paywall owns? That bridge needs to be designed and named, not assumed.
• Measure free-GLP-1 → paid-nutrition conversion as its own funnel. If it is weak, treat GLP-1 strictly as a brand/awareness and trust play, and put the monetization spearhead on the second wedge below.

Second Wedge: High BP / Cholesterol

Why:

• Large market.
• Food connection is obvious.
• Sodium, saturated fat, fiber, potassium, and calories make running totals useful.
• Lower claims risk than diabetes if framed as tracking and awareness.

Positioning:

See where the day stands for the nutrients your heart-health plan is watching.

Third Wedge: PCOS

Why:

• Strong creator ecosystem.
• Users are already seeking nutrition help.
• Protein, fiber, glycemic load, and micronutrients are more relevant than generic calories.

Positioning:

A food log that understands the nutrients PCOS creators keep talking about, without judging individual meals.

Need caution:

• Avoid promising symptom improvement.
• Avoid hormone-cure language.

Fourth Wedge: Gout

Why:

• Pain intensity is high.
• Generic calorie apps are especially irrelevant.
• The market is under-served.

Need caution:

• Purine data complexity.
• Flare claims risk.
• Avoid per-food fear labels.

Positioning:

Track your day through a gout-aware nutrition lens, without turning every meal into a verdict.

9. Creative Strategy

What Is Working In 2025/2026

The strongest creative formats across app categories:

• UGC demos that show the product in the first two seconds.
• Screen recordings with a human voiceover.
• Day-in-the-life content where the app enters an existing routine.
• Creator-led trust, especially in health and fitness.
• Founder-led opinion content when the category needs a new worldview.
• Before/after narratives, but only when compliant and not misleading.
• Challenge formats: 7 days, first week, reset week.
• AI magic demos when the output is concrete.

Trace should bias toward:

• Real meal visuals.
• Fast scan flow.
• Updated Running Totals receipt.
• Calm concern-specific copy.
• No meal shaming.
• No "this food is bad" overlays.

30 Trace Creative Concepts

Creative rules:

• Never say "safe food" or "bad food."
• Never claim symptom improvement.
• Never imply Trace diagnoses or treats a condition.
• Never show a per-meal red/green verdict.
• Prefer "see," "track," "understand," "where the day stands."

10. App Store Strategy

App Name / Subtitle

Options:

• Trace: Nutrition Intelligence
• Trace: AI Nutrition Tracker
• Trace: Food & Health Tracker
• Trace: Meal Scan Nutrition

Recommendation:

Use "Trace: Nutrition Intelligence" where character limits allow. Use "AI meal scan" in subtitle/keywords, not as the whole brand.

Default Screenshot Sequence

1. Snap a meal.
2. See nutrients beyond calories.
3. Updated Running Totals.
4. Today through your health lens.
5. Food ideas for today's gaps.
6. GLP-1 companion.
7. Privacy and estimates disclosure.

Custom Product Pages

Apple supports up to 70 custom product pages, and these can be tied to ads.

Source: Apple Custom Product Pages

Recommended custom pages:

Keyword Themes

Core:

• nutrition tracker
• food tracker
• meal scanner
• calorie tracker
• AI food scanner
• macro tracker
• nutrient tracker

Differentiated:

• GLP-1 nutrition
• high blood pressure diet
• sodium tracker
• cholesterol tracker
• PCOS nutrition
• gout diet
• diabetes nutrition
• protein tracker
• fiber tracker

Need caution:

Condition keywords may attract scrutiny if listing copy implies treatment. Use "track," "support," "nutrition lens," and "talk to your clinician" language.

Google Play

Google Play supports custom store listings and store listing experiments.

Source: Google Play custom store listings

Trace should use Google Play experiments for:

• First screenshot: scan speed vs running totals.
• Short description: AI scan vs health lens.
• Feature graphic: meal photo vs app UI.
• GLP-1 language: "companion" vs "nutrition clarity."

Asia Store Strategy

The current app localization is a latent launch asset only if the store metadata is localized too. In-app EN/zh-CN/zh-TW/KO/VI without matching App Store / Play listings creates a broken promise at the exact moment of conversion.

Required APAC store pages:

Do not reuse US screenshots with translated labels. Asia screenshots should show local food and local nutrients of concern. For Singapore and Korea, this is not cosmetic; it is proof that Trace understands the user's actual meals.

11. Paywall and Onboarding Strategy

Current Product Reality (as shipped — read before recommending changes)

Trace has:

• Monthly and annual plans; annual pre-selected; annual 3-day trial once/user.
• Every food-logging path Pro-gated.
• Free GLP-1 companion, IF, water, exercise, limited non-food surfaces.
• A free pre-paywall sample-meal demo that already shows running-totals output. This is the single most important and most-overlooked fact for this section. The shipped onboarding renders a demo meal's macros + per-condition lens readings before the paywall (SampleMealResultScreen.tsx), so a non-paying user already experiences the core "photo → running totals" proof.

The shipped first-session order is therefore:

onboarding steps → Plan Loading → Food Lens Reveal ("see it on a meal") → Sample Meal Picker → Sample Meal Result (running totals, free) → Paywall → First Scan Prompt (post-payment, where the OS notification prompt fires).

That is better than a paywall-first flow and aligns with findings #4 and #6 (prove value in seconds, before the ask). Earlier drafts of this report recommended a paywall-before-any-proof sequence — that would be a regression and should be discarded.

Trial-reconciliation note (verified, already a tracked cleanup):

The product still carries dead "3 lifetime AI meal scans / no credit card required" language from the pre-2026-04-19 freemium model — live in PRODUCT.md, flagged in PROGRESS.md, plus orphaned logMeal.trial* locale keys ("3 free AI scans") across mobile/web locales. The store-managed 3-day annual trial replaced it. Reconcile docs, store copy, onboarding, and paywall so users never see two definitions of "trial." This is a known repo task, not a new discovery.

Recommended First-Session Flow (optimize what ships, don't replace it)

Keep the shipped sequence and tune it:

1. Make the Food Lens Reveal and Sample Meal Result condition-relevant, not a generic demo meal — the proof lands only if the sample total speaks to the lens the user just chose (e.g., sodium for high-BP, protein/fiber for GLP-1).
2. Instrument and watch the Sample Meal Result → Paywall drop-off; that transition is the real conversion moment, and the events to measure it already exist (sample_preview_completed, onboarding_paywall_shown).
3. After trial start, route straight to first scan (already shipped via FirstScanPromptScreen); keep the OS-notification prompt on that screen only.
4. Test the §5.5 corollary: because a real scan costs ~$0.0036, an A/B of "few free real scans before paywall" vs the current sample-demo-then-paywall is economically free to run — decide it on conversion, not cost.

The goal is not paywall conversion alone. It is post-Sample-Meal-Result conversion and post-paywall activation.

Paywall Copy Direction

Headline options:

• "See your food through the lens that matters."
• "Start your nutrition lens."
• "Make today's meals easier to understand."

Subhead:

• "Scan meals and see how they change your running totals for the nutrients your profile is watching."

Bullets:

• AI meal scans.
• Running daily totals.
• Concern-aware nutrient lens.
• Food ideas for today's gaps.
• GLP-1 companion included free.

Avoid:

• "Fix your condition."
• "Know exactly what's in every meal."
• "Never eat the wrong thing again."
• "Lose weight faster."

Trial Length

Trace currently has a three-day annual trial. RevenueCat's data warns that many three-day trial cancellations happen on Day 0. The tactical implication is not necessarily "switch to 7 days." It is:

• Make Day 0 excellent.
• Trigger first scan immediately after trial start.
• Send first-60-minute retention nudges carefully.
• Track Day 0 cancellation reason if possible.

Later test:

• 3-day trial vs 7-day trial for GLP-1 traffic.
• Annual default vs monthly default for condition traffic.
• Hard paywall before first scan vs sanctioned sample scan/demo before paywall.

Any sample/demo path must respect food-logging Pro gating decisions and API cost.

12. Mistakes and Failure Modes

Trust checklist before scale:

• Google Play Data Safety complete and accurate.
• Health apps declaration complete.
• Privacy policy covers food photos, conditions, AI processing, analytics, deletion, and Health Connect if used.
• In-app account deletion works.
• Store screenshots do not imply medical treatment.
• Creator brief explicitly bans unsafe claims.
• Paid ad review checklist exists.

13. Strategic Recommendations

Best First Audience

GLP-1 users who are trying to keep nutrition steady without diet-culture noise.

Why:

• Current demand is strong.
• The creator ecosystem is active.
• Trace already has a free companion surface.
• Nutrition logging has a clear upgrade path.
• The product can provide day-level clarity without making medical claims.

Best Secondary Audiences

1. High BP / sodium-aware users.
2. Cholesterol / fiber and saturated-fat-aware users.
3. PCOS nutrition users.
4. Gout users.

Best Positioning

Primary:

Food logging for people managing something real.

Product proof:

Snap a meal and see how it changes today's running totals.

GLP-1 wedge:

A calmer way to keep nutrition steady on GLP-1.

Best Initial Channels

1. GLP-1 micro-creators.
2. Dietitian and condition-specific creators.
3. TikTok/Reels organic and Spark amplification.
4. App Store custom pages and ASO.
5. Web-to-app landing pages for GLP-1, high BP, PCOS, cholesterol.
6. Apple Search Ads on long-tail high-intent terms.

Best APAC Initial Channels

1. Singapore: TikTok/Reels/YouTube creator demos, WhatsApp referrals, dietitian credibility, Google Play listing tests, local-food SEO.
2. Korea: YouTube/Instagram, Naver Blog/Cafe, KakaoTalk sharing, Korean dietitian/health creators, Korean food-scan proof.
3. Taiwan: LINE sharing, zh-TW store listing, YouTube/Instagram, high-BP/ cholesterol/diabetes-adjacent nutrition content.
4. Vietnam: Zalo/TikTok/Facebook community tests, VI content, Android-first learning, low-budget feedback loops before subscription spend.

What Not To Do

• Do not launch as a calorie-only app.
• Do not use before/after body transformation claims.
• Do not score meals red/green.
• Do not scale paid UA before first-value metrics are known.
• Do not use broad wellness influencers first.
• Do not let GLP-1 copy imply medication or clinical advice.
• Do not call the app "updated" or "ready" in release handoff without verifying the shipped artifact, per repo release rules.

13A. Marketing Strategy Playbook (Deep)

The economics (§5) prove paid cannot lead. This section is the how of an organic-led launch for a solo founder with effectively no paid budget on the #1 wedge. Every benchmark is sourced (notes file); inference is flagged.

13A.0 Sequence the engines — do not run them all at once

Cal AI's actual playbook was not "do everything." It ran engines in sequence: influencer/organic saturation first, then paid, then affiliate — never simultaneously. Trace should do the same, adapted to its constraints:

The discipline matters more than the list: prove one engine produces attributable, retained payers before lighting the next.

13A.1 Creator seeding — the launch engine

• Structure: gift + affiliate/commission, no upfront fee. Free product alone converts only nano/micro creators; the gift-plus-code model lifts post-rates without cash. Mid/large creators require retainers — that is Cal AI's paid version (150+ creators on retainer, ~4 posts/mo, sourced via a dedicated content-trained discovery account). A solo founder runs one founder account + a small seeded micro-creator set and should expect months before signal.
• Use the in-app referral codes as the affiliate substrate. They double as the only GLP-1 attribution path (organic has no UTM — §5.6), so codes are not optional for the #1 wedge; they are the measurement.
• FTC is non-negotiable for health. Every gifted/affiliate post needs clear #ad/#sponsored disclosure regardless of creator size (enforcement against small creators rose in 2025–26). Brief creators to share experience ("here's my running total") never outcomes ("this lowered my cholesterol").
• Brief template: hook + scene-by-scene script + CTA + reference videos + deliverable specs + usage rights (pay a flat fee upfront for lifetime/raw footage) + required legal language + an explicit "what we do NOT claim" list.
• Cost anchors: freelance UGC runs ~$150–300/asset; health affiliate commissions 5–30%. Both beat a $2.50–5.00 paid CPI when the content is reusable.

13A.2 ASO — the highest free leverage (with health-specific landmines)

• Verbs, not nouns, get you rejected. Condition names are allowed; "manage / lower / diagnose / measure" trips Apple Guideline 1.4.1, and Google Play's Health Content policy requires a "not a medical device; does not diagnose, treat, cure or prevent — consult a professional" disclaimer in the description. Safe: "understand how meals add up for cholesterol." Unsafe: "lower your cholesterol."
• Never put drug brand names in metadata. Ozempic/Wegovy/Mounjaro/Zepbound → Apple 5.2.1 trademark rejection, and Novo Nordisk filed 130+ trademark suits in
  2025. Use "GLP-1" (a drug class — broader keyword anyway).
• Screenshots are the highest-ROI free lever (benefit-led first screenshot drove up to +9pp install lift; first two screenshots do most of the work). For Trace, lead with the condition-lens output card, not the camera — the camera is Cal AI's story; the interpretation is yours.
• Store-metadata localization is the best leverage-per-hour you have. Trace already ships 5 in-app locales (EN/zh-CN/zh-TW/KO/VI); only the store listings need translating, and localized metadata lifts CVR ~26–30% in non-EN markets.
• Custom Product Pages: build 2–3, not 12. Apple reports +156% CVR on matched referred traffic (AppTweak's independent measure is a more sober +5.9–8.6%) — but a CPP is worthless without inbound traffic to point at it. Build GLP-1 + one other, assign condition keywords, deep-link from tracenutrient.com.
• ASA popularity data is your free keyword tool pre-traction — don't buy Sensor Tower/AppTweak before you have volume.

13A.3 Web-to-app vs the sample-demo — don't blindly copy Noom

Noom's quiz converts (up to 113 screens, email gate ~33% before the result reveal, the quiz is the demo because users never see the real UI before paying; sunk-cost of 10 minutes drives the paywall). H&F top performers hit 23%+ download-to-trial. But Trace already ships the cheaper, arguably better instinct: a free pre-paywall sample-meal demo that shows real output, which Noom deliberately withholds. For a product whose value is visual, a short condition-select → sample-lens-result → paywall flow may out-convert a 113-screen quiz. Test both; do not assume the Noom playbook transfers. Compliance line on any quiz: personalize and educate, never diagnose — output is "your nutrition focus for gout," never "you have / are at risk of X."

13A.4 Lifecycle — a 3-day trial is a Day-0 game

55% of 3-day-trial cancellations happen on Day 0, and 82% of H&F trials start on download day (no warm-up). The sequence that matches that reality:

Push + in-app carry a 3-day window; email is secondary (health email opens ~48% but clicks ~1.5%). Trace's Rule 5 (notification opt-in only post-payment) already matches best practice. Pre-churn save: 35% of annual cancellations hit in Month 1; pause beats cancel (no payment re-entry) — branch the save offer on cancel reason. Win-back is near-dead: ~95% of annual cancellers never return, so build one win-back email and pour the rest of that effort into the Day-0 aha and the Month-1 save flow. Highest-EV experiment overall: test a 5–9 day trial (§2.3) — worth more than any lifecycle copy.

13A.5 Referral — a multiplier, not a launch channel

Two-sided give-get is standard (91% of successful programs). Make share targets native — WhatsApp + SMS carry ~90% of referral sharing, so a copyable code alone underperforms. Mature programs drive 20–35% of installs and referred users retain ~37% better at D30 — but that is mature; at launch with near-zero base referral does little. Model it as a multiplier on whatever seeding/organic produces, not a source. Prefer a free month over cash (cheaper, self-selects engaged users), and defend against self-referral fraud (IP/device/velocity checks). The code system already exists in-app — wire it to native share sheets.

13A.6 Community, content, and SEO — start now, harvest in year 2

• Condition subreddits (r/PCOS, r/GLP1, r/gout, r/Cholesterol, r/loseit): the fast path to a ban is link-dropping. Value-first (many health subs enforce 99/1 or ban self-promo outright); founder disclosure ("I built this") raises trust. Highest-leverage use is free product research, not acquisition — there is no clean sourced case of a health app scaling primarily on Reddit.
• Founder build-in-public (X/LinkedIn, anchored on a personal condition story) is real but survivorship-skewed — plan for the median ($1–3K MRR in 6 months), not the viral outlier (which usually had a pre-existing audience).
• SEO is Trace's latent moat — gated by one thing. The 976-ingredient × 12-condition dataset is genuine programmatic-SEO inventory, but these are YMYL queries held to Google's highest E-E-A-T bar; the Sept 2025 update specifically penalized health pages with missing author credentials. A credentialed (RD/MD) reviewer byline is the single unlock — without it, YMYL ranking is near- hopeless. Only ~30–40% of permutations have real volume, and the category takes 12–24 months to mature. Start now, harvest in year 2; organic CAC runs ~3× below paid once mature.

13A.7 The real creative problem — dramatizing interpretation, not a number

Cal AI went viral because "snap → calories" is legible in under 3 seconds. Trace's value (interpretation, not a number) is harder, and pretending otherwise is the biggest creative risk. Education beats selling; the hook lives in the first 3 seconds. Formats that map to a subtle value prop:

• Reveal / accuracy test: "I logged a 'healthy' lunch — watch what it does to my gout numbers." The running-total reveal is the surprising payoff = shareable. This is the closest analog to Cal AI's signature "AI vs manual" format.
• "What I eat in a day on a GLP-1": a massive native genre — the app appears as the interpreting tool, not the subject. Frame around nutrition/protein/ side-effects, never weight loss (TikTok's May 2026 organic suppression).
• "Things your nutrition app won't tell you about [condition]": lo-fi educational explainer; no production value required.
• Myth-busting the running-totals thesis: "you think X is bad for cholesterol — but it's your daily total that matters." This teaches the actual differentiator while entertaining.

Reality check: a solo founder is not Cal AI's 150-creator operation, and the reveal-test format is a workaround, not parity — it will never match a calorie number's instant legibility. Set the expectation: daily posting for months before signal.

13A.8 Cross-cutting takeaways

1. The highest-EV experiment is trial length (3 → 5–9 days, +~10–15pts trial-to-paid, two independent datasets) — not any piece of marketing copy.
2. Sequence channels (organic/seeding → referral multiplier → non-GLP-1 paid), never simultaneously.
3. GLP-1 is doubly constrained — no paid ads and organic weight-loss suppression — so lead it with the free companion + nutrition framing.
4. Win-back is near-dead (95%) — redirect that effort to the Day-0 aha and the Month-1 save flow.
5. A credentialed medical reviewer gates SEO, store-listing credibility, and creator-claim safety simultaneously — secure one early; it is the highest- leverage single hire/advisor.
6. The free sample-meal demo is a real asset Noom lacks — it may justify a shorter funnel and is the cheapest pre-paywall proof you have.

14. 30/60/90-Day Launch Plan

Days 1-30: Foundation and Proof

Goals:

• Confirm first wedge.
• Build measurement spine.
• Produce first creative library.
• Prepare store and landing-page tests.

Actions:

1. Finalize launch positioning:

   • Primary: "food logging for people managing something real."
   • Wedge: GLP-1 nutrition steadiness.

2. Reconcile trial story:

   • Store-managed 3-day trial vs any older free-scan trial copy.
   • Ensure paywall, store listing, website, and onboarding agree.

3. Attribution setup (the event catalog already exists — see §5.6):

   • Ship an MMP or, at minimum, creator codes + per-wedge vanity URLs + App Store custom-page-ID capture, so source stops being hardcoded 'organic'.
   • Wire source / campaign / creator / custom-page-ID through to the existing events. Without this, creator CAC is unmeasurable and paid spend is blind.
   • Confirm the existing events fire end-to-end: first scan, scan_result_viewed, Food Ideas, second scan, cancellation-by-day.

4. Creator seed list:

   • 50 GLP-1 micro-creators.
   • 25 dietitians.
   • 25 PCOS/high-BP/cholesterol creators.

5. Creative production:

   • 30 raw UGC concepts.
   • 10 screen-record demos.
   • 5 founder POV videos.
   • 5 RD/expert-style scripts.

6. Landing pages:

   • GLP-1 nutrition.
   • High BP sodium.
   • PCOS nutrition.
   • Cholesterol fiber/saturated fat.

7. App Store assets:

   • Default screenshots.
   • GLP-1 custom product page.
   • High BP custom product page.
   • PCOS custom product page.
   • Singapore local-food screenshot set if APAC proof is in scope.
   • Korean / zh-TW / Vietnamese store metadata drafts, even if not launched immediately.

8. APAC proof setup:

   • Choose one first APAC market; recommendation: Singapore.
   • Build a 25-meal local scan QA set for that market.
   • Add market-specific share/referral rail: WhatsApp for Singapore first.
   • Define APAC cohorts separately in analytics; do not blend them into US install-to-trial or payer-CAC benchmarks.

Success thresholds:

• First scan completion from trial starters: 70%+.
• Updated Running Totals receipt view after first scan: 60%+.
• Day 0 trial cancellation below benchmark concern level.
• Qualitative user comprehension: users can explain what Trace does in one sentence after first scan.

Days 31-60: Controlled Launch Experiments

Goals:

• Test channel quality.
• Identify creative winners.
• Validate CAC ranges.

Actions:

1. Creator seeding:

   • Ship to 20 GLP-1 creators with codes/links.
   • Pay small fixed fees where needed.
   • No affiliate bounty yet unless tracking is solid.

2. Paid amplification (non-GLP-1 only — GLP-1 creative cannot be boosted, §6.1):

   • Spark/boost only top organic posts on heart-health/sodium, cholesterol, or PCOS framing; keep GLP-1 strictly organic.
   • Budget caps per creative; kill if activated-trial CPA exceeds the §5.4 ceiling (payer CAC ≤ ~$25 target, ~$35 hard tolerance).

3. Apple Search Ads:

   • Brand terms.
   • Long-tail "GLP-1 nutrition tracker", "sodium tracker", "PCOS nutrition tracker" style terms.
   • For APAC, use Google Play custom listing experiments first if Android is the active release path; do not assume ASA is the first paid intent channel.

4. Landing-page tests:

   • GLP-1 page to App Store custom page.
   • Direct App Store vs web-to-app quiz.
   • Singapore sodium/local-food landing page -> Google Play listing.

5. Paywall tests:

   • Headline variants.
   • Annual value framing.
   • Concern-specific chip cloud emphasis.

6. APAC channel tests:

   • Singapore: 10 local-food creator videos; WhatsApp share/referral test.
   • Korea: 5 Korean-native screen-record demos; Naver content test if Korean food QA is ready.
   • Vietnam/Taiwan: content-only tests unless pricing and store metadata are ready.

Success thresholds:

• Install-to-trial: 12-15%+ on qualified paid/creator traffic.
• Trial-to-paid: 40%+.
• Payer CAC: <$50 early, <$30 target.
• D7 active among trial starters: strong enough to justify more spend.
• At least one creator cohort with payer CAC under target.

Days 61-90: Scale Winners, Kill Losers

Goals:

• Turn winning wedge/channel into repeatable system.
• Prepare broader launch only after first economics are known.

Actions:

1. Scale top 3 creator formats.
2. Build creator brief v2 from actual conversion data.
3. Expand custom product pages.
4. Add high-BP/cholesterol creator tests.
5. Start small affiliate pilot only with quality controls.
6. Publish founder/product essay:
   • "Why Trace does not judge individual meals."
7. Build PR angle:
   • Safer alternative to generic AI calorie tracking for people managing real health concerns.
8. Expand APAC only if the first market proves food trust:
   • Singapore -> Korea only after local-food scan QA and Korean store copy pass.
   • Singapore -> Taiwan only after zh-TW screenshots and LINE sharing are ready.
   • Vietnam remains community/content until price sensitivity is tested.

Scale decision rules:

• Scale a channel if payer CAC is under $30 or under $50 with strong annual mix and retention.
• Pause if Day 0 cancellations spike.
• Pause if trial starts are high but first scan/receipt activation is low.
• Pause if refunds/cancellations concentrate in one creator cohort.
• Double down if a creator cohort has lower CPI, higher receipt view, and higher second-scan rate than paid baseline.
• Double down in APAC only if local-food scans produce trust, not merely installs. A low CPI in Vietnam or Singapore is not useful if receipt views, second scans, and paid conversion lag because the food output feels generic.

15. Appendices

15.1 Suggested Analytics Dashboard

Daily:

• Installs by source.
• Onboarding completion.
• Paywall views.
• Trial starts.
• First scan completion.
• Updated Running Totals receipt opens.
• Day 0 cancellations.
• Purchases.
• Refunds.

Weekly:

• Creator cohort CAC.
• Install-to-trial by source.
• Trial-to-paid by source.
• D7 retention by source.
• First-week scan count by source.
• Annual/monthly mix.
• Trial cancellation timing.
• LTV projection.

15.2 Creator Outreach Template

Subject: Trace for your GLP-1 / nutrition routine

Hi [Name],

I'm building Trace, a nutrition app for people managing real health concerns. It lets someone scan a meal and see how it changes their running daily totals for the nutrients their profile is watching.

We're looking for a few creators to test a calm GLP-1 nutrition workflow: protein, fiber, hydration, and daily clarity without food shame or per-meal good/bad scoring.

Would you be open to trying it and, if it fits your audience, making one short routine-style video? We'd provide a creator code, talking points, and clear claim guidelines.

15.3 Creator Brief Rules

Creators may say:

• "Trace helps me see where my day stands."
• "I scan meals and see running totals."
• "It tracks nutrients my profile is watching."
• "It is not a diagnosis."
• "It does not judge individual meals."

Creators may not say:

• "Trace treats/prevents/cures [condition]."
• "This food is safe/unsafe."
• "You should eat this on GLP-1."
• "This will prevent muscle loss."
• "This meal is bad for PCOS/gout/diabetes."

15.4 Paid Ad Testing Matrix

15.5 Source Appendix

Market and subscription:

• Sensor Tower State of Mobile 2026
• RevenueCat State of Subscription Apps
• RevenueCat 2026 subscription benchmarks
• RevenueCat web-to-app funnels
• AppsFlyer State of App Marketing 2025
• Liftoff 2025 Mobile Ad Creative Index

Store strategy:

• Apple Custom Product Pages
• Apple Product Page Optimization
• Google Play Custom Store Listings
• Google Play Store Listing Experiments

Case studies:

• TechCrunch: MyFitnessPal acquired Cal AI
• Business Insider: Cal AI tiny team
• Simple / Fitt Insider: $160M ARR claim
• Ladder funding release
• RevenueCat interview with Ladder
• Strava acquiring Runna
• Yuka company site
• Apple 2025 App Store Awards
• Tiimo App Store listing
• TechCrunch on Clyx
• Business Insider on Apple Invites / Partiful
• TechCrunch on Tea removal
• TechCrunch on Neon data exposure
• Business Insider on Cluely
• Appfigures on ChatGPT mobile spend
• Rork Wrestle AI case study

Competitor pricing:

• Cronometer Gold
• MyFitnessPal App Store
• MacroFactor pricing
• Cal AI App Store
• Cal AI site
• Lose It! App Store
• Lifesum App Store
• YAZIO App Store
• MyNetDiary Premium
• Foodvisor App Store
• Carb Manager Premium
• FatSecret Premium
• Shotsy
• Shotsy vs MeAgain
• Noom cost
• Noom plan pricing
• Noom Med
• Healthify plan page

Asia / APAC sources:

• AppsFlyer State of App Marketing in Asia 2025
• AppsFlyer State of App Marketing in Vietnam 2025
• AppsFlyer State of App Marketing in India 2025
• RevenueCat State of Subscription Apps 2025
• DataReportal Singapore 2025
• DataReportal Singapore 2026
• DataReportal South Korea 2025
• DataReportal South Korea 2026
• DataReportal Vietnam 2025
• DataReportal Vietnam 2026
• DataReportal Taiwan 2026
• LY Corporation LINE global data
• Singapore MOH on LumiHealth
• Straits Times on LumiHealth / Healthy 365
• HPB Nutri-Grade
• MOH sodium/saturated fat Nutri-Grade expansion
• Healthify Google Play listing
• Healthify App Store listing
• Healthify funding announcement
• TechCrunch on Speak
• Forbes on Speak
• TechCrunch on DeepSeek
• The Verge on RedNote / Xiaohongshu
• BioWorld on Wegovy Korea launch
• Korea Biomedical Review on GLP-1 demand
• Linklaters on China app filing
• CMS digital health apps and telemedicine in China
• JMIR mHealth China sports/health app privacy study

15.6 Self-Review Notes For Next Pass

Addressed in the 2026-06-15 codebase-grounded revision:

• §5 rebuilt on measured COGS → derived CAC ceiling (was hand-waved guardrails).
• §5.6 + §14 corrected: events already exist; attribution is the real gap.
• §6.1 added + extended: GLP-1 is organic-only AND organically suppressed (no weight-loss framing).
• §11 corrected to the shipped sample-meal-then-paywall flow (was paywall-first).
• §8 added the GLP-1 free-tier-vs-monetization paradox.
• §1 findings 12–13 sharpened; 16–19 added.

Addressed in the 2026-06-15 research pass (web-verified):

• Verification done — all external figures web-checked; one correction (AppsFlyer $65B/2024, not $78B), Liftoff UGC precision caveat, Simple labeled self-reported, plus the material 3-day-trial → 25.5% trial-to-paid caveat folded into §2.3 and the §5 CAC model. Results table in the notes file.
• Competitor teardown done — new §4A (Cronometer, calorie-first pack, GLP-1 field: Shotsy/Noom/Caloria/telehealth, whitespace, price exposure, TAM).
• Marketing strategy expanded — new §13A playbook (sequencing, creator seeding, ASO landmines, web-to-app, lifecycle, referral, SEO, creative for a non-demoable value prop).

Still open after this revision:

• Refresh LTV once renewal is observed — the model's one free variable; re-run §5.3/§5.4 with real D30/renewal data before scaling any spend.
• Platform + geo decision — state Android-first vs iOS-first and the EN-vs-multilocale launch scope (finding 19).
• Secure a credentialed (RD/MD) reviewer — gates SEO + store-listing credibility + creator-claim safety (§13A.6/.8).
• Pull real non-AI infra cost/MAU to firm up the §5.2 COGS line; cite KFF primary for the GLP-1 TAM; find a quiz-step conversion benchmark.

Added in the 2026-06-16 Asia quality pass:

• New section 2A with Asia/APAC market context, quality review of US bias, country sequencing, Singapore/Korea/Vietnam/Taiwan/India/mainland-China implications, and Asian case studies.
• Added Healthify, Speak, LumiHealth/Healthy365, messaging-platform, DeepSeek, and RedNote/Xiaohongshu rows to the case-study matrix.
• Added APAC channels to section 6, Asia store strategy to section 10, APAC initial channels to section 13, and APAC steps/decision rules to the 30/60/90 plan.
• Updated the platform/geo open question with a working recommendation: Singapore first APAC proof market, Korea second only after Korean food-scan trust is proven, Vietnam/Taiwan content tests later, and mainland China out of first-launch scope.

Added in the 2026-06-16 pricing pass:

• Refreshed §4A competitor pricing with current observed/public prices across scanner apps, classic trackers, premium AI nutrition apps, GLP-1 companions, Noom/coach programs, and Healthify/APAC context.
• Reframed Trace from "top of the field" to "premium tracker pricing": expensive versus scan-only, roughly in-line with MFP Premium, below MFP Premium+/ Foodvisor/some Lifesum IAPs, and far below Noom/coach/clinic.
• Added annual-discount math and concrete pricing experiments: keep $79.99 and test $14.99 monthly, test $69.99 annual with $9.99 monthly, or keep prices and improve condition-lens justification first.
• Added APAC pricing caution using RevenueCat 2026 geography/price medians: Singapore/Korea can be premium proof markets, but Vietnam/India cannot inherit a US-style annual paywall assumption.