4.0 - Upcoming wearables

VAW.BE said:

However, can we rely on the specs that are given in the simulator.json files in the devices of the SDK? I mean, screen sizes, elevation support, fonts,...? Can we actually start adapting our clocks/apps to these new devices? Or is it safer to wait?

This is just an educated guess, but I think Garmin released these device files so that devs could get a head start on developing for them...

According to the specs I'll also expect a Venu 2 and Venu 2S or something like that. I just hope everything stays as is (screen size, fonts, etc..). So I don't have to adapt everything twice ;)

This has been done in the past - Anyone remember "Tall Watch", "Round Watch", etc?

It's so when the "upcoming  devices" are announced, there are a bunch of apps available in the store for them really fast as this gives devs a chance to do whatever porting is needed before hand..

Awesome! I'm relatively new to the SDK, so never saw something similar happen like this. So I know what to do then

"Tall Watch" became the va-hr, but the real name wasn't used until the va-hr was announced.  This was early 2016.  If I recall, most recently, there was a generic name for the e530 before that was announced.

jim_m_58 said:

It's so when the "upcoming  devices" are announced, there are a bunch of apps available in the store for them really fast as this gives devs a chance to do whatever porting is needed before hand..

Thanks.

flowstate said:

I think Garmin released these device files so that devs could get a head start on developing for them...

Doesn't look like you can test on it, yet, though?

In VSCode it just fails. In Eclipse, it fails over to Venu.

Looks like no CIQ is set, so maybe I should test using the CIQ4 SDK?

Yes, you must use the 4.0 preview 3 SDK to work with the upcoming devices.

For the Upcoming devices, you do want to use the preview 3 SDK.