Manually logging swim is tedious

[egpuckett]

Fitbit  needs to improve the interface for manually ending swim workouts. The scrolling dials are not cutting it. It takes forever to enter 2500 yards because I have to scroll through a dial that increments in units of 1 until I get to 2500 yards.  

Recommend a number keypad instead.  

[LiliyaFitbit]

Hi @egpuckett, it's nice to see you again in our Community Forums. 

I appreciate your participation in the Forums and sharing your feedback in order to improve the interface for manually ending swim workouts. Thank you for providing an example, I understand your point and appreciate your suggestion for a number keypad. Feel free to post your idea in our Feature Suggestions board. That way other users can comment and vote on the idea to show their support, and our team can take it into consideration. You can read the FAQ to better understand how that board works and do a search first, in case someone else has already suggested your idea, or something similar.

Keep on visiting the forums! 

[egpuckett]

Hey everyone I took @LiliyaFitbit‘s advice and posted this idea on the Feature suggestions.  Please vote it up.    

https://community.fitbit.com/t5/Feature-Suggestions/Need-number-pad-to-manually-enter-distance-for-s...

[LiliyaFitbit]

Thank you for the update, @egpuckett.

I am glad to hear you posted your idea in the Feature suggestions board. Thank you for your time and efforts. These ideas are reviewed by our team and if this suggestion receives votes from other customers, it will be shared internally with various teams at Fitbit and the developers will try to implement it.

I'll be around. 

[egpuckett]

I've been taking time to think about this more and wanted to add some more clarity to the issue. I am not sure this should be limited to a feature request that is dependent on enough votes to gain popularity.  The image below shows the experience I see when logging a swim workout.  A couple of issues are present.

1. The distance input is almost illegible. It looks like it's a little confused between expecting a number or a date.
2. This morning, I scrolled through the dial to enter 2800 yds. I stopped at 2800 and noticed the units was set to meters.  When I switched from meters to yards. It converted 2800 to 3062.  While this conversion is accurate.  The unintended consequence is the user has to go back to set the number back to 2800.  

I really think this is a GUI bug and not something that should wait for a feature request.   I get that the Fitbit team is trying to do agile-based product management. But some of these issues need to have a way to be resolved without waiting for a high enough vote from the user base.