Strava's new API rules for third parties will make it harder for users across dozens of fitness apps and wearables to integrate their fitness data in one place
Run tracking is one of the example problems in my ActivityPub book. I think we need to start working on this problem.
Context & Ripple Effects
Strava's rule change follows its earlier ban on third parties using Strava data in AI models or similar apps. Together, the moves narrow how external services can reuse activity data and present it to other users.
The issue matters because Strava sits among many fitness apps and wearables: limits at this API layer can determine whether a user can maintain a unified view of their activity across products.
First-order effects
- Third-party fitness apps and wearable integrations must revise or curtail features that consolidate or display Strava-derived activity data.
- Users who rely on cross-app dashboards face more fragmented fitness histories and fewer ways to share Strava data through outside services.
Second-order effects
- Developers building aggregation and social features have less reason to depend on Strava data, while platforms that control both tracking and presentation gain an advantage.
- The restrictions make API terms—not just technical compatibility—a central constraint on fitness-data interoperability and product design.
Third-order effects
- If other fitness platforms adopt similarly restrictive terms, personal activity data may become increasingly siloed inside the services that collect it rather than portable across a user’s preferred tools.
- The pattern also sharpens the trade-off between protecting platform data from AI reuse and preserving an ecosystem of interoperable third-party experiences.
The trend: Fitness platforms are treating API access and data reuse as strategic control points, especially as AI-driven uses make shared activity data more valuable and harder to govern.