FitBit OS 2.0 questions

[paperinik]

Few questions for @JonFitbit:

1. has this been released and rolling out or just announced? If it's rolling out any way to get the update earlier?
2. has the functionality of accepting calls, previously only available on iOS, been added to Android? 
3. what was the rationale (if it can be shared) of a different display resolution/aspect ratio for the Versa? 

Thanks!

[JonFitbit]

• has this been released and rolling out or just announced? If it's rolling out any way to get the update earlier?
  
  It's just been announced at this time. The simulator is running 2.0, but we aren't running a public beta this time.
  
  
• has the functionality of accepting calls, previously only available on iOS, been added to Android? 
  
  I'm unsure about this one.
• what was the rationale (if it can be shared) of a different display resolution/aspect ratio for the Versa?
  
  I assume this just came from the product team.  

[paperinik]

Thanks

Feedback for the product team: developers really hate these kind of changes. As you can imagine, changing aspect ratio on such a small display, really makes things hairy. This is the kind of stuff that killed Windows Mobile. 🙂

[_Attila_]

I have to agree that the resolution change is going to create problems down the road.

Also, not having a developer version of 2.0 for the Ionic makes developing on the emulator somewhat pointless as my smallish app that runs fine on the emulator is broken on the watch.

Without detailed release notes on what has been fixed and what new features are in 2.0, development will have to be put on hold until the firmware is updated as well. Using trial and error on the simulator and then not have it work on the watch is no fun.

Any ETA of the firmware update?

[Giampi71]

My 2 cents about the topic (as a new kind in the block since so far I did only a couple of clockfaces but never released) and how I would manage the problem described above.

- The first and easy solution would be to have all developers to be part of the initial rollout of every new firmware update so they can immediately test their apps and clockfaces

- The second, maybe only for big changes like from OS 1 to OS 2, to introduce developer previews (like Google does with Android) that all developers can volunteer to install.

[gaperton]

@JonFitbit is there the change list for 2.0 firmware release? New features, improvements, bug fixes, etc? It would be really helpful.

[paperinik]

@JonFitbit also, any improvements SDK wise? New APIs, capabilities (running in background), etc.?

(I am downloading it on my watch as I type...)

[gaperton]

> (I am downloading it on my watch as I type...)

Oh, really? What a nice surprise. Still, it would be great to know what is inside :).

[Giampi71]

---

@gapertonwrote:

@JonFitbit is there the change list for 2.0 firmware release? New features, improvements, bug fixes, etc? It would be really helpful.

---

https://help.fitbit.com/articles/en_US/Help_article/2302

[gaperton]

That’s great, but developers are more interested in SDK-related improvements. Bugs fixed, API changed, performance improved, etc. That are things you cannot see with a naked eye.

[Giampi71]

Sorry, I didn't realize we were in the development section of the forum.

Looking at the SDK documentation I don't see any update.

[JonFitbit]

The developer related changes (in addition to the usual firmware release notes) were all covered in the developer announcement blog post: https://dev.fitbit.com/blog/2018-03-13-announcing-fitbit-os-2.0-and-simulator/

We've started a release notes page for the simulator, and we're going to start doing the same for Studio too.