June 2, 2021 | Version 1.8.8
Good app but during my last workout, i realized that power 3s shown is ~30W upper than reality so my workout was too easy. I cannot use anymore this datafield as i can’t trust it
June 14, 2021, RobAyris
Hi Cedric, sorry to hear you're having trouble. If you would like some help to try and find out why this isn't working for you, please use the contact developer link. Rest assured though, the power averaging calculations performed by the App are correct, but there are a few external factors that may be causing an issue for you.
March 7, 2021 | Version 1.8.5
I love the way this software displays everything I want to see (and then some) at one time. I feared it might be too confusing but that hasn’t been the case. The only complaints I have are with Garmin not providing the ability to read power zone values from Garmin connect, but programmers can only use the api’s made available to them.
I highly recommend this to anyone training with power.
August 22, 2020 | Version 126.96.36.199
Rob is a great developer who build amazing apps and he is so responsive. I am using his data fields on my Edge 1030 Plus. Good job Rob
July 9, 2020 | Version 188.8.131.52
I have an issue with this and that why won't use it.
Bar display works normally i think so, but circles which I like more does not scale properly on Edge 820.
If I use 2 data fields bar display still stays only 1/4 and is not readable.
July 11, 2020, RobAyris
Thanks for the review. It's great that you want to see the new circles mode on the 820 device. Good news! It's done. Update to the latest version (184.108.40.206) and the new circles mode is available for Edge 820 / 520+ in 2 field configuration mode.
July 31, 2019 | Version 220.127.116.11
Buena apliación, pero no muestra los datos de un smart trainner BKOOL con medidos de potencia.
July 31, 2019, RobAyris
Hi there, thanks for reaching out. Are you able to pair your smart trainer with your garmin device? If so, can you see power in the standard garmin power datafields? My app just picks up power data from the activity, so as long as it's paired and the power data appears in the activity, then it should be fine. contact me directly and we'll see if we can get to the bottom of it.
May 10, 2019 | Version 1.6.5
Hey Rob, Training Power keeps being my favorite IQ App!, congrats for a very nice job.
An improvement suggestion for your consideration, on the average power field, would it be possible to make it optional and choose between Lap Avg power and Total Avg power?. thanks!
May 13, 2019, RobAyris
I’ve thought about adding that functionality before. Unfortunately, garmin don’t make it easy as there’s no inbuilt lap data for power - I have to manually calculate it and respond to the lap button. Because of that I struggled to convince myself lap data was useful.
How would you use lap data?
The problem I see with displaying Lap Average power is that it’s only an average for the current lap and once you’ve pressed the lap button, you will forever see LAP average power for that activity. What if I want to see average power for the whole activity again?
I’ve previously thought about coding the app for this approach: If I’m out riding and get to the bottom of a hill, I’d like to press the lap button and have the app start displaying average power for that lap. When I get to the top of the hill I want to press the lap button again and have the app resume displaying power average across the whole activity. This way you can see your average power on the climb (or whatever segment you’ve chosen), but then be able to revert back to displaying activity average power. I even went so far to test this in the app, but decided it wasn’t that useful in the end, so removed it. It’s a constant struggle with memory limitations on my device (Edge520), so I don’t like leaving stuff in there that won’t be used. But I could be convinced otherwise…
December 10, 2018 | Version 18.104.22.168
thank you it's perfect now
December 6, 2018 | Version 22.214.171.124
great！circles mode is back in 126.96.36.199.
However, there is a new problem. In the "CHOOSE DATA FIELD TO DISPLAY" setting, if "Current Speed" is selected, there will be many zeros after the decimal point, just like "0.000000".
Again, this is a great data field! Whether in training or competition. Super cool！！！
December 6, 2018, RobAyris
Thanks for bringing that to my attention. It's fixed in v188.8.131.52. Cheers.
October 8, 2018 | Version 1.6.3-upd1
Just removed my old comment with only 2 stars. Now I understand the app, and I like it.
October 8, 2018, RobAyris
Thanks for taking the time to update your review and reply, I really appreciate it. I'm glad you like the app. All the best.
August 5, 2018 | Version 1.6.3-upd1
This is the best data field I have ever used. All the data I need can be displayed in a data cell.It feels great.
But it also has some small shortcomings. I used it on edge820.When i 'm riding. The numbers are too small to read.
So I can only give four stars. I very much hope to be able to expand the display scope in the next update.
这是个非常棒的数据栏 里面的内容 正好是我需要的 丰富 紧凑 缺点就是 在820上使用 可视面积太小 不便于读取
希望在下一个版本 能得到改善 根据数据栏的大小 来自动缩放 那样的话 会是完美
August 7, 2018, RobAyris
Hi MIN, thanks for the great feedback and review. I understand exactly what you're saying about the text being too small, there's a lot of info to display. Unfortunately, the Edge 520/820 have small screens anyway, so it's hard to fit larger fonts in. Providing different screen configurations is also difficult as the 520/820 also has limited memory capacity available for each CIQ app. The upshot is, there's not a lot I can do about it unfortunately. I'm in the same boat as you. I'd love to buy an edge 1030, but can't justify the cost. Ironically, there's also more memory available in the 1030 and more screen available to do larger fonts and different layouts!!
April 20, 2018 | Version 1.6.3-upd
Only seeing 3 data fields on Garmin Edge 1030 with FW 3.90. Unable to see the full-screen mode shown in your screenshots.
Rubén Ibáñez Gómez
February 7, 2018 | Version 1.6.3
Grandísimo trabajo, un campo de datos excepcional
February 12, 2018, RobAyris
Gracias por sus comentarios positivos y revisión. Muy apreciado.
December 25, 2017 | Version 1.6.2
Hr and Power app are fantastic.
All of us are waiting for cadence data field, like hr and power.
Can you do that for your fans ?
January 5, 2018, RobAyris
Thanks for the feedback. Personally, I’m not convinced of the merits of a specific cadence data field, but I’m happy to be convinced otherwise, if enough people think it might be useful… What data would you like to see?
November 16, 2017 | Version 1.6.2
Hey Rob, top job with this version addressing the bug in edge1030, working great now!
November 10, 2017 | Version 1.6.1
Love the app, but the with the latest version for 1030 something went wrong..., data is overlapping everywhere
November 12, 2017, RobAyris
Hi Loukas, Can you please send me a screen shot? Also, Can you please check the app settings and see what the two values for the Text Offset X & Y are? If they are anything other than zero (for both), can you try setting both to zero and see how that looks? If you do this from your phone whilst connected to your device you should be able to see the changes straight away. Thanks.
October 8, 2017 | Version 1.6
Great app.... and 1 request to make it even better :), the W' feels more important (to me) than the w/kg one... so, is it possible to swap them? currently the W' field is too small
October 9, 2017, RobAyris
Hi Loukas, thanks for the feedback and review. I know what you mean. I chopped and changed on that one a few times. To me the W Prime percentage figure wasn't as important as seeing the visual indication provided by the bar (or the circles in the circles view), so I made the percentage figure smaller. But, I can understand your POV, so I think I might provide the choice of two options in the settings page: option 1 - display W Prime value on left, W/Kg value on right (default, as is now). option 2 - display W/Kg value on left, W Prime value on right. I can't give a timeline as to when this might happen - depends whether any issues are found with the current version or if there's any more feature requests, that sort of thing, but I don't see why it couldn't be in the next release. Cheers.