I still develop optional 3rd party add ons for other vendors, but I will never ever again rely on a single vendor 'lock in' with any of my apps.
I think this is Relive's misstep, though time will tell. They have all of the major apps as part of their API now, but they've also started directly competing with these app, giving the app creators an incentive to compete right back.
I do have a dog in this fight as the founder of https://ayvri.com which creates interactive 3D videos, used for sports and other domains.
And while less developers will be incentivized to use the API seeing this behavior, very few can actually afford to launch a proper competitor. So plenty will continue do develop with this philosophy in mind, knowing that if it's successful they will be cut off but hoping they make enough and then just pivot to the next thing.
What's funny is that Relive doesn't have to depend on Strava. When I knew about the service months ago I signed up expecting to be able to upload a GPX file and get a video back. But no, they want to get those files via Strava (or other cloud services) so I closed my account.
I understand that 1) it removes a lot of friction, 2) it's what the users of Strava are used to and 3) they can get all those juicy data instead of a few files. However it's risky and Strava eventually cut them off.
I wonder if they'll implement a file upload, just live with the other services, or close the business.
Ostensibly the reason was due to competing with a feature that Strava intend to build themselves (“thanks for proving the demand”). This was back in March, I’ve since been informed that access won’t ever be reinstated so have open sourced the code [2].
Lesson learnt, don’t depend entirely on third party APIs.
[1] https://segmentchallenge.com/
[2] https://github.com/slashdotdash/segment-challenge