Expose data, sensors, objects and methods in the API for use in the SDK for apps and watchfaces.

[BamaBob]

There are many sensors and data elements that are either missing from the API or woefully under-documented so that developers are not able to access them.  In reality, anything available from the device or user or account or settings should be evaluated to determine if there is any reason to hide it from the developer.  There would only a few bits of personal data that would need to be kept private, but all other data and sensors should be exposed to the API.

Below are a couple of items that I have come across that should be exposed so that developers can use them in writing apps and clock faces for Fitbit devices. This is by no means an exhaustive list of everything that is missing.

 - Hourly steps/goal (Reminders to move) - A lot of developers are doing a lot of extra coding trying to calculate and keep up with this data when it should be available to them with one line of code.

 - Ambient light sensor data - I would like to use this to change the color scheme on my watch face when the room is dark.

[JonFitbit]

Thanks for the feedback. The SDK is still evolving and we're adding new APIs with each release.

There's a feature suggestion for the Reminders to Move, so please vote on that to express your interest. https://community.fitbit.com/t5/Feature-Suggestions/Enable-developing-clock-faces-that-support-Remin...

I agree the ambient light sensor would be handy too. Please add a feature request.

Can you provide some examples of the missing documentation you'd like to see added? Thanks.