Stryd S+ app
-
I want RE during the run, not after. During a warmup at flat constant power. Then RE it would tell me if I should take a longer run or take it easy and do recovery run.
-
@lexterm77 that’s cool. Stryd doesn’t currently have such metric, hopefully there’ll be a end-user S+ editor of sorts
-
@herlas so the official S+ Stryd app will not have metrics that Stryd doesn’t have, but Speed/Power is already possible to compute right now. I can test the idea and tell Suunto there is some interest in this.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
Or have s+ app where we can enter our own equations and play with them
-
@isazi right, having STRYD metrics on S+ screen is fine and people have requested, but IMHO for me I use/check them for post analysis and that I already do on powercenter, rather than on the fly. Do you know if there’s another benefit from the STRYD S+ app? Like i.e. minimizing the 7 sec gap to receive power on our Suunto?
Things like STRYD structured workouts or enabling the new running profiles from the new STRYD sounds too tempting to have on our Suunto watch
Either way, will still be happy to see the integration happen when the STRYD S+ comes out
-
@herlas I think the advantage for users will be seeing some metrics in real time, and have them also saved in SA for analysis.
I will implement the efficiency S+ app during Christmas holidays just for fun.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi just to clarify, you have an acces to API, but regular users don’t? As there any chance to get an acces if we contact support or sb else? No need for a fancy interface, raw code will do just fine.
-
@DMytro not sure if the plan is to open access to users, or just third-party companies working with Suunto. I have access to the development environment (like others, also on this forum) mostly for testing, but I can develop apps (I developed few basic ones for fun).
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi no fair!
-
@DMytro Indeed. I’m starting a public protest in my town! Dev tools for *
-
@taziden wait for me, I’m printing a banner.
-
What can I say is that we started with S+ apps being part of the firmware and only Suunto being able to develop them, to now where they are developed with a VSCode extension available to third-party partners of Suunto. Maybe Suunto will open this to other users at some point, but you know that this requires effort and resources on Suunto’s side, so it may take time.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi said in Stryd S+ app:
What can I say is that we started with S+ apps being part of the firmware and only Suunto being able to develop them, to now where they are developed with a VSCode extension available to third-party partners of Suunto. Maybe Suunto will open this to other users at some point, but you know that this requires effort and resources on Suunto’s side, so it may take time.
I dream of the day where there will be a beautiful Neovim extension in Lua. A man can dream
-
Finally found some time to play with this
I basically added RE as defined here and ECOR as defined here.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi isn’t one of the metrics redundant? Basically one is the reciprocal of the other.
Dunno, maybe an finds both helpful at the same time and dividing on the fly is inconvenient.
-
@DMytro they are reciprocal yes, thought about showing only one and storing both but put them both in eventually.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi interesting.
Just some thought:
The RE is speed/power. So far so good. Just as I understand, power is calculated in the watch using speed as an input variable.
It would work with a native power meter (like built in cycle crankarms), but I doubt it makes much sense when power is just a function of watch metrics… -
@Egika I guess speed isn’t the only variable used to calculate suunto wirst power.
-
@v-sacre of course. But you still get some kind of self referencing data.
-
