D2Bravo?!

According to the release notes for the ConnectIQ 1.1.2 SDK, it is already there...

https://forums.garmin.com/showthread.php?292574!

Nice, didn't see that yet.

My guess is that by supporting the abstract 'round-watch' and 'fenix3', we're basically covered. Is this accurate?

Supporting the 'round-watch' doesn't actually mean anything when it comes time to package the app. The round and square watch were originally added way back at the beginning of time so we could release a preview of the SDK before the CIQ supported devices were actually announced. They are simply generic watches. I've created an issue to remove them from the device list.

To support the D2 Bravo you will have to rebuild your app using the 1.1.2 SDK. The screen is the same as the fenix 3 so you should be able to use fenix 3 resources/code. There is some ongoing discussion to support device "families" in the future.

There is some ongoing discussion to support device "families" in the future.

You mean like "Round Watch" and "Square Watch" families? :)

No, more like fenix-based devices, vivoactive-derived devices, etc. :) It's possible that we may have other round or rectangular devices in the futures that have screen sizes that differ from the existing devices.

Just thinking, but wouldn't the best place to handle device families be in the app store? In this case, the device seems to be just like a F3, but to support it, everything it can use will need to be re-compiled and re-submitted to the app store.

Could the app store be made smarter to say "Oh, you have this member of the F3 family, so you get the F3 version!" It would save the recompile/resubmit delays.

That's similar to what we'd like to do, though it's a little more complicated than that in reality. You're thinking along the same lines that we are, though. :)

Just thinking, but wouldn't the best place to handle device families be in the app store? In this case, the device seems to be just like a F3, but to support it, everything it can use will need to be re-compiled and re-submitted to the app store.

Could the app store be made smarter to say "Oh, you have this member of the F3 family, so you get the F3 version!" It would save the recompile/resubmit delays.

But then how could they justify not having a Bravo app for the Fenix 3? Same watch, same software, exclusive app which makes the idea of an app store worthless.

D2Bravo resources

I tried to make a different resource for d2bravo, but it does not work. I created a new folder resources-d2bravo and put image there like for other devices. But when I run my application, I see strange image with distorted colors for square watch.

if you see a square watch then you haven't configured your run target. Simply creating the resource is not enough to tell ConnectIQ which device to simulate.