I didn't mean to gloss over Nikeow's question earlier about some kind of performance evaluation tool.
We have more developer tools in the pipeline, but the focus has been more on debugging tools, which I believe should be our priority right…
I didn't mean to gloss over Nikeow's question earlier about some kind of performance evaluation tool.
We have more developer tools in the pipeline, but the focus has been more on debugging tools, which I believe should be our priority right…
Could it be possible to set up an easier UI for entering large numbers ie "Initial Velocity".
Making a way to enter large number values with the touch screen would be awesome.
On watches where you can only have 2 CIQ DFs in an activity, if every DF used less than 1/2 of the possible fields, that would be a work around.
Not to state the obvious, but that only works if everyone is aware of the limit and is willing…
I like my Garmin watch because:
- it has buttons (hard to imagine Apple making a watch with 5 buttons.)
I see all the limitations in apple stuff, like you can't take manual laps in the AW strava app or you have to press both the button and the digital…
TL;DR it looks like an earlier hardware revision / internal model [2021] of the OTBeat Burn supports both ANT+ and BLE, while a later revision [2023] only supports BLE.
If a sensor broadcasts either via BT or ANT or both, it can connect…
I guess the years-long discourse about using old SDKs is finally coming to an end.
Tbf this is probably the best possible solution for everyone…
