With the current state of tech indeed the web app world is diverging from the Apple platforms.
Browsers on iOS don’t have access to hardware like Bluetooth and USB like they have on Android, Mac, Windows and Linux.
So while web based apps can cover 4 different platforms, they are still cut off from Apples’ iOS, iPadOS, tvOS and watchOS.
My plans are to have 2 versions of Auuki. The current web based version and also I am working on a group of Native apps for all the Apple deveices.
So the web app will cover Android, Mac, Windows and Linux and the Native Apple apps will cover iOS, iPadOS, tvOS and watchOS and will also add first class support for Mac.
Developing native for Apple allows for code reuse across the different Apple devices and unlocks a whole lot of features from the famous Apple Ecosystem.
So having Auuki run on Apple TV while being controlled by Apple Watch and the tv remote is going to be cool. An outdoor app for watchOS with support for the Moxy monitor is also in the works. It’s a lot of work for a solo developer, but I am excited about it and can’t wait to ship it in production one day!
I used Auuki for one workout, but I noticed that the target power (ERG) is slightly different than what it should be. It sounds bigger than a rounding error, but I don’t know…
For instance, my FTP is set to 218W.
I did intervals at 100%, 115%, and 125% FTP, which should have been at 218W, 251.7W, and 272.5W, but they were at 217W, 249W, and 269W respectively.
Basically, I saw 2-3W difference.
Here the power targets are 1.0, 1.148 and 1.247 which is a bit off, but enough that they were rounded down with a full percentage point in Auuki. So this is the reason that the watts were off. I added a code to Auuki, which tries to round the ZWO target back up, which kinda fixes the issue. But still if you would actually want to use a percentage like 114.8% you’re gonna end up with something rounded up to 115%.
@David is that the expected behavior or I am missing something about the workout editor syntax?
I’ve compiled another example in the github repo here: GitHub issue 232
I have sorted out the rounding issues. Intervals.icu was converting everything to watts and then back to % of FTP for ZWO, now those are passed straight through:
It will be fine if we can choose any workout within 7 days range for example and not only workout of the day.
FTP and weight sync will be a fine improvement too.
For the moment I am not planning to add support for more workouts than the daily one.
FTP and Weight sync is almost ready. The development version of Auuki has it implemented, but I am still debating with my self on how to approach the UI side of the feature. Currently any time you get the daily workout Auuki will query Intervals.icu for the latest FTP and Weight and will update them. But existing Users will need to re-authorize Intervals with one new permission in order to be able to sync this data from Intervals.
Anyway will think it through and will let you know when it’s ready for general usage.
Thank you for response. For workout it’s not very difficult, I move workout in intervals and sync Auuki with the new calendar.
Some other improvments :
A filed with Cadence and target cadence (actually you can have cadence or target)
Ability to increase/decreas power only for interval or for all workout (like in ictrainer).
A popup or anything to see next intervals power & cadence target. (in IcTrainer, I have a popup 5s before next interval).
A filed with Cadence and target cadence (actually you can have cadence or target)
You can actually tap on the Cadence Data Field and it will start cycling between different value. One of them show the current Cadence + the target cadence next to it. Other switchable fields are: Power, Target, Heart Rate, Power Lap.
Ability to increase/decreas power only for interval or for all workout (like in ictrainer)
You can inc/dec power for the whole workout by changing your FTP in settings. The change will take effect immediately and will re-calculate the workout on the fly. The original FTP value will e restored automatically next time you sync a planned workout from Intervals.icu.
You can change the Power Target of the current intervals by using the +/- buttons.
A popup or anything to see next intervals power & cadence target. (in IcTrainer, I have a popup 5s before next interval)
At the moment I am not planning on adding this feature, but you can switch on the audio signals in Settings, and also the workout graph should show target if you hover on an interval (although that’s more usable on Desktop).
@dmarinov But WebANT doesn’t seem to be further developed. Or am I seeing this wrong?
My goal would be to use it under Linux, since Microsoft will no longer support many old computers that many use for training and I have problems with the Wahoo Core and Bluetooth there.
Is it worth testing the ANT+ version?
On one hand I have large parts of the ANT+ protocol developed and ready for web specifically, including most things related to cycling. And there is a working demo which shows that you can connect a trainer and a heart rate monitor to a browser.
On the other, it’s potentially usable only on Android, Mac and Linux, with Windows being a huge unknown. The demo is also just a prove of concept, it’s going to work for only about 8 minutes. Won’t be suitable for actual use.
The main blockers on this are:
The Windows driver issue, and
There is not much interest in ANT+ currently,
I need to code a proper Message Handler (the one included is getting overloaded after about 8 mins, therefore the demo breaks at that point),
Could easily resolve 3., but 1. and 2. can’t do much about it.
I’ve left the ANT+ button on Auuki to let people know that it’s a possibility, but you guys are the first ones to ask about it in like 2 years.
Could try to put a couple of weekends of work into it, but as it is my resources are already kinda stretched.
Ok! Thanks for the answer. It might be better to mark the ANT+ button as beta. Otherwise we will look for the problem for too long. I’ll see if I can get Bluetooth to work under Linux. Thank you!
Hey everyone,
here is a summary of the recent Auuki updates:
Moxy Integration Gets a Boost
Since today is the second day of the Moxy Summit, I decided to expand the support for the device. This latest release brings dedicated Moxy muscle oxygen (SmO₂) graphs. Now you’d be able to switch between the Power graph and the Moxy graphs by clicking on the graph window. The Moxy graph will also feature Power and Heart Rate, so even if you don’t use the device there is something for you.
HRV Data in .FIT Files
Recording of Heart rate variability (HRV) as native RR intervals in your .FIT files is now supported.
Battery Monitoring in Settings
You can now check your device’s battery level directly in the settings. When you connect a device a battery icon in the right corner will indicate the battery level with real time updates if the device supports that as a feature. I found that particularly useful with the Moxy monitor.
Weight and FTP Sync from Intervals.icu
Weight and FTP can now sync automatically from Intervals.icu. Some of you may need to update the permissions by re-connecting Intervals.icu.
Visual layout improvements
Dock mode, and high resolution displays will got some visual improvements.
Great APP. I had my first workout with her today and it worked out wonderfully. A few more tests and I will switch from MyWhoosh completely.
I would have a small wish. All the other apps I’ve used so far have an autostart. I can prepare everything and when I start kicking the workout starts. That would be easier than pressing play on a distant laptop. Auto break would also be great at the end
You’re right I will add autostart. Currently there is auto-pause (switchable in settings), function that does that, but only for the middle of the workout, will expand it to be available for the start also.
Yes I’ve been looking into DFA Alpha 1 too, but it will take some time. I’d need to do some computational optimizations on the existing algorithms, in order to make them suitable for the browser.
Hi. Great app! One question. Can you display the power as averaged over a user defined interval? I like to use either 3 or 5 seconds. It reduces the fluctuation I see in the app.
If that option already exists, I may have missed it …