I have a Surge, and I bought it because of the GPS for bicycling. However, I'm not very happy with the step conversion algorithm. Yesterday, for example, I bicycled for 3.5 hours - 46 miles. 67 minutes were spent in the peak zone, and 84 minutes in the cardio zone. My Fitbit increased my step count about 4,000 steps for that entire effort.
Now, suppose I spent that time walking a leisurely 3 mph, for 3.5 hours. My stride length gives me 2,100 steps per mile. That would be 6,300 steps per hour, or 22,050 steps for the 3.5 hours -- and all that would be at a far lower expenditure of energy than my bike ride!
Fitbit is currently giving me about 87 steps per mile bicycled. It would be much more realistic to give around 475 steps per mile.
If this were a premium feature only, I would be happy to pay a bit extra for it.
So here's my suggestion: allow a "conversion factor" for Fitbits equipped with GPS and clearly identified bike rides. This could be based on miles ridden, or on calories expended. If miles ridden, I would suggest a range from 500 steps per mile up to 2,000 steps per mile, in increments of 100 steps.
Or, it could be based on calories expended (a more reliable gauge, IMO). In the ride above, Fitbit showed I expended 2,166 calories for the 3.5 hours of bicycling - which might be a bit high, but not that much. Fully weighted, my conversion factor would be 10 steps per calorie. So I would suggest a conversion setting ranging from 1 to 10 steps per calorie, in increments of 1 step.
The reason I'd like this is that I have some fitness buddies in my family, but they don't bicycle. Since I bicycle between 100 and 150 miles a week, this would give us a more meaningful comparison
Moderator edit: Labels
Join us on the Community Forums!
Community Guidelines
Learn the Basics
Join the Community!
Not finding your answer on the Community Forums?
Go to the Help Site
Contact Support