help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Provide separate documentation access to SDK 4.2 documentation

Status: Reviewed By Moderator Submitted by on ‎09-27-2020 07:01
4 Comments (4 New)
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.
This is needed because:
The current documentation was updated to match SDK 5.0 and is hard to search the exact functionality for SDK 4.2 due to the fact that some features were deprecated.
I'd use this: Daily
See more ideas labeled with:
4 Comments
Status changed to: Reviewed By Moderator
JonFitbit
Fitbit Developer
Fitbit Developer
‎09-28-2020 02:56
‎09-28-2020 02:56

Thanks for the feedback. In the meantime, you can find an archive of the website in the Wayback Machine. https://web.archive.org/web/20200912173010/https://dev.fitbit.com/

gnitz
Recovery Runner
‎11-06-2020 12:57
‎11-06-2020 12:57

+1 for this. As someone who's just starting out with developing apps for Fitbit, it is beyond frustrating for me to run into information that is outdated or simply incorrect for SDK4.2. I'm sure developers are still targeting devices older than Versa 3 when making apps, having access to version specific documentation will be a big plus.

niilz
Jogger
‎12-20-2020 07:22
‎12-20-2020 07:22

I was looking for exactly that: an API-documentation for 4.x so that I could work on an app for the original Versa.

And my guess, why only so few state this wish here, is merely because the fitbit community forum has always been a little hard to search through in my opinion.

 

Although it is understandable from a company perspective to focus on the latest tier, I don't see why there shouldn't be an archive of older docs.

 

Thanks @JonFitbit for always trying to help. I can only imagine how hard it is to support so many cross-combinations. And the WayBackMachine-hint might actually even work for a few cases.

 

Nevertheless, older docs are something I would recommend. Especially if third-parties are kinda invited to provide value to the eco-system by creating software for the devices. It is never a nice experience for clients if they HAVE to upgrade their hardware after a rather short period of time. Especially if some software theoretically could be made available for their devices.

I just like to point out the frustration from this thread:

https://community.fitbit.com/t5/Other-Charge-Trackers/Charge-2-has-not-synced-lately/td-p/3086717/

where the sync feature for the Charge 2 just stopped being supported on Android apparently.

 

Like mentioned earlier. There are many many reasons to not support "older" device-software-combinations. But if this happens too soon (a very subjective time frame, I know) it is a thin line between upgrading and buying an alternative product.

 

Best wishes

moLiathroidí
Jogger
‎01-14-2021 10:58
‎01-14-2021 10:58

+1 for this. Very frustrating trying to learn fitbit development by stumbling through documentation for SDK 5 and old forum posts.

Having each SDK version cached and accessible through a drop down menu would be ideal, similar to how the OpenCV website is structured

 

@JonFitbit  thanks for the link.

To comment, you must first accept the terms of the Idea and Feedback Submission policy.
Accept Terms and Comment