Skip to main content

Hello, I have an application that is used to upload gpx to strava from usb cable connected devices,

it can also view activities general details - mostly track and map. It does not duplicate any strava functionality besides uploading gpx via API. It is a desktop app with 1 user only using his own api-application. I was autidted by the team, i got all the required stuff in the app (logos, strava promotion, links to activities ‘view on strava’ etc) and I got all the blessings, plus request limits set for the app. I am happy with that. But my question is - if I make the app public, and some people will download it and use as their private api applications, will that be a concern for me, or just they need to setup their api-app and use it. It is a one-user desktop app. Hope it sounds reasonable 😉 if not I can give more details to strava team. 

My take (as a developer):

As long as you aren’t including your API key in the public release, I don’t see why it would be an issue. Each person using your app will need to use their own private key to configure the app, so they will be using their own limits. It’s as if they developed the app themselves in what Strava calls ‘single player mode.’ It would be up to each individual user to manage requests to keep within their API limit, though from what you’ve described that shouldn’t be a problem.

Thanks, yep that’s my understanding as well, just thought someone from strava team would confirm that (not that your reflection on this is not appreciated!, thanks)

Reply


Terms & ConditionsCookie settings