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?

How to Allow Common Code for 4.2 and 5.0 API

Status: Reviewed By Moderator Submitted by on ‎09-28-2020 14:19
2 Comments (2 New)
Version "resources" folder in Fitbit Studio/CLI using major OS build numbers, ex. "resources/4" and "resources/5". Support one prior MAJOR version (not minor) in tools. Allow tools to dynamically select resource folder based on the build target. Allow JavaScript to query for device capabilities (4.2 returns false for new 5.0 features).
This is needed because:
Most new home consumers are still using recently purchased 4.2 legacy devices and want software. Prevents developers from having to duplicate projects/code to support multiple API versions. Prevents duplicate projects and fragmentation of the Fitbit Gallery.
I'd use this: Daily
See more ideas labeled with:
2 Comments
TigerPointe
Base Runner
‎09-28-2020 14:33
‎09-28-2020 14:33

The basic ideas is that most of the high-level JavaScript will not change and is still compatible no matter which API is used..  For most projects, it's only the "resources" that change (different sized icons, images, styles, etc.) or get renamed.  Plus, versioning the resources folder allows for compatibly with future platforms, like API 6.0 and beyond.

Status changed to: Reviewed By Moderator
YojanaFitbit
Moderator Alum
Moderator Alum
‎10-29-2020 13:06
‎10-29-2020 13:06

Hi @TigerPointe, and thanks for taking the time to share this suggestion about allowing tools to dynamically select resource folder based on the build target. We rely on feedback like yours to help us develop products and features that we know our community wants to see. If this suggestion receives votes from other customers and gains popularity, it will be shared internally with various teams at Fitbit. To learn more about how Fitbit decides which suggestions get developed, visit our FAQs.

Watch this space for status updates. In the meantime, try visiting Health & Wellness to talk with other members about all things health and fitness.

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