Honestly I've never created a donation button before, haha - I've just added a donation link (via wise) to the README and to the settings page in the app.

Again, appreciate the support!

Not sure it's above board to scrape the site for workouts though - plus I wouldn't want to take away from their ad revenue.

I started building this app out initially to see how far I could get in a short space of time. It's still quite bare but it shouldn't be difficult to flesh out from here.

For me, it's more about the fun of making a working thing and then sharing that with others. If people contribute that would make my year, but it's rewarding enough to know that people are using it.

I'd like to expand on the exercise details page, but not looking to profit so licensing resources is off the table. Cloud sync is an interesting one because I'm trying to keep this free. I was hoping to offer users the choice of sync solutions (Google Drive, for instance).

I was thinking of adding in workout templates and maybe even figure out progressive overload or routines like 5-3-1.

Someone earlier made a reference to another app that lets you write/share scripts that can be used to design custom programs - which is very interesting. Being web based, custom programs could be written in JavaScript and `eval`'d in a sandbox - allowing for a similar experience.

I'm going to be adding in workout templates and maybe even auto-workouts (like auto progressive overload or routines like 5-3-1).

Another commenter mentioned an app that lets people write scripts to program custom routines. That sounds super interesting and a great way to share routines. I'm thinking of writing an engine for custom routines then use that to program some default ones.

As an aside, the coolest benefit I've gotten from gym logging apps is charts. It's interesting to see my session volume, 1RM and heaviest lifts go up over time. It helps me plan my progressive overload schedule and notice when I'm plateauing/have to up the calories.

Plus it's super rewarding looking at the chart from 4 years ago and seeing how far I've come.

But you're completely right about notes on finding ways to ergonomically record variation.

If you have any ideas, drop them in the issues

CI/CD is all set up so anything merged to `main` get published straight away, happy to include PRs - doesn't have to be perfect, can always fix it up after.

A few low hanging fruit pieces would be a "details" page for exercises (e.g. "/exercises/Bench Press").

I've also gotta set up the "measure" page for tracking bodyweight - but I am working on adding sqlite to the client so this sort of stuff (like charts) is easier to do.

The first was much like this one with browser storage. There was a bug in Chrome that wiped out the persisted storage of all websites which nuked all of my records

https://www.bbc.com/news/technology-50809216

I tried rewriting it in React because it was the new hotness but spent so much time worried about component rendering cycles, hooks, state that just ended up distracting me away from time on the UI and UX. It was fast (like it matters), but ugly.

As for data sync, I've just added SQLite on the client and going through the painful process of normalizing the records.

My idea is, users will be able to supply a Turso API key and the app can sync against that, keeping a local copy of the data - eventually consistent.

I'll probably do something dumb like keep a timestamp of the last change and push/pull data periodically.

It only works because it's 1 person using the app and no one trains with two phones