Quite nice, but does not meet all expectations

The concept is good. In particular, I like that you do not ever have to worry about charging, because the batteries will hold up to one year. In addition, the connection works for my Windows desktop via Bluetooth outstanding. The accuracy of the distance measurement is very good. With some adjustment effort I managed to make my jogging provides Vivofit identical values ​​with the GPS. What is less great that Vivofit recorded only run activities in principle. All sorts of other activities pushups, squats, exercises with weights, even running on the steppers are not caught or not in a comprehensible manner. Although I have not, but I suspect that Vivofit is immune to cycling exercise bikes. The sleep function is relatively useless, at best, you can see beautiful, how many times you had to pee, so what can provide good benchmarks in advanced age.

Addendum: Lately (end February - early March 2015) I have problems with the synchronization. Constantly attack through the synchronization a red underlaid error message and the data is not transferred. I then looked in the times Logprotokolle stored under Program Data> Garmin, but it has become'm not really smart. Emotionally, but I would think that the Garminserver are overloaded. I then attempted to manage the data under Core Service> Devices> ID number of the bracelet> Sync are stored> Fit_Type_32 manually load. That did not work. Garmin support the found files, of which I suspected it were the upload files, the manual upload not. Now after I had tried everything on my desktop what had occurred to me as I have Garmin Connect installed on my laptop and then synchronize went well. The installation, access to my old account etc. but was painfully slow and therefore also my guess to congested servers. After a new installation of Garmin Express (as always very comfortable at Garmin) it is now running again on my desktop. Unfortunately, now runs but at Garmin (in the cloud) not get it right. In my case, for example, the value for the number of steps from the last Sunday is indeed a single value properly reported but incorrectly assumed in 7 days history (difference of about 10,000 steps). The value for Monday then votes again. One day later, then the correct value was taken after Sunday in the update.

Overall quite an indictment of a company like Garmin!