What to do with the Strava implementation #64
JaapvanEkris
started this conversation in
Polls
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Now that our file creation is reasonably complete, I'm looking at what to do with these files. Lars has created a Strava integration 3 years ago as part of 0.8.2, which I maintained since then. But that remained the only integration, as Strava used to be interesting as a single portal to many other analysis platforms, greatly increasing data portability for users in a single integration.
However, today Strava announced these platforms aren't allowed to analyse data anymore, greatly limiting your use of your own data. RowsAndAll.com is one of the affected parties, which can't do analysis on rowing data obtained via Strava, nor can coaches (which you pay to help you) see your data anymore. This renders Strava useless as a conduit. In all honesty, I have strong issues with their approach, as it goes against OpenRowingMonitor's founding principle that your data must be as free and accessible for you as you want it to be. I think that should be the leading principle for the entire sport metrics ecosystem.
Some things also bother me from a technical perspective, as I see OpenRowingMonitor somehow decides that the user gets a question, and that triggers the Strava upload in a complex interaction between frontend and backend. That implementation doesn't fit well with our new technical architecture, and it will never work on headless units. Given that Strava uses Oauth2 authentication, I have concerns it will ever fit well in a way that Oauth2 is intended while fitting our intended use cases and architecture.
I also see what other (free!) data analysis platforms, Intervals.icu and RowsAndAll being the primary ones, are doing. Automatic uploads are much simpler, their analysis is far superior to Strava's (especially for rowing) and they do respect the user's desire to share and analyse data freely across many platforms. I personally think eliminating Strava's role as a conduit here would benefit users, as it puts users firmly in control of who sees their data, and not a vague social media company that struck gold.
Personally, as a daily rower on EXR, I do post to Strava for social reasons, but I use EXR to connect to Strava as it also uploads nice pictures and virtual geodata. This, combined with Strava's diminished role as (conduit to) a data analysis platform, would make direct Strava integration for OpenRowingMonitor less relevant.
So my key question is if we want to keep Strava integration and how elaborate should it be?
5 votes ·
Beta Was this translation helpful? Give feedback.
All reactions