Photo credit: arstechnica.com

Strava Implements Major Changes to API, Affecting Third-Party Apps

Strava has announced significant updates to its API, emphasizing the importance of responsible AI usage and user control. The company expressed concerns that third-party developers may not adhere to these principles, prompting a reevaluation of how Strava’s data is accessed and utilized. The changes are expected to impact only a minimal number of applications on the Strava platform—less than 0.1 percent—while the majority of current use cases, such as coaching platforms that focus on user feedback, will remain unaffected.

In discussions about these changes, DC Rainmaker highlighted the challenges faced by many applications as they navigate the new restrictions. The simplest workaround for accessing fitness data would be for apps to directly obtain information from users; however, the reality is more complex. Most fitness devices, except for well-known models like Garmin that offer comprehensive APIs, typically rely on Strava as the primary method for transferring training data to other applications.

The recent adjustments to Strava’s API guidelines have introduced more stringent regulations, particularly regarding the handling of user data. Specifically, the updated agreements now stipulate that apps are prohibited from processing Strava data in an aggregated or de-identified manner for purposes such as analytics or customer insights. Ray Maker, the blogger behind the DC Rainmaker alias, noted that many training apps were caught off guard by this sudden policy shift, given that they were given only 30 days’ notice to adapt their applications.

Strava has also made it clear in its forum post in the Developers & API section that requests aimed at having Strava reverse its business decisions will not be entertained. This policy reinforces the company’s resolve to maintain tight control over its data ecosystem, prioritizing user security and responsible information management.

Source
arstechnica.com