Over the next 9 months, I sent 15 emails to try to save it : no replies. Feature requests & issues were ignored. The community was left with a "broken" tool let's say.
I couldn't just let it die So I built the new version from scratch with the same open-source spirit, but a better architecture long-term vision, more features and no license problems.
It's called : Workout.cool (https://workout.cool). What it offers: 100% open-source, MIT-licensed - 1200+ exercises (with videos, attributes, translations) - Progress tracking - Multilingual-ready - Self-hostable
I'm not doing this for money. I'm doing it because I believe in open fitness tools, and I’ve been passionate about strength training for 15+ years.
If this resonates with you, feel free to: - Star the repo - Share with fitness/tech friends - Suggest features - Contribute code/design/docs
Together, we can build the open-source fitness platform we all wanted to easily build a workout routine and get in shape
Website: https://workout.cool GitHub: https://github.com/Snouzy/workout-cool
As someone who doesn't know much about working out or what exercises to do this sounds like a good app. I need help, but picking based on muscles is off. My thought and goals are not by muscle group, but losing weight or getting more toned.
Conversely, someone who knows what muscle groups they want to target, probably already has some sense of the exercises to target and thus less likely to need the app.
Personally, as someone that exercises but not for aesthetics, I think of strength training in terms of movements not muscles worked. So I'm thinking "press, pull, squat, hinge" not "chest, lats, glutes". Thinking of function and then doing fundamental compound movements just makes more sense to me, although I do sometimes need to hone in on a muscle for functional reasons -- like targeting the glute medius for opening up my kicks in my Muay Thai training.
Neither is more correct, they're just different approaches.
Also - for most people who had accidents they'd probably rather click on "Dislocated Kneecap" and then have the software suggest exercises to help with that condition - vs needing to bring that knowledge to the app.
The goal is to make the app more welcoming by offering goal-based (or filters,let's see) entry points like "fat loss" "beginner full-body" or "3x/week routine" and not require anatomy knowledge to get started.
The muscle filter will just be one of many ways to browse, not a gatekeeper i guess. Thanks a lot for highlighting this!