Fitbit's feature suggestion is broken, or the triage and prioritization process ineffective. Currently many suggested features have received high praise (examples where legal or IP protection are not a concern - 1, 2 3, 4, 5), but have not been prioritized over other features like Bitmoji integration are developed without any communicated interest.
Fitbit community members have been asking to have a more open SDK to fill in the gaps while Fitbit pursues corporate agreements, or new products. Currently users of Fitbit products don't have visibility to the rollout of features which may lead them to look elsewhere when features (5) that many low end trackers have, or were advertised by fitbit (1) are not available.
Fitbit should either publish or share a roadmap of features, break out statuses for features that will not be implemented such as "not planned for 2019" (or 20XX), or open up the SDK similar to what Pebble had done prior to it's acquisition. Doing any of the above suggestions would give insight to interested users about what to expect or when, slow down requests or provide a more complete reason to why a feature was not or is not being pursued by Fitbit, or allow the community to fill in the gaps that Fitbit is not meeting.
Moderator Edit: Clarified subject
... View more