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, appreciate it!
Let me know your issues and post server/browser console/app logs, and ill do my best to assist. You can also create an issue if you feel that this is a bug in the repo. Outside of this i do want to mention, im working on a suite of “Trace” apps. One of which is a Recipe app. I love Mealie, but wanted a bit more for myself, and have created something that i think will be special. It also allows for direct api integration to and from NutriTrace. Will hopefully have a beta that will be publicly available in the next month or so if interested.
latest update has been released!
Thank you and great question. There’s already an open issue for this in the repo (#31) and the fix is in dev. Next RC will have it. The Android scanner will use the bundled ML Kit model directly, with no Google Play Services calls at runtime. Same scanning engine.
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.
Yes, TLS is left to a reverse proxy (nginx, Caddy, Traefik, Cloudflare Tunnel). The container serves plain HTTP on a port you map; whatever you put in front handles the cert.
No wger integration today. NutriTrace covers food + wellness + workout sync (from Fitbit/Garmin/Withings/Google Health/Health Connect), but doesn’t connect to wger or other dedicated exercise-routine apps. My soon to be released app in the Trace family of apps will be dedicated to lifting, and will include wger integration to name one of its exercise databases (as well as support for custom imports).
It is an android app with Health Connect Support! Android app works with or without the server! :)
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.
Open Food Facts (OFF) for barcodes. Free, open license, community-edited. Their API: https://world.openfoodfacts.org/api/v2/product/<barcode>.json
Not directly. NutriTrace doesn’t record steps or GPS itself; it reads them from whatever’s already tracking you (Health Connect on Android, or Fitbit/Garmin/Withings via their cloud APIs). So if Google Fit, Samsung Health, or your watch is counting your steps and logging workouts, NutriTrace will pull those numbers in and chart them alongside your nutrition.
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.
Hey, thanks for trying it out!
For things you don’t measure by weight (eggs being the classic example), the easiest path is to make a local entry once and then reuse it. A few ways to go about it.
The nutrition label on your egg carton is your friend here. It’ll show you the serving size, usually 1 large egg at around 50g, plus the full breakdown (calories, protein, fat, carbs). Tap the + on the Foods page, type those numbers in, set Serving size to 50 and Unit to “grams”. From then on, logging eggs is just typing “Quantity: 2” in the diary and the math takes care of itself.
For irregularly-sized stuff like apples or bananas, a kitchen scale is honestly the easiest path. A medium apple can swing anywhere from 130g to 220g, so weighing it once and typing the gram count gets you accurate numbers without needing a separate per-piece entry for every size.
One thing worth knowing about OFF and USDA results: the “100g” you see is just the per-100g nutrition density. That’s how those databases store everything, it’s a baseline reference, not a forced serving size. So you can either weigh your food and type the grams directly, or edit the entry to change the portion and unit (say to “1 piece” or “1 cup”) and the totals rescale.
Once you’ve dialed in a handful of items you eat regularly, day-to-day logging gets a lot faster. The new Favorites and Most Used sort in rc.19 will float your top items to the top of the Foods page automatically.
Just pushed rc.15 with the fix. Energy unit setting is now respected across the app, and the wizard auto-picks kJ for AU and NZ on first run.
Glad you’re enjoying it.
On the kJ, you’re right. The setting was being respected for goals and storage but a bunch of display spots still had kcal hardcoded. Just pushed the fix to dev and it’ll be in the next public release. Also added auto-detect so if your device locale is en-AU or en-NZ the wizard pre-selects kJ on first run, no toggle needed (but present now in settings).
On AI for coding, yes I utilize it. Claude Code to be specific. It makes me more efficient and helps lift the work I ship.
Will let you know when i push out the update, should be later today.
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.
Thank you! Enjoy the app!
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.