Product Feedback

Let customers and developers know when you will allow us to develop apps for the Sense 2 and Versa 4. Give us some kind of planning. Moderator edit: Clarified subject ... View more

As the new devices (Sense/Versa 3) have a speaker, please provide an API so we can play sounds. Will be perfect for us, game developers, giving users a more immersive experience. ... View more

I think an essential feature for the SDK is a way to a way to uniquely identify the current user. Ideally this would be linked to their Fitbit account so it is transferable between devices much like Pebble.getAccountToken() from Pebblekit JS. ... View more

Please create a dashboard that would display user statistics, ie, number of installs, statistics for Fitbit Web API, etc. It could be integrated into the existing GAM ... View more

Currently, the Fitbit OS simulator only supports Windows and macOS hosts. There are certainly developers out there who use Linux as their primary (or even only) development OS. It shouldn't be too difficult to maintain Linux port of the simulator since it is built using the cross-platform Electron framework, which officially supports Linux. I successfully installed and ran Windows variant of the simulator using the Wine (version 3.0 on Ubuntu 16.04 LTS), and it properly connects with the Fitbit Studio. Applications run with no problems. The only thing that currently does not work is switching the device type from Ionic (default) to Versa. Doing so will always crash the simulator. If the simulator properly ran under Linux, it would be kind-of solution for developing Fitbit OS apps from Linux. The real port of the simulator would be even better, though. ... View more

Please add 'path' support to svg in Fitbit OS. There is a large library of svg objects that use mostly 'path' elements to define them freely available on the web. By adding support for this, we could create a richer user experience.   It would also be easier to use 'path' elements to draw certain objects that currently require image files (e.g. images of a heart, footsteps, stairs etc.). Image files also use more memory than would be required by an equivalent svg 'path' definition.   Svg 'path' is also more flexible than an image. For example, there are currently two 'heart' images in Fitbit OS. One is a solid heart while the other is a heart outline. Both of these could easily be reproduced using a single svg path element and changing a single attribute to switch between a solid or outline heart.   Svg elements can also be scaled and rendered any size without losing quality. Currently, if you want differently sized images, you will either have a 'large' image that is then scaled down to the required size, or several differently sized images. Both of these options would require more memory than a path definition.   Moderator Edit: Clarified subject ... View more

It would be helpful to new and experienced developers to include github integration with fitbit studio. This would allow new devs to download sample projects and try them out and experienced devs to share their work and work collaboratively. Fitbit already has their sample code on github and requests code questions be posted with links to github gists, so they are already working with the github platform. ... View more

By implementing this simple change, you can achieve multiple results with one simple change: de facto you wouldn't need this anymore, as native apps could communicate with the watch via companion apps: https://community.fitbit.com/t5/Feature-Suggestions/Fitbit-BLE-API/idc-p/2219115 it would take care of this as well: https://community.fitbit.com/t5/Feature-Suggestions/Background-notifications-for-Ionic-apps/idi-p/2184239 Simple solution, a listen() method that takes a port and a function. The implementation will spin a thread that opens that port and listen to it and invokes the function. Example:     // my companion app code listen(8080, function(data) {  // data can be a byte array or a string   if (data == "ping") {     // send a message to the watch   } ) From a native app perspective it would be a simple as sending a message to a TCP port. Perfectly cross-platform, simple straightforward solution.   ... View more

It would be great if we could develop a new clock face that displays the current status of Reminders to Move, but this is not currently possible, although it is possible to come somewhat close.   I think we need the following enhancements to the SDK:   Provide a way that the clock face code can access the Reminders to Move preferences that were set by the user, e.g. the start and end times. Provide a way that the clock face code can obtain the exact values that the Today app is displaying, otherwise the new clock face app will appear broken if a user compares the values. Regarding the second item, what I'm looking for is a way to obtain the exact same counts, including previous hours, so that if a user installs a new clock face with Reminders to Move displayed and then goes to the Today app they will see the same thing.  I think the only way to currently implement the Reminders is to have the new clock face start counting when it is installed so it will not display the correct value for the current hour nor can it display how many previous hours were met or missed.  Note that this should work no matter when the device was last synced, so the hourly counts probably need to come directly from the device and not from the web API.   Thanks,   John ... View more

