Thanks for pointing this out. As I’ve mentioned before, I have always been transparent about utilizing AI assistance to help develop my apps. I wasn’t aware of the requirement to include a specific tag for them, but I appreciate you letting me know. I will make sure to include [AIP] in the title of my posts going forward.

Thanks for giving it a chance. Alot of time, effort, and testing went into this self hosted app. I am a longtime Mealie user and though its an absolutely great recipe manager, there were a few more things i wanted to see in an app like this, and thus CookTrace was born. Feel free to report any bugs or feature requests on the github page.

RC2 now includes improved import functionality. I believe this will address your concern above!

Genuinely useful feedback, thanks for taking the time. Walking through each:

Per-exercise sharing. Real gap. The exercises table is already structured cleanly enough to dump one as JSON; adding a “share this exercise” button that produces an importable file is small. The community-repo idea is good too: a separate awesome-lifttrace-exercises repo where people can drop contributions, and the in-app importer can read from a URL. Going on the roadmap.

Custom equipment + searchable tags. The schema already supports arbitrary equipment strings; the UI just defaults to a fixed list. Adding a “+” in the equipment picker plus a “what’s available today” filter chip set on the Exercises page is genuinely useful, especially for travel and home-gym use. Adding to the roadmap as a near-term candidate.

Per-exercise timer for time-based work. Real gap. The rest timer infrastructure exists but doesn’t currently cover “do this exercise for N seconds with a countdown and a cue.” That’s a meaningful addition for anyone doing carries, planks, isometrics, hangs, or hybrid stuff. Sharing the same audio + haptic plumbing as the rest timer keeps it cheap. Roadmapped.

Per-set / per-round rest in HIIT-style circuits. Currently rest is global with per-exercise memory, which doesn’t cover the “20s between reps, 2 minutes between rounds” pattern you described. That’s a structural change to how sets express rest. Going on the list to think through together with the time-based timer above, since they share infra.

Heart-rate data. The export direction you called out is the cheap win, and you’re right that PWA makes it easy. I’ll push a CSV export of the completed workout (sets, reps, weights, RPE, timestamps, rest durations) in a near term RC. That covers anyone who wants to feed an external analysis pipeline. Live HR ingestion from a BLE chest strap is the heavier direction and goes on the roadmap.

Thanks again for your valuable feedback. Appreciate the level of detail.

Thanks for highlighting the above:

Banner overlapping the H1 (“rcises”). This one I’m fixing structurally. The illustrated SVG banners across LiftTrace (and my other 2 Trace apps) are getting removed entirely. They were the single biggest source of layout fragility across viewport sizes, plus they were doing the project no favors aesthetically. In their place: the existing compact Gradient header stays as-is, and the “Animated” option becomes a subtly animated version of the same compact gradient (slow accent-hue drift, same height, no overlapping content). Three modes total: Animated, Gradient, Off, all sharing the same compact-header geometry. That removes a whole category of bugs and trims a real chunk of bespoke SVG maintenance.

Until that is released, you can flip your view to Settings → Appearance → Page Banners → Gradient (or Off) and the overlap should go away immediately.

Add button + exercise count missing on mobile. Real bug, haven’t pinned down the CSS yet but I’ll find it. The Exercises page action bar isn’t wrapping or relocating correctly at narrow widths.

Thanks again for bringing these to my attention.

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.