Understood. The public repo isn't where day-to-day work happens. Active development lives in a private dev repo and the public mirror gets squashed syncs at release time, which is why all you see are "chore: sync from lifttrace-dev (v1.0.0-rc.X)" entries.

Same pattern applies to my sister app NutriTrace. That public repo at TraceApps/nutritrace is at rc.42 right now, similar squashed-sync history, plus a couple of merged external PRs in the open, so the workflow isn't unique to one repo or trying to hide anything.

Reason for the split: the dev repo has a few files (internal planning docs, keystore config, that kind of thing) that aren't part of the shipped product, so I've been keeping it separate.

Thanks for taking the time to write this out and thank you for the feedback that helped improve the onboarding process.

I completely respect your preference (as well as the community's). LLMs definitely have their flaws, and they aren't for everyone. For me, AI acts as a thoroughly tested extension of my workflow rather than a shortcut, but I know that doesn't fit every project's philosophy.

I really appreciate your mature approach to the "No thank you" mindset. I hope you find a solution that works perfectly for your needs and aligns with your principles!

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.

Unfortunately there are no demo sites for either of the projects yet, that is planned for the future.

Appreciate the tip. Thanks!

Sorry to hear that. It's completely optional and you can go minimalistic with no banner if you so choose. Try it out and hopefully it works for you.

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.

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!