Please provide a way for developers to publish in GAM 2 different versions in the same time, one for SDK 4.2 (Ionic/Versa/Versa Lite/Versa 2) and one for SDK 5.0 (Versa 3/Sense) and both version to be reviewed in the same time, so we can be able to release the app in the same time for all our clients. Plus, this will lower testing time. ... View more

I would like to see the hourly activity feature on the watch face for the Versa. It is unfathomable that you can see calories but not your hourly steps.  Supposedly the Versa is aimed at the mass market, in other words people who are trying to be more fit but don’t necessary exercise on a regular basis. I think one of the greatest features for those trying to increase their activity is to do at least 250 steps each hour. And if you use this feature, you are going to be checking it probably a few times every hour. So why isn’t it on the watch face?  It is available on the Charge 2 watch face.  I would like some reassurance that this oversight by FitBil will soon be remedied.  I would also suggest that all the watch faces allow the user to choose which stats they want to see on the watch face. ... View more

(Looks like I've had this improperly tagged under Ionic. Should be under SDK. Fixed.)   I'd like my Ionic apps to be able to send notifications to FitBit's standard notification queue. I'm suggesting a two-part solution:   (1) Allow apps to register a background process function that the FitBit device calls on a regular basis, even when the app is not running. The app would indicate its desired wake-up frequency, but FitBit might want to set a maximum wake-up frequency to limit resource usage.   (2) Allow apps to drop messages into the notification queue that FitBit displays above the clock face. This allows apps to provide notifications without having to write a phone app to push them, which would further clutter the phone's own notification queue.   The max wake-up frequency would determine the kinds of apps that users could write. Once-an-hour wake-up would allow apps to provide reports or reminders. Once-every-N-minutes wake-up would allow apps to monitor progress and make suggestions or provide encouragement. Once-every-minute (or faster) would allow apps to provide real time notifications. Absent this feature, app developers are forced to write their own clock apps to provide app notification services, even when a novelty clock isn't the point of the app. Alternatively, app devs could write mobile phone apps that issue app notices to the FitBit watch, but this clutters up the phone's notification queue. At present, this latter approach also requires round-tripping between the phone app and an Internet server in order to communicate with the companion.   Also, it's ideal that the app be able to do this without the phone (companion) present, so that people can rely on the FitBit without having to always have the phone around.   Moderator Edit: Clarified subject ... View more

I'm getting a strong impression that improvement of FitbitOS is non-existent 😞 Basic features like alarm are not getting fixed for over a year. Improvements that would make some apps on the watch much more viable (like exposing basic crypto functions) aren't getting implemented as well.   I don't know what are the reasons for this state, maybe there just aren't enough people behind FitbitOS. But I would love to see FitbitOS doing much better than this. I would love to see changes implemented and released on the order of days/weeks instead of years. I would love to see the direction of the product actually motivated by how people use it.   I really like what you did with Versa, it looks and feels very nice. And I'm sad to admit this, but because it fails to perform some of the basic functions I need from it, I'm contemplating the possibility of returning it and getting some Android watch instead 😞   Please, try to improve this situation in any way you can, because currently the future doesn't look very bright. ... View more

It would be great if developers could access the sleep data without using the Sleep API (which requires internet connection and a reliable connection to the companion app). Device has the sleep data we need to parse and display in awesome ways in our apps! ... View more

The Sense 2 / Versa 4 SDK needs to be released ASAP to allow App and Watchface developers to bring teh Sense 2 up to the usability level of the original Sense. Moderator edit: updated subject for clarity ... View more

The current documentation is updated and reflects the current SDK 5.0. Please provide a separate documentation for SDK 4.2 so we can be able to further develop and support the clockfaces that run on Fitbit OS 4.x. ... View more

Hello, I would love to see NFC API in fitbit studio - (I have versa 2) or at least some way to add more than just credit cards.     ... View more

As competitor products have become available that provide public BLE api's, I feel it is important that a way to communicate with Fitbit devices is provided through BLE. There is a clear desire from consumers for this service, a quick Google search shows some consumers have even spent the time attempting to reverse engineer the BLE protocol. I hope you will seriously consider opening an api or even making some closed source mobile SDKs for accessing the Devices across bluetooth ... View more

I want to develop an app that uses NFC tags and while I searched the forum I noticed that there are others who also interested in making an apps that using that feature (like opening doors etc) so it would be nice if you allow the developers to access the NFC API.   Thank you, Shlomi. ... View more