Feedback on an app we're creating

[hitmobi]

Me and my friend have been running a variation of 5/3/1 for over a year now and immediately I was annoyed by all the excel management. I tried using some of the apps out there but mostly it meant that i doubled my work by keeping up-to-date info in the excel and also in the app. So we are creating our own app.

We kind of want to create something cool that would have all the tools for programming a routine (any routine, not just 531) with progression rules and tracking it. It's completely free and currently in early beta - Hardy App. We will continue with this if it gets some feedback and traction.

Is this something any of you would use? If we're on the right track, would you mind giving us some feedback? If you wouldn't use this app, why?

 

[MindlessWork]

You just joined today to post this?

 

[hitmobi]

Yes, that kind of sucks, sry about that.

If this is against the rules, please remove the post.

 

[Eman]

It's not against the rules, I think it's really cool. It looks pretty complex but I'd like to study it a little more to see what all it has.

Why would you not charge money for this?

 

[hitmobi]

I appreciate that. Not charging money because there's a gazillion other apps out there but nothing really mainstream. And it seems that there's way too much noise that's targeted for beginners.

We just thought it would be cool to create something that is actually accepted as a good solution and a tool for experienced lifters. I know we have a long way to go. This is our hobby project.

 

[MindlessWork]

Sorry if I sounded rude…

 

[hitmobi]

Sorry if I sounded rude…

no worries, I get it... I would've probably answered the same way.

We have a small list of features that's feedback from our gym-friends but i thought it might be a good idea to get some ideas from a more public forum, but i agree that it's shitty to just go ahead and start posting links to some app .

 

[Eman]

- I think you could make "exercises" a subsection to muscle groups. Instead of choosing that I'm going to do RDLs in 12 weeks, it might be better to pick that I'm going to do hamstrings on that day in 12 weeks and then the week before or day of, decide to do RDLs. It allows more variance.

- To make it more strength specific, I think it would be nice to see the option to make different training blocks at my chosen length of time. Instead of a 12 week program, I'd like to choose a X week hypertrophy block, an X week strength block, an X week peaking block, etc.

- There should be a section next to the lifts to log what RPE the lift was.

- The term deload isn't really being used correctly... It's more of a back off or drop down set in PL terms. The term overload isn't really being used correctly either but it's a little closer. Overload is more the macro effect over a training block of increasing intensity and/or volume to create an adaptation. In your app, it's just increasing the weight on a subsequent set... So, kinda true but a little narrow.

- I think it would be interesting to add more MRV and MEV applications to it but that's probably going to get incredibly complicated. You'd also probably need a system to rate fatigue.

Anyways, that's just a few thoughts... I think it's a cool idea. I think, overall, it needs to be more specific and technical while staying user friendly but I don't think you're on the wrong track with it being in beta.

 

[Test_Subject]

Looks very cool.

I like the progression based on AMRAP functionality. I’ve used that method of auto regulation in the past to excellent effect.

I agree with Eman, a system to rate fatigue/fatigue accumulation would be incredibly useful.

 

[hitmobi]

This is some excellent feedback.

- exercises to muscle groups.

This is something we've also discussed but haven't really come up with a good technical plan

- time-blocks for workouts

This is coming. We noticed that workouts are not enough to organise a routine anyway. It almost always results in workout names being something like "Week 2 Workout A"

- RPE

RPE/RIR tracking and also RPE autoregulation rules are in the works already

- Deload/Overload

Noted. Currently the way it works is that it will deload the % from the TM value after the workout is done. And it will add weight to the TM once the workout is done.

so my bench TM might be 250 lbs. My routine has a rule to deload 10% if i fail any of the sets. after that workout i will end up with a bench TM of 225. All the sets can be calculated as a % of the TM. Same goes for overloading.

The thing that might be confusing is that you might have an overload rule for a specific set. What this actually means is that after the workout is completed, depending on how many reps you could pull off on the set which had that rule, your TM will be increased by x lbs.

The actual plan was to have several options how to de-/overload. Right now it's just reduced weight, but we want to tie that in with reps/sets somehow.

- MRV/MEV.

That's an interesting idea, thank you!

Currently the usage of Training Max is not exactly accurate as well. The place where you can enter TM % will soon consist of a couple of different options:

TM / empty / 1RM% (coming) / RPE (coming)

This is basically the suggested weight. If it's not specified it will suggest the weight used on your previous session. for RPE, it will use an e1RM.

Thank you for the detailed response, that was very helpful!

 

[Eman]

Deload/Overload

Noted. Currently the way it works is that it will deload the % from the TM value after the workout is done. And it will add weight to the TM once the workout is done.

so my bench TM might be 250 lbs. My routine has a rule to deload 10% if i fail any of the sets. after that workout i will end up with a bench TM of 225. All the sets can be calculated as a % of the TM. Same goes for overloading.

The thing that might be confusing is that you might have an overload rule for a specific set. What this actually means is that after the workout is completed, depending on how many reps you could pull off on the set which had that rule, your TM will be increased by x lbs.

Yeah I get it, and I agree with the principal to a certain extent... I just don't agree with the terminology. Overload and deload mean something different in the PL dictionary.

Also, was just thinking that the original juggernaut method and subsequent variations of it would work well with this format of an app... It's kind of an expanded version of 531.

 

[Worf]

- I think you could make "exercises" a subsection to muscle groups. Instead of choosing that I'm going to do RDLs in 12 weeks, it might be better to pick that I'm going to do hamstrings on that day in 12 weeks and then the week before or day of, decide to do RDLs. It allows more variance.

- To make it more strength specific, I think it would be nice to see the option to make different training blocks at my chosen length of time. Instead of a 12 week program, I'd like to choose a X week hypertrophy block, an X week strength block, an X week peaking block, etc.

- There should be a section next to the lifts to log what RPE the lift was.

- The term deload isn't really being used correctly... It's more of a back off or drop down set in PL terms. The term overload isn't really being used correctly either but it's a little closer. Overload is more the macro effect over a training block of increasing intensity and/or volume to create an adaptation. In your app, it's just increasing the weight on a subsequent set... So, kinda true but a little narrow.

- I think it would be interesting to add more MRV and MEV applications to it but that's probably going to get incredibly complicated. You'd also probably need a system to rate fatigue.

Anyways, that's just a few thoughts... I think it's a cool idea. I think, overall, it needs to be more specific and technical while staying user friendly but I don't think you're on the wrong track with it being in beta.

This is excellent feedback. I have nothing to say now.lol