The principal for Wear 4 is that the end user should personalize with complications not with designer complications to give a consistent User Experience.
I think you basically want the same as @rzrshrpstudio and @nushio want. That would allow this.
B) Also capability to make a analog stopwatch/chronograph.
A true chronograph watch would require the use of the buttons and those are reserved. There is a stopwatch app that comes preinstalled (at least on Samsung) that is probably a better option
secondary timezone tag (retrieved from world clock secondary zone?)
World Clock is a separate app and I donāt think it has a public API
E.g the timezone tag is now mean for local time zone only
Time zone tag is set to whatever Time Zone is set in the digital clock settings so if you choose to create one that doesnāt sync to device it will show that time zone.
In both case this is not an end user option but doable for your personal use.
The color picker and color being set using tags are already suggested.
I can add the others
For the health ones I can suggest butā¦
[CAL]tag for calories burned.
I can suggest it but this gathered a lot of complaints when it was in the Tizen Based watches because some people want total calories and some people want the Active Calories that Samsung Health has.
[DIST] tag for calculate distance of walk/run
This is part of the health Services if the Health Settings are set to share to Health, If not then it isnāt. I donāt know if they are mandatory. I can suggest them
I understand itās weather licensing but I am just wondering why I can make a complication that allows a user to set the Google default weather app, but I canāt just āhard wireā it into my watch face? there is a difference here that causes a licensing problem? Not meant in any disrespect, I am just genuinely curious about it.
If i am not wrong its because complications are provided by the apps itself. They expose data to the complication via complication inteface,If that made sense?
I was thinking about the stock watch faces included in the official Wear OS 4 emulator image. No need for any low-level APIs or fancy complications.
Edit: To be more precise most of these stock watch faces have a toggle for ābold fontsā (BooleanConfiguration).
Most of those have multiple layouts to choose from (ListConfiguration).
And all color names are localized like ātealā, āpinkā and āsmaragdā (ColorConfiguration displayName).
Edit2: Here are a few screenshots to illustrate what can be done with the full set of Watch Face Format XML:
Both Google Weather and Samsung Weather use The Weather Channel as their provider. As I understand it the license for that agrees to have advertisement in the app when it runs. It does not allow Samsung or Google them to sublicense the Weather API to 3rd parties.
What you can do is create the App with Android Studio and Jet Pack and license your own Weather API Openweathermap.org has a free version with limited end user uses that you could use. This was what was used in the Tizen based watch faces with Galaxy Watch Studio.
What about the ability to have more than 1 .WFS file open at the same time? There are many occasions where I just need to refer to another file while working on a new file to get a code snippet or whatever but in order to do that I have to close that file and open the other one? It would be great to just have files open in different tabs.
The last I heard they were working on this. The new Wear 4 and Watch Face Format changes took precedenceā¦ Iāll remind them this is extremely useful for designers.