Watchface: Glance

zener79 said:

Actually, I don’t think it’s too complicated, because from what I understand the developer frinkr is simply leveraging the complications exposed by a widget:

Yes, that is one of the ways to do it. However, I prefer not to use widgets from other developers - I don't want my apps to depend on anyone who might stop supporting their apps at any time. If I do it, I'd create my own widget.

zener79 said:

If you’d like to implement it, I’d be happy to help test and debug this feature.

Thanks, I'll keep it mind if I decide to do it.

you don't need to depend on other app or widgets. You could just allow third part complications to be used, like many others watchfaces do.

Please check the attached image from the "Fenix 8 V2" settings

https://imgur.com/a/sDq6WC0

I don’t think I expressed myself clearly… You don’t need to depend on other developers. It would be enough if you simply allowed the use of third-party complications in general. No additional dependencies, just more data available for your watchfaces.

zener79 said:

I don’t think I expressed myself clearly… You don’t need to depend on other developers. It would be enough if you simply allowed the use of third-party complications in general. No additional dependencies, just more data available for your watchfaces.

You don't understand how it works. I didn't want to go into details, but it looks like I can't avoid it.

Lets say developer of the CGM widget reads a bad review and doesn't update his app for the new watches, or he changes the name of the published complications, or does any of dozens of other things that will break functionality on my side. I can't fix it until he does, but you will ask me, "why it doesn't work anymore in the watch face I paid for"? That is unacceptable for me.

Thanks

Yes, I see your point, I’m an IT professional too.

You shouldn’t say that your application supports CGM widgets or other external dependencies. You could simply expose the third-party complications in the field selection, as shown in the screenshot above, so that they appear in the list. Nothing more.

If you want, you can also make it clear that the functionality of third-party complications does not depend on you and that you’re not responsible for them.

At least that’s what I would do

Thanks anyway, and keep up the good work

zener79 said:

Yes, I see your point, I’m an IT professional too.

zener79 said:

You shouldn’t say that your application supports CGM widgets or other external dependencies. You could simply expose the third-party complications in the field selection, as shown in the screenshot above, so that they appear in the list. Nothing more.

The way it is done in the screenshots you sent, is not the best - name of the widget and a specific complications from it are hardcoded in the app settings. It works well if you own the widget, but otherwise I would do it differently - universal metric for all kinds of widgets. I'll put it on a TODO list. Thanks