I’ll be looking at the Alta soon but I’m going to focus on the Blaze for now. I forgot to begin my Surge with me while away recently so I relied on the Blaze for running. However, given a recent run test with the Blaze, I decided to try again.
There’s no kind or gentle way to say this. The Fitbit Blaze is woeful at measuring distance (and therefore pace). I ran with the Blaze, connected to my iPhone using Fitbit’s GPS assistance feature and with Strava tracking my run as well.
Here are the two recordings of the same run (I’ve got Strava and Fitbit exchanging information so the two summaries are stored in the Fitbit app).
Fitbit added an extra 3.63km to the distance and credited me with a 5:56 pace.
These are significant differences – particularly as I’m now in marathon preparation mode and tracking distance and pace closely so I build slowly for the 42.2km journey that awaits me.
This problem needs to be solved. Fitbit has all the pieces – communications to the phone, access to the GPS, the ability to produce nice running maps with splits and graphs that show heart rate, elevation and pace so I can look at my performance and tune my training accordingly.
I understand that the Blaze is pitched as a fitness device rather than a bespoke running watch but if you’re to tout the GOS assistance then it should be used to accurately measure distance and not just produce pretty pictures.
Come on Fitbit – you can do better.