strive.ai’s vision was founded on two key pillars: Enhance the Strava Experience and Enhance Athlete Performance through advanced analytics. Impactful data science requires enough data to be successful so what we did to start was offer some interesting features that created
Stryd update
Several weeks back I noticed that my runs were no longer getting synced to strive.ai with run power. Turns out Strava made a change on their end to remove the power stream from run activities as it was impacting their
Segment PR today?
Imagine you wake up and your mobile device has a strive.ai notification suggesting you should hit 3 of your starred segments that afternoon because it’s predicted you have a 90% probability of achieving a Strava PR based on loads of
Next Generation Features
Super excited to start laying down some advanced features to enhance your Strava experience. The key to any good AI is the data so over the next 6-8 weeks we’re enriching our data to unlock exciting new algorithms that we
Athlete Clusters
One of the initial visions for strive.ai was to offer features that help athletes find training partners with similar characteristics. We tried one approach in the early beta that clustered athletes based on starred segment completion time. This approach had “mixed
Run Power and Best Efforts
Today we introduced improved support for runners in strive.ai we eluded to here. We’ve made the following changes: Removed the Run Pace threshold type Introduced Pace Best Efforts for 400, 800, 1600, 5K and 10K distances (aged over 8 weeks
Support for Runners
Admittedly, we’ve started out with a focus on cycling with power. We attempted to mix in run pace thresholds using the same time duration concept [1, 5, 20, 60] as we do for heart rate and power. We learned
Initial Beta
Our first post on strive.ai! We’ve been focused on the engineering and data science of this application for the past 6 months and I’m excited to see it launched to a broader beta to test the features and infrastructure at a