Announcing Fitbit OS 3.0

[JonFitbit]

Hot on the heels of the Fitbit OS 2.2 release, we’re bringing you a fresh set of APIs which will supercharge your app development, and unlock some amazing on-wrist experiences for users.

This update for Fitbit Ionic and Versa smartwatches will allow developers to easily create custom exercise applications, perform faster on-device calculations, launch other applications, upload files from the device to companion, and experience super fast side-loading with partial installs and compressed bundles.

https://dev.fitbit.com/blog/2018-12-17-its-time-to-exercise-with-fitbit-os-3/

[jomis003]

@JonFitbit -  I (and I am sure others) have users that are reaching out to me saying they are seeing clock errors on their devices along with other unusual activity.

Is this due to the release of 3.0? I am unsure on how to respond as I am unable to reproduce anything. The only thing I can think of is that everything is still targeting framework 1.0.

Should we now be targeting framework 3.0 for all new apps/updates?

[Capitano]

Is it possible to define the marked icon for userdefined exercises shown in the Fitbit app when I'm working with the exercise API?

Regards

Capitano

[nokotok]

@JonFitbit Hi, can we get answer on this question please? I recently switched all my clockfaces to SDK v3, will fitbit devices with older OS work with this SDK or is it better if I revert them to SDK v1? What is the current coverage of SDK v3 (how many users have already installed new OS)? Thanks

[skiddy56]

@JonFitbitJust wanted to say Thanks!  The updates look great and will, I think, reduce the code base considerably for those of us doing exercise apps.

Rich

[ceriboo]

hello. What a pity still no web api for the watches... Please can your  add this on your road map?

[kimri]

The blog post on versioning says users won't be able to install apps from the app gallery that don't target their current firmware version.

But critically I can't find any explanation for what happens when a user's device gets a firmware upgrade (to 3.0, say) and a pre-installed app isn't targeting the new firmware? (assuming the app developers haven't yet released an update that targets the new firmware).

Will the pre-installed app be automatically removed from the user's device? Will it stay on the device but stop functioning because it's incompatible with the firmware? 

Either way the user experience isn't great, and since us developers aren't given access to the new firmware in advance to test against, it's inevitable that there will be a delay before we can release an update to our app targeting the new firmware. 

Could you please clarify for everyone's benefit? Thanks a lot.

[JonFitbit]

---

@kimri wrote:
... I can't find any explanation for what happens when a user's device gets a firmware upgrade (to 3.0, say) and a pre-installed app isn't targeting the new firmware?

Will the pre-installed app be automatically removed from the user's device? Will it stay on the device but stop functioning because it's incompatible with the firmware?

Could you please clarify for everyone's benefit? Thanks a lot.

---

This only really applies to apps created with the new SDK version.

For arguments sake, let's say your device is running Fitbit OS 2.2, and your app is built using SDK 2.0. When the device is updated to Fitbit OS 3.0, existing apps continue to run without requiring an update.

If your device is running Fitbit OS 2.2, and a developers creates an application targeting SDK 3.0, you won't be able to install that app on the device until it's updated.

I hope this helps.

[DrRobin]

Thanks Jon,

That is what I had assumed, but good to see it explained.

[DrRobin]

Hi,

Did Polyline get added?

Also what about 128k?