u/Acceptable_Cry_822

Hey Bevel Team,

Great work on the 3.0 release. I’ve been using Bevel every day to analyze my trends, recovery, and to create/revise cardio and weightlifting plans for the week, and it’s been great.

That said, I have a few pieces of feedback that I think would make the app even better:

1. Give Bevel AI the ability to edit workout templates: Every morning, I ask Bevel to look at my metrics and update my workout plan to maintain progressive overload or deload if needed. While it can create workout templates based on my historical patterns, it still can’t edit old templates. So it ends up creating a new template every time, which becomes a bit cumbersome. It would be great if it could update an existing template with new weights, reps, and sets instead.
2. Add a tab for historical weights lifted / reps / sets: Bevel currently tracks total volume lifted, but it doesn’t offer that level of detail, except for the last recorded workout. It would be great to have a separate tab that tracks historical progression so both I and Bevel AI can use it to suggest next week’s workout plan.
3. Make Bevel AI responses more consistent across chats: I’ve noticed that Bevel’s recommendations sometimes change across different chats. I’ve reported some of these instances already, but it would be great to have more consistency and alignment between responses.

Also, I’ve already requested support for reading Running Dynamics from Apple Watch data, so Bevel can provide guidance on running form and potentially alert users to incorrect form that may lead to injuries.

Thanks for all the development work on the app. It’s been very helpful to me, and it’s great to see it keep getting better every day.

I’ve realized there’s a massive missing piece in how Bevel analyzes our runs: Running Dynamics (Cadence, Ground Contact Time, and Vertical Oscillation).

Right now, Bevel is great at the what (our scores), but for runners, these dynamics explain the how. I’ve found that many “fitness drops” or “Strain spikes” are actually just mechanical inefficiency, not a loss of cardiovascular fitness.

Why we need this feature enabled:

1. The Efficiency Gap: When Ground Contact Time increases and Cadence drops (plodding), our heart rate spikes even at a slow pace. Bevel sees the high HR vs. slow speed and estimates a lower VO2 Max. Without seeing the dynamics, users might think they’re losing fitness when they just have “heavy” form.
2. Form vs. Fatigue: High “bounce” (Vertical Oscillation) is a massive energy leak and injury risk. Bevel should monitor this alongside Strain to flag when our form is breaking down before we overtrain.
3. Actionable Coaching: Bevel Intelligence could proactively spot these trends—letting us know if a bad VO2 Max day was actually just a “form day” due to low turnover or fatigue.

The Request: Please enable the import of Apple Health Running Dynamics into the workout summary and correlate them with our Strain and VO2 Max trends. The data is already there—we just need Bevel to use it!