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
It might seem odd for one app's users to fume over an API, but at the heart of the matter is the inherent messiness of fitness data. Mastodon: @evan@cosocial.ca , @cdamian@rls.social , @lackattack@mastodon.social , and @vicmsong@mastodon.social Mastodon: Evan Prodromou / @evan@cosocial.ca : @Techmeme — Run tracking is one of the example problems in my ActivityPub book. I think we need to start working on this problem. Christof Damian / @cdamian@rls.social : Strava is trying everything they can to make me cancel my subscription. — My main use case for Strava is as a data hub for all kinds of apps. They seemed to have removed this feature now. — https://www.dcrainmaker.com/ ... #Strava #Cycling #biketooter @dcrainmaker Chris Actually / @lackattack@mastodon.social : #strava, this is not how I expected to be rewarded for being a subscriber from nearly day one. Please pump the brakes on this speedrun to enshittification, dorks. Thanks — #fitness #cycling #outside — https://www.theverge.com/... Victoria Song / @vicmsong@mastodon.social : Wild when you think about how people use Strava to integrate data across other fitness apps, wearables, and connected fitness equipment. — https://www.theverge.com/...
Context & Ripple Effects
Strava’s restrictions arrive just after it [[a:879493|barred third parties from using Strava data in AI models and from displaying one user’s data to another]], extending its control from AI use to the broader ways activity records move between services.
The related coverage traces a continuing access-tightening arc: Strava later [[a:1170048|put developer API access behind a monthly fee and required authentication for public profiles]] in response to AI scraping concerns. This makes the integration dispute a question of who can assemble fitness data, not merely a technical API change.
First-order effects
- Third-party fitness apps and wearable services face new limits on importing, combining, or presenting Strava activity data, making all-in-one fitness views less complete for shared users.
- Users whose routines depend on Strava as a data hub must contend with more fragmented records and reduced functionality in connected services.
Second-order effects
- Developers that built cross-service dashboards or social features around Strava data will need to redesign workflows, narrow features, or seek alternative data sources.
- Direct integrations become more strategically valuable than broadly reusable API access, increasing the importance of platform-by-platform partnerships for fitness services.
Third-order effects
- If this pattern persists, fitness-data interoperability will increasingly be governed by platform terms, authentication, and commercial access rather than by user expectations of portable activity histories.
- Pressure may grow for user-controlled data portability, but the corpus shows platforms balancing that demand against concerns over AI reuse and scraping.
The trend: Fitness platforms are turning APIs from open connective tissue into managed control points for data rights, AI exposure, and monetization.