Versa 2 & Fitbit Studio

[rc26]

With the announcement of the Versa 2 watch, what can developers expect when it comes to developing Apps and Clockfaces in Fitbit Studio?

• What is the Versa 2 screen resolution?
• Has the Versa 2 processor been updated? Can we expect better/faster performance and load times? Can more ambitious projects be developed for the Versa 2 as a result?
• Is the heap memory limit still 64kb?
• Is the Versa 2 bluetooth 5.0 or 4.0? Fitbit.com shop says "Radio Transceiver: Bluetooth 4.0", and sites like digitaltrends.com reports 5.0.

Thanks.

[FLav0ured]

Furthermore I'd like to know what version of JavaScript will be supported on the Versa 2. Will it be limited to ES5.1 as previous devices or does it support using the Event class or Date methods with the options parameter for example?

[AlexProphet]

I'd really like to know these things too especially regarding the 64kb limit on the RAM. I think this was a massive mistake on the part of Fitbit. I know they had to compromise on something but IMO they compromised on the wrong thing. It sounds like the specs of a computer from 1982 but it's actually far worse than that, because those computers were programmed in assembly language which is many times less memory-hungry than JavaScript.

If they haven't increased the available memory they should at least provide us with a way to program in C or assembly!

[allan175]

I think Javascript was their biggest mistake. C/Assembly is definitely more suitable for a memory/CPU constrained device.

I'd have done a lot more with Fitbit if I could do it with C.

[SunsetRunner]

concerning screen resolution , you probably noticed that all apps and clockfaces available in gallery and compatible with VERSA and VERSA lite are now compatible with VERSA 2.

It means same screen resolution.

[AlexProphet]

Of course, good luck explaining assembly language to chief executives/investors! But I still hold out hope for C...

[JonFitbit · Accepted solution]

There will be a developer announcement soon, but can confirm the screen resolution is still 300x300.

[Partah]

Just got a new Versa 2. A few of my my old Versa watchfaces not showing on Versa 2 watchface collection. 

Fitbit Studio is also not ready for Versa 2. I guess I bought and switched to Versa 2 too soon.

[gratefulmommy]

Will our present faces made for Versa work for Versa 2? I have several private faces I've made for myself, but it is saying that it cannot be installed on the Versa 2. Please help 😞

[Gondwana]

Fitbit staff will be initiating a sweep through the gallery to flag all compatible apps and clockfaces as available for Versa 2 fairly soon. They've already done it once, which is why some (mostly older) products are available.

[Gondwana]

Present faces will almost always be compatible with Versa 2, but they have to be built with that Versa 2 compatibility indicated in package.json. At the moment, the publically-available build tools don't support this. Fitbit as promised an announcement about this soon.

[Partah]

Very helpful information. Thank you!!!

[jmw137]

Looking forward to the announcement. I’m curious, do you know if developers will be able to take advantage of the always on display for watchfaces?

[Gondwana]

Unfortunately no; at least, not initially. display.autoOff won't work for your app/clockface, but the watch will revert to a built-in always-on clockface when the time is right (and the user selects that setting).

[jmw137]

Okay. I understand not having this initially but I would love to be able to have a custom built always on clockface. At least more options. It is annoying having the face change styles on waking up. 

[BlythMeister]

Since the device has been released, my face apparently supports versa 2.

But getting reports that the UI alignment is off.

Without buying a device, I'm unable to rectify this...it's a shame that the device is released before Devs can actually work with it!

[FitnessJunky]

What a pathetic implementation of always-on display!

I turned off this feature on new Versa 2 in the first 10 minutes. Raise-to-wake functionality does not work in AOD mode. You will have to either double tap the screen or press the button to resume the normal watch face.

Samsung watches have this always-on feature for sometime and the experience has been great from day one. Apple has taken it to the next level with series 5.

It may be a resource issue for Fitbit. They are struggling to compete and grow. No wonder they are taking such shortcuts!

They must open up the always-on feature for further refinement to the developer community. Otherwise Versa 2 will be a flop! IMO.  

[TKCMuzzer]

I agree, the fitbit studio simulator should have been updated before the Versa 2 was released, this would have given devs a heads up for any code issues.

It also seems odd that devs can't just produce an AOD face using the limitations provided by fitbit to keep battery usage down.

[tjmcc01]

It would have also been a good business decision to give devs access to the mic from day one. It's clear Fitbit isn't putting in effort to device software -- opening up the SDK would allow 3rd party devs to in fill the gap.

[AdeRussell]

I have only Versa and Versa Lite visible in Fitbit Studio.  I assume the part of the json file that currentlt reads 

"buildTargets": [
"meson",
"gemini"
],

Would need another keyword - whatever is the codename for Versa 2.

Is this correct?  If so what is the missing entry?

Or do I need to get my new clockface released as Versa 1 only and then hope it gets scanned and flagged at some point in the future?