This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Poor Strength activity user interface with Forerunner 255 compared to 245

Please up vote this thread if you agree.  Hopefully Garmin developers will notice and make the requested change.

The Strength activity interface of the Forerunner 255 is very cumbersome compared to that of the Forerunner 245.

On the Forerunner 245 you can edit weight digit by digit.  For example, warm up with the bar, scroll to the tens digit, click up four times, scroll to the ones digit, up (or down) five times.  For a total of 10 clicks (4 plus 1 to scroll plus 5).  Throw on ten lb plates for the next step all you have to do is increment the tens digit by two.

On the Forerunner 255 you can only edit the hundreds digit individually.  The next two digits are coupled together, so to enter 45lbs that's 45 up clicks!  And to enter 65lbs that's 20 more up clicks!

Additional clicks are also required on the Forerunner 255 to select edit the reps and weight.  As if Garmin wants you to really make sure you want to edit the reps and weight on the 255.  On the 245 the data was already there for you to adjust, or confirm, no extra press to select edit.

On the Forerunner 245 you just click straight through.  Adjust the number of reps, click straight through to adjust the weight. 

It's as if there were two different developers for the strength activity.  Like the developer for the 245 actually lifted weights and used the feature, and the developer for the 255 did not.

Garmin's response was, you can press and hold the increment button for it to increment faster.  Which isn't great, because then you're hoping it stops at just what you want, and if you overshoot you've still got ten button presses up or down to correct.  Whereas with the 245 there was max ten button presses, 0 to 9 for each digit.

Garmin Product Support also suggested that I could submit feedback here:

https://www.garmin.com/en-US/forms/ideas/

Hopefully if enough people submit feedback that the 255 Strength activity interface is so poor they'll change it to be like that of the 245.  Meanwhile, I'll use my 245 for Strength training....

  • On the Forerunner 255 you can only edit the hundreds digit individually.  The next two digits are coupled together, so to enter 45lbs that's 45 up clicks!  And to enter 65lbs that's 20 more up clicks!

    Additional clicks are also required on the Forerunner 255 to select edit the reps and weight.  As if Garmin wants you to really make sure you want to edit the reps and weight on the 255.  On the 245 the data was already there for you to adjust, or confirm, no extra press to select edit.

    On the Forerunner 245 you just click straight through.  Adjust the number of reps, click straight through to adjust the weight. 

    It's as if there were two different developers for the strength activity.  Like the developer for the 245 actually lifted weights and used the feature, and the developer for the 255 did not.

    I agree with what you're saying and I've complained about it before, but nobody cares.

    This is totally speculation, but I think the problem is that:

    - Garmin is trying to optimize that latest firmware/UI shared between recent devices for touch, since most recent devices do have touch

    - Seems that Garmin thinks fewer spinners is better than more spinners, for touch (and they might be right)

    Unfortunately, devices like 255 and 945 LTE do not have a touchscreen, yet they seem to have the same shared firmware/UI as other recent devices which do have a touchscreen

    I will say that even on a touch device (like 955), it's annoying to spin the 2nd spinner (the 10s and 1s). No UI that Garmin ever implements will be as fast and responsive as an iPhone or Apple Watch, for example, due to the purposely limited hardware resources on Garmin devices.

    I just do what Garmin suggested, and hold UP or DOWN to increment/decrement faster (it goes by 5s in this case). If I overshoot, I just hold the opposite button. Sometimes I will need to press a button up to 5 times to finally reach the correct value.

    Personally I would prefer one of two changes:

    - Have 3 separate spinners for 100s, 10s and 1s

    - If they must group spinners, group the 100s and 10s together, instead of grouping the 10s and 1s

    I think this kind of thing is an unavoidable problem for a hybrid button/touch device like Forerunner, where you can do everything with buttons if you want to, so touch is kind of optional. If you try to optimize for one input method, the other input method suffers.

    e.g.

    - strength seems to optimized for touch now (but not really) so button input suffers

    - spotify is optimized for buttons, so touch input suffers (in this case I can think of a lot of improvements, but that's a tangent)