Comment - FBXL Lotide

Comment on LiftTrace v1.0.0-rc.5: Scheduled Automatic Backups + Raspberry Pi support

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.

original

Sort:hotnew top

TraceApps@lemmy.world ⁨2⁩ ⁨days⁩ ago
should now be addressed in latest RC6.

original
curbstickle@anarchist.nexus ⁨1⁩ ⁨week⁩ ago
I like the differentiation, but yeah it is going to make things much more complicated. Maybe icon color/theme color set per category for the same (but much easier) level of visible differentiation?

To be clear the add button and count are present, just hidden by the svg in the banner.

Right now creating some json of exercises I do to test import, manual creation after that, and (as long as the kids cooperate) I’ll get a workout in for a test too

original
curbstickle@anarchist.nexus ⁨1⁩ ⁨week⁩ ago
Ok, I’ve got some utility/usability comments:

Exercise Creation:

Both options (manually creating and json import) work without issue

It may be handy to create some kind of per-exercise export specifically to be shared to others. I’m thinking since its just json it could live in a repo on a per exercise basis, right next to the app itself (not necessarily the same repo).

It would be good to have an option to either add your own equipment type or allow a searchable tag. I sometimes make a workout on the fly based on whats available at the gym (like if I’m traveling), and this would help for quick searches. I also have some equipment here at home that I use that would be handy to include or exclude (like if my kids are using the slackboard).

Workout:

The overall timer is good, but a per exercise timer inside that would be great along with a settable rest time. If I’m doing 2 minutes of weighted carries for example, I’d want to start the timer, get a countdown, then get a beep or something when the timer hits. That should be settable for the exercise.

For a settable rest timer, if the exercise itself has a timer, then a “rest” could just be an exercise with a custom timer. This would be per rest settable, not overall. For example, if I’m doing an HIIT circuit I may want a 20s rest between exercises, but then at the end I may want a 2 minute timer to run before starting another round.

Ideally I’d want to also grab HR data off my chest strap sensor, whether I’m getting it in-app during the session or after. I’ve made a couple of apps to pull that data in (entirely different purpose btw), its not too bad for devices like polar with a clean api, but you could also do something with an import possibly. It would be that or the other way around, allow the session data to be available for export, which would be drastically easier as a PWA. Since this is more structured indoor training/logging, a timestamped csv is probably best, though json would be fine too.

I know you’re not looking to add features in when you’re at RC, just some general feedback on what I like to see/do
original
- TraceApps@lemmy.world ⁨1⁩ ⁨week⁩ ago
  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.
  
  original