Fitbit: Difference between revisions

{{CompanyCargo

| Founded = 2007-03-26

Unlike the Charge devices that came before and after them, the Charge 3 and 4 have plastic strap connectors that snap off from the device with regular use, this often happened in under a year. Fitbit was willing to provide replacement devices in many cases, but never admitted to this fault publicly.

Fitbit supported syncing music from your PC to your smartwatch to play offline. Supported devices for this were:

Legacy fitbit devices (Surge and prior) used oauth1.0 to connect to Fitbit's servers. The firmware embedded onto these devices gate core functionality like setting the time, setting the clock face, logging heartrate data, setting alarms, etc. behind this authentication process. The company leaves no way to use the devices without authenticating and uploading data to their servers and having that data fed back to your client which is no longer possible on these watches due to them updating endpoints to oauth2.0, making the Fitbit Surge the "Super Watch" that could only correctly tell the time for less than a decade.

The Fitbit Ionic was the first device to debut Fitbit's new Pebble-like SDK called "Fitbit SDK 1.0" and it released in 2017. Fitbit reportedly ignored issues of the device burning on people's wrists for 5 years until their voluntary recall program in 2022. If a user enrolled in this recall, they would be offered varying refund options, and their device, regardless of functionality, would be remotely bricked by Google. If a user did not enroll into the recall, their device would remain as-is, but without any new security patches for it's Fitbit OS.