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.
Nice work, exactly the kind of bridge that makes leaving MFP a lot less painful for self-hosters. Would you be OK with me linking the gist from the NutriTrace README (under Foods & Meals) and from inside the Bulk Food Import modal? Happy to credit it as your script with a link back to the gist.
Either way, thanks for putting it together.
Thank you so much! I appreciate it!
Yes! Settings → Backup → Nutrition Import. Built-in adapters for MyFitnessPal, Cronometer, LoseIt, and a generic CSV shape. Export your diary from MFP (it’s a CSV in their account settings), upload it, preview, commit. Skip / Merge / Replace per-date semantics, so you can re-import safely without overwriting.
Open Food Facts (OFF) for barcodes. Free, open license, community-edited. Their API: https://world.openfoodfacts.org/api/v2/product/<barcode>.json
Yes, Health Connect is supported on the Android app. As long as Samsung Health is set to write to Health Connect (Samsung Health → Settings → Connections → Health Connect), NutriTrace can read steps, sleep, heart rate, weight, and exercise from it.
Honestly though, this path hasn’t had many testers yet, so if you give it a shot I’d really appreciate a heads-up on what works and what doesn’t. Feedback (positive or bug reports) is welcome on GitHub.
Thank you! Enjoy the app!
Great glad that fixed it!
Thanks for catching this. The Cronometer adapter was treating the parsed gram count as a serving multiplier, so a 750g entry got its calories multiplied by 750. The “NaNg” had the same root cause: the portion was stored as the raw string “750.00 g”, which JS coerces to NaN when the diary tries to multiply it for display.
The layout overlap on the duplicate-day dialog is should now be fixed too (added a divider so the buttons have proper visual separation from the radio options).
Both are hopefully now fixed and pushed in rc.14. Grab the latest package, delete the affected day from your diary, and re-import. Items should hopefully now come in with the right values.
Thanks again for the detailed report.
I gave this a shot, but when I press the “preview” button I just get a little popup that says “Invalid CSRF token”.
Hmm… i think i see the issue. The preview / commit upload was missing the CSRF token, so the server was rejecting it before it even read the file. Just pushed a fix. Once you pull it down, hard-refresh the page (Ctrl+Shift+R / Cmd+Shift+R) to grab the new bundle and try again.
Import feature has been added to app as experimental in latest build (1.0.0-rc9). Please test and let me know how it works for you.
The JSON-massage route may work. Diary items are self-contained snapshots, IDs in your file are ignored on import, and the only real catch is that re-importing a date overwrites the existing entry. Happy to drop the field-by-field shape if you want to go that route.
That said, native CSV importers for the popular apps (MFP, LoseIt, Cronometer, etc) are now on the near-term roadmap (thanks to your suggestion) as the proper path for this. If you can hold off a bit (and use one of the above), that’ll be much easier.
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.
Barcodes work internationally. i can confirm because i have used in both europe (italy) and africa (south africa). Only difference between nutrition facts i see is that the US uses Sodium and i want to say that at least Europe uses Salt. I have a built in conversion where when one is used the other is automatically calculated.
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.
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.
Cookidoo has no public API and their ToS prohibits scraping, so a direct integration would be both legally fragile and maintenance-heavy (the scraper breaks on every UI change Vorwerk pushes). The indirect path that works today: Mealie is a self-hosted recipe manager that imports Cookidoo URLs as one of its many recipe sources, and NutriTrace has Mealie integration built in (Settings → Mealie). Your wife adds recipes from Cookidoo into Mealie once, and they show up as searchable foods in NutriTrace with full nutrition.
Also worth mentioning: I’ve got a sister app called CookTrace (may not be final name) in development as a purpose-built self-hosted recipe manager that pairs natively with NutriTrace (same UI patterns, same AI assistant, federation already wired between them). It has a schema.org Recipe scraper for URL imports, though Cookidoo itself is gated content so it’d still need either a Mealie middle layer or manual entry. Currently private; aiming for a public release in the next month or so.