Giving zero days notice to your 3rd-party developers is one way to anger a relatively powerful bunch of your users. Many people will find today that their hobby/side-project is now dead in the water. I hope nobody was relying on any income from software using these APIs. But the 'best' bit: "We realize these changes could be especially challenging for some of you, so they’ll be non-breaking for 30 days, returning emp…
> Giving zero days notice to your 3rd-party developers is one way to anger a relatively powerful bunch of your users. I understand the frustration, but I also understand Strava's desire to rip the band-aid off and just shut it down. When it comes to free APIs, a sunsetting period gives a lot of people the idea that they can change the company's mind if they complain loudly enough, make enough noise on social media, o…
And I also entirely agree Strava needs to change. Their strategy has been non-existent for years. I was a paid subscriber for around 2 years. In that time I dutifully (naively) submitted bug reports and feature requests since I wasn't really getting much use out of the premium features but I wanted to support it. However, I never saw any value in the few changes they made so I figured my support was misplaced. I've been a happy free user ever since. I use their platform as a way bring together my data that's spread across 9 years and various Garmin, Wahoo and TomTom devices. I put quite a lot of value in that data and I trust Strava with it all. I definitely trust them less now. I think they could have handled this a lot better.