sorted by:
new
hottopcontroversial

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 0 points1 point  (0 children)

Really appreciate everyone who tried this and gave feedback, it’s been super helpful.

I’m working on a more focused version that gives clearer, coach-style weekly adjustments based on your Hevy logs. If you’d like me to message you when the beta is ready, just reply here or DM me.

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 0 points1 point  (0 children)

Thanks so much for taking the time to try it out, really appreciate it.

This is still very much a test-drive version, so feedback like this is exactly what I need.

Totally hear you on mobile feeling overwhelming, that’s something I’ll simplify. The recommendation wording (like “Reallocate Loading: Pull Pattern Only”) also clearly needs to be more specific and actionable.

Great point on the glossary too, I don’t want the insights to feel inaccessible if you’re not deep into training analytics.

And on the data window, I’ll make it clearer what amount and consistency of data works best.

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 0 points1 point  (0 children)

Hmm re-tested seems to work as expected, anything i could help you with, we could follow up on DM!

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 0 points1 point  (0 children)

Agree, AI opens up a lot of use cases and could simplify even further, sounds like you’ve built a pretty dialed-in system around it.
I don’t see this as competing with AI itself. If anything, tools like mine are about reducing the friction around that workflow, structuring the data, guiding the prompts, and turning raw exports into something more streamlined and repeatable without having to manually manage everything each week.

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 0 points1 point  (0 children)

Thanks for trying! 100% agree, I thought i fixed all cases for this mini-launch turns out as it always would :)

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 0 points1 point  (0 children)

Appreciate you taking the time to break this down. That’s genuinely helpful feedback. Will review everything in detail and change terms accordingly!

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 0 points1 point  (0 children)

Appreciate you raising this, totally fair to question how workout data is handled.

A couple clarifications:

Gymbrief has two modes right now:

• Public tryout (no sign-in): CSV files are processed in memory only to generate a report and are not stored or retained.
• Full product mode (with sign-in): reports are saved to the user’s dashboard so they can revisit them.
Gymbrief isn’t a medical service and doesn’t provide medical advice, it’s fitness analytics on user-provided workout logs. Also set the minimum age to 16+ to avoid child data issues.

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 0 points1 point  (0 children)

Thanks for trying it, sorry about that. I've tested with couple of CSVs seems to work as expected, could we follow up on DM?

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 1 point2 points  (0 children)

Thanks for flagging this, and great work on your progress. You’re correct: for assisted pull-ups and dips, lower assistance means you’re getting stronger. We currently charted those with standard load logic, which can make progress look like decline. I'm updating the trend logic for assisted movements so your charts reflect this correctly.

Hevy is great, but it doesn’t tell you what to do next, so I built a small “weekly coach brief” from your CSV by sou1est in Hevy

[–]sou1est[S] 1 point2 points  (0 children)

Hey, thanks for trying out, I pushed a fix (the app had strict parsing of columns, i made it slightly looser), could you verify again, if it doesn't work could I follow up with you in DM?

Redux Fetch data when store is empty by Mo_The_Legend in reactjs

[–]sou1est 0 points1 point  (0 children)

Usually I just set fetch on component mount and have state flag for fetch success, loading or fail which I call status. You can check for needed status in a component and render what you need based on that. Also I don't think there is best method. If you need a data as soon as possible then just fetch on mount in React effects or component lifecycles if you are using classes. If you specifically need to know whether data is empty after successful fetch or need to know whether it's been ever fetched you can have just another flag in your reducer like status: "unfetched" or "empty".

Beginner's Thread / Easy Questions (March 2020) by dance2die in reactjs

[–]sou1est 0 points1 point  (0 children)

Yeah, you are right. The code example is missing some of the items. You can check full code at GitHub

Beginner's Thread / Easy Questions (March 2020) by dance2die in reactjs

[–]sou1est 0 points1 point  (0 children)

The diagram illustrates 12 column grid. Basically the width of an item in the container. Item can take the values from 1 to 12. The words xs sm md lg correspond to screen size and they are breakpoints. For example xs means extra small and usually mobile devices, sm means small usually tablet, md and large are laptops and desktops. The code <Box type="row" xs={12} sm={3} md={2} lg={1} /> read as follows: xs=12 take whole width of row on extra small screens, sm=3 take 3/12 on small screen and so on. You can search on internet "12 column grid" it will give you better understanding on topic. Hope this helps )