Hi all,
I'm the developer of OpenSwim Forecast, an open water swimming conditions and coaching app that integrates with Strava to read and visualize swim activities (HR zones, laps, route maps, device water temperature). It's live on the iOS App Store with an Android build in progress, and has an active user base syncing swims via Strava.
I've submitted requests through the developer support process for an athlete count limit increase and a rate limit increase for production use (tickets #14733, #14559, #15019). The athlete cap is currently the practical blocker, new users hit the limit and can't connect.
A couple of questions for anyone who's been through this:
1. Is there a typical timeline for production access / athlete cap reviews, or a way to tell whether a ticket is actively in the queue versus waiting on something from my side?
2. Is there specific information reviewers like to see up front to speed things along — privacy policy, brand-compliance screenshots, a demo of where Strava data appears in the app? I have all of it ready and would rather include it proactively than wait for a request.
The integration follows the brand guidelines ("Powered by Strava" attribution, official logo, "View on Strava" deep links) and only requests activity:read_all scope. Happy to share more detail if it's useful.
Thanks for any pointers.