yes here are a few of different areas:

Thanks all, really appreciate the kind words. Feedback is welcome on anything: bug reports, missing features, things that feel rough, or just "this works for my setup." A few features are flagged Experimental right now and I'd like to harden them enough to drop the badge.

Native Android app is in active development. There's also a sister project in the works called LiftTrace under the same TraceApps umbrella, same self-hosted Docker setup but for workout tracking (sets, reps, programs, PRs). Not public yet but close.

Thanks for asking. Reception of this app has actually been positive overall since my first post here, with upvotes well ahead of downvotes.

Last week I posted about my newer app LiftTrace, which I also build with AI assistance. Once folks realized AI was part of how I work, "AI slop" became the read on that post and the downvotes came fast. I assume some of this week's downvotes here are coming from the same crowd reacting to a familiar name, which is fair. Everyone is entitled to their opinon and I respect that.

I've never hidden the AI involvement, and from what I can tell on the NutriTrace GitHub page real users are getting value out of it: stars are steadily climbing and issues and enhancement requests are coming in. I'll keep posting these updates because I think the apps are genuinely useful, I use them every day myself, and I wouldn't share them if I didn't believe they could help someone with their own health or fitness journey.

Happy to answer any other questions folks have.

That is correct, and it is called out in the README under Apps → iOS and in the Support section at the bottom. iOS needs a Mac, an iPhone, and a paid Apple Developer account, none of which I currently have. The Support section is where I mention that donations go toward exactly that. Apple Health sync specifically needs a native iOS wrapper since the data isn't exposed to PWAs, so it has to wait on the same blocker. I hope to someday get this out to the community.

Open Food Facts (OFF) for barcodes. Free, open license, community-edited. Their API: https://world.openfoodfacts.org/api/v2/product/.json

That URL should import cleanly; it's a standard food blog with the markup the importer expects.

TikTok though, honestly, no. TikTok pages don't expose the recipe text to scrapers and the AI fallback has almost nothing to work with. A real TikTok URL importer would need to call TikTok's caption API and transcribe the video audio, which isn't built yet.

Workaround that may possibly work today: screenshot the recipe overlay (or the comment where the creator wrote it out) and use Photo Import the AI extracts the recipe from the image. Two taps, same result.

here are a few pics. i have to setup some demo screenshots for github, on my to do!

Not right now. I want to get all my apps past the RC stage and into stable GA but will certainly consider it in the future.

Interesting idea, but that's out of scope for this app, Fathom is just a Jellyfin/YouTube/Seerr client, with no torrent or P2P layer, so there's nothing for I2P to integrate with.

:)

Is the docker image public? I’m getting an “unauthorized” error when attempting to pull it. I’m not getting that error for other ghcr.io images. But I’m not docker expert, so I may be doing something wrong.

Should be fixed now, package was set to private by default on first push. Just flipped it. docker pull ghcr.io/traceapps/nutritrace:latest works without auth now. Thanks for flagging it.

Yes indeed! On my future to do!

Updated, thank you.

Glad the workaround clicked. Custom-nutrient "water" plus your own recipes is the cleanest path for comprehensive accounting without waiting on a built-in feature.

The "two lists feels more complicated than one" observation is fair and worth sitting with. Ill add this as a possible future feature

Thanks for the thoughtful feedback.

Mealie integration allows you to pull in your Meal/Recipe from your self hosted instance of Mealie via api. If you have nutrition facts set there by the recipes total weight, it will pull in that data and then you can set your serving size accordingly so it calculates properly. It also pulls in the recipe pic if set in Mealie.

For docker, It is only one service. everything else can be setup in app once you are in if you so choose. Android App can be used with or without server.

It is an android app with Health Connect Support! Android app works with or without the server! :)

Here is what i see as some differences today between CookTrace and Tandoor:

CookTrace:

• Pantry is a real first-class catalog, not a tag list. Barcode scanner, Open Food Facts + USDA lookup, per-item stock / serving size / nutrition, plus an "8 / 10 in pantry" match pill on every recipe card. Tandoor has the food list; CookTrace treats it as a primary surface.
• AI assistant with tool use — not just a chat bubble. Trace can log a cook, plan a cook, add things to the shopping list, mark a pantry item out of stock, import a recipe URL, etc. by reading and writing your real data
• FDA-style Nutrition Facts box auto-computed per recipe from pantry-linked ingredients
• Android app with full offline mode (on-device SQLite, differential sync when you reconnect)
• NutriTrace federation can import foods from NutriTrace directly into CookTrace's pantry.

Where Tandoor still wins today: PDF / image OCR bulk import, longer track record, larger ecosystem, iCal meal-plan feeds.

Importer's there in CookTrace, so you can move a copy over to compare with zero risk to your existing library whenever the time shows up.

Honestly, not automagically. CookTrace's bulk importers today handle JSON, HTML, schema.org Recipe markup, and full-backup zips from Mealie / Tandoor / Paprika. Plain text, RTF, and PDF aren't on that list yet, and there's no "point at a folder and import everything" mode.

What works today for the same end goal:

• Photo Import — point Trace AI at an image of any recipe (including a PDF you've screenshotted) and it extracts it. Fine for a handful, probably painful for hundreds.
• Trace AI chat — paste the recipe text into the assistant and ask it to create a recipe. Same idea, no image step.

A proper OCR import is a worthwhile feature. I created a feature enhancement request in the GitHub repo, so that in the near future I can set aside some time to explore how feasible it would be to implement.

just added. Was a request for my other NutriTrace App so made sure to add it here as well.