Yes, sharing workouts is on the roadmap. Users will be able to create routines, save them, and share them with others (even with public links) as the previous workout-lol project.

As for API integrations (Strava, Garmin, HealthKit, etc.) definitely something I’m open to.

Curious to know : what kind of data would you want to sync or pull in? Workouts? Step counts? Heart rate zones?

I’m working on stabilizing it and will have a fix in the next minutes / hour

Appreciate you testing it out! thanks again.

Why are compound lifts in the middle of the workout and why am I doing three different types of chin ups? There are also no reps / sets calculated nor are there 1RM percentages for weight.

Bro splits are some of the lowest quality routines you can use and this somehow makes them worse. You could replace all of this, remove the bells and whistles, and create a bare bones PPL app that determines exercises based on equipment available and it would be light years better than this.

Btw I totally agree: once you’ve been training a while, the only thing that really matters is tracking your progress and showing up consistently (or "mental" side in my case, i do not train anymore for performances).

Good news : saving + tracking routines over time is in the roadmap.

That's why the architecture of the "workout session" is the part that is the most different from the old app.

I want users to create, reuse, share, analyse and evolve their own training blocks with minimal friction.

Would love to hear how you handled that in your own PWA sounds like we've walked similar paths :)

I wanted to make sure everything is legally safe and not just scraped or reused without rights.

Producing proper 3D exercise videos is actually VERY expensive we’re talking €10–20 per animation, or thousands of euros per month if you go through a good/high quality API provider. That’s why it's such a tough space for open-source tools to compete in.

Long-term, I'd love to help build a community-driven, open-licensed library of movement animations but until then, this partnership was the best balance between cost, legality, and quality.

Thanks for raising it

Bcs a lot of beginners don’t know what to do with certain equipment, but they do know what they want to train.

That said, I’ll maybe make both paths easier and let users toggle between them!

PR ares welcome

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.

I’d love to see your ideas make it into Workout.cool!!

Let me know if you need help porting the PRs îll support and merge contributions quickly.

I'm already planning to make the filters optional, and add things like "beginner-friendly", "popular exercises", "calisthetics", ...

Thanks for pointing it out

sent 15 emails over 9 months to the new owner, offering to help or even take over the repo but i had no replies.

Issues and PRs were ignored(you juste have to see the issues section of the report). Rebuilding from scratch was the only way to fix the licensing & continue the project i guess

For this, i rebuilt the entire dataset from scratch with a partner to avoid any licensing ambiguity (especially with videos), and to have full control over attributes, translations, etc.

But I absolutely love seeing other open projects in this space and I'd be happy to explore possible synergies if it can help both communities.

DMs open !

For the sell process, like with any open-source project whether it's an NPM package or anything else, there are no absolute guarantees... that's just the nature of open ecosystems...

But I've built Workout.cool with transparency in mind, no hidden business model, and self-hostable.

Just what I can tell you is this :

I've been passionate about fitness my whole life let's say. I started sports at 3 years old, and I've been into strength training for over 15 years.

I didn't build this to make money. I built it because I genuinely care and because I see more and more people missing out on the benefits of training, often overwhelmed by complexity, closed ecosystems, or paywalled apps, including people close to me, like my sister.

Hope that my reply counts for something...

I’m only embedding YouTube videos now, all with permission or public use from the original author.

If you’re into 3D or want to help create open assets, I’d love to chat!

You have no idea how happy I was when I saw your name pop up ahahha

Yeah, no luck either. It really broke my heart to see the project stall like that.

That's what pushed me to rebuild everything, keeping the same open spirit you had from day one.

Thanks a lot for the kind words about the UI it means a lot coming from you.

And if you ever feel like jumping back in (I totally get that it might be tricky, especially since you sold the original project and this one is so close) but you’d always be welcome.

Your input, ideas, or even just your presence would mean a lot !

Cheers !

I’ve been working on an automated calendar scheduling api that integrates with Apple CalDAV (iCal) that lets you schedule your life around goals (it uses Google OrTools to solve a great big CP-SAT constraint model blazing fast, a year in under 5 seconds), along with meal planning around macro goals. I knew I wanted to integrate a workout/training plan system but had no idea what component I’d end up using.

Now I know! Thanks for building this project.

Bcs It's true that most beginners tend to think in terms of "full body" or "upper body" rather than doing a structured split let's say. They don’t usually say "I want to train my posterior deltoids and lats" lol

I love the idea of filtering exercises by gym type or gym but can be hard to handle for "private" gyms and will also need some kind of moderation... Could work for large branded gyms though.

The current onboarding assumes a bit too much knowledge up front (didn't expect that).

Bcs yeah, most beginners don’t think in terms of "rear delts" or "lats" they just want to "get stronger", feel better i guess

I'll be adding:

Optional muscle selection (or skipping it entirely)

Beginner-friendly presets like "Full Body", "Upper Body", etc.

OR suggested muscle groups with labels like "Chest + Triceps (Push)" / back-biceps... etc.

The goal is definitely not to make you study anatomy before you can get started lol and your feedback helps to build a smoother, more welcoming flow

Thanks again for that ! And welcome to the fitness journey! Hope to see you soon

The idea of sharing your protocol (or full workout templates) is something I'm definitly building into Workout.cool as well. Users will be able to create routines, save them, and share them publicly (or privately) super useful for friends, coaches, or even just "community inspiration"?.

If you ever feel like revisiting your old project or contributing some ideas/features, I'd love to hear more!

Adding it to your home screen is exactly the right move ahah i've done the same

Would love to hear your thoughts after a week of usage feel free to drop feedback anytime, i will add a button in the topbar called "Feedback" by the end of the week.

Thanks !

And yes I'd absolutely be interested in discussing a UI + flow for a self-adjusting progression system like that. Yeah. Let's talk about that, drop me a DM? I can think about some (ugly) alhorithm first

I choose to keep a server backend for a few key reasons:

- Centralized updates to the exercise database (videos, translations, attributes) without shipping a new frontend each time. (The goal is to have 5 to 10 new exercices per week)

- The ability to offer shared features like community workouts, saved routines, and (eventually) syncing across devices, etC...

Room to grow into more advanced features like progression tracking, public/privates APIs (strava, garmin, ...), and integrations all of which are much harder to manage purely client-side in my humble opinion.

But you do need to have an active Apple Developer account (which is $99/year) to set it up and maintain it.