Hi all,
I'm looking for advice from developers who have been through the athlete capacity increase process.
I run Fencingmetrics, a free web app for fencing clubs in France (results and rankings, training load, video analysis). Strava is one of the sources for training load: a fencer connects their account, and their activities feed a CTL / ATL / TSB model shown on their own dashboard.
The app is still on the default cap of one connected athlete. I submitted a capacity increase request on 31 August (client ID 257652) and haven't heard anything since — no acknowledgement, no refusal. Meanwhile, fencers who want to connect Strava can't, and I'm stuck on this part of the project.
Usage is light: one sync per athlete when they open their dashboard, at most every 12 hours, 30-day window, no background polling. "Powered by Strava" branding is in place, and the support page covers disconnection and data deletion.
A few questions for those who've been here:
What is a realistic response time these days? Is a month of silence normal, or a sign the request went nowhere?
Is there a better channel than the request form — a specific email, or something to include in the subject line?
Is there anything in the request itself that typically gets it stalled or bounced (screenshots, wording, the way the use case is described)?
Has anyone had a request rejected for showing derived training metrics to a coach, as opposed to raw activities? I'd rather adjust the product before resubmitting than get refused for that.
Any pointers appreciated — thanks.
Gaëtan
Fencingmetrics
https://fencingmetrics.com