Sugestion Idea to keep developing on Versa family ( except Versa 3 ) and Sense after 2022

[ceriboo]

In 2022, it will not be possible to use Fitbit Studio and Fitbit simulator for SDK 4 projects. The suggestion below is intended to make it easier to maintain SDK 4 projects without needing to create multiple Fitbit accounts.

The first change would be to the Account Settings menu (below):

I suggest that a new line be added to  this menu: “Developer Mode”. In this menu we enable the developer mode. Maybe we can add a validation process; eg, a request from a user and an acknowledgement from Fitbit team.

After enabling developer mode, the Account menu (below) would be enhanced.

Here we will see the primary watch of the developer (which must be the first paired device) and an optional SDK 4 development-only device. Or the  will have to tag which one is his main device.

The Fitbit app would only sync stats (eg, steps) with the primary device; development-only devices would only be linked to the account for development purposes. For the next smartwatches’ generations, I suggest to provides dummy devices to developer to ease the management in Fitbit app.

Thank you for your suggestions or ideas

[JonFitbit]

Thanks for the feedback. Unfortunately the Fitbit mobile app just isn't capable of running multiple devices with multiple companions at this time. Perhaps you could use a second Fitbit account with the Fitbit app installed on a second phone or tablet, then install the fba file for testing via a GAM link.