Complication Suggestions for Garmin

waterkip said:

I really don't like the naming of this thing. Complication, what.. why? Where in the English language is complication a sharing of data?

As linked previously, it's a term that dates back to mechanical watches:

[https://en.wikipedia.org/wiki/Complication_(horology)]

A complication is a piece of information displayed on a watch face other than the time.

I'm guessing the reason Apple (and others) use the term is because of the implicit association with the luxury mechanical watch market (*). That and it's a pre-existing term of art.

(* Consumers who know what "horology" and "complications" mean are probably willing to spend lots of cash on expensive watches.)

I can't see why it cant be done with on device settings for CIQ watch faces.  That came up in the GDVC yesterday.

There's no reason that you can't do some settings on the phone/GE and this on the device

There may also something that can be done with the new stuff in the watch face delegate -Tap and hold, if I recall.

jim_m_58 said:

There's no reason that you can't do some settings on the phone/GE and this on the device

Do some settings on the phone and some on the watch is the worst scenario for users and for developers who will have to somehow explain to users why it is done in such a ridiculous way.

Look at possibly using hold on the WF and just use that for picking complications.  Setting these up seems to be done on the watch so the list of producers on that watch specific watch needs to be available

MobileDriveway said:

Do some settings on the phone and some on the watch is the worst scenario for users and for developers who will have to somehow explain to users why it is done in such a ridiculous way.

2027: Hot new CIQ System 13 feature - On-Device Mobile App CIQ App Settings (it's phone app settings dynamically generated from your app code running on the watch)

Seriously, it's kind of funny how the "big app settings" feature for CIQ watchfaces and data fields was to allow them to be configured on the watch instead of the phone app. A few years later, the next "big app settings" feature for native data pages and fields was to allow them to be configured on phone app instead of the watch.

I do think on-device settings are great for apps which have relatively simple settings.

flowstate said:

2027: Hot new CIQ System 13 feature - On-Device Mobile App CIQ App Settings (it's phone app settings dynamically generated from your app code running on the watch)

I would settle for them to fix what they already have ! I'm kind of tired of daily routine replying to users who can't save their settings...

flowstate said:

I do think on-device settings are great for apps which have relatively simple settings.

I do think so too, but for bigger settings it becomes too much code and starts taking memory that is already tight. There were cases where I had to remove settings from the watch because the app was running out of memory...

Today's case:

- current settings 1232/2073b

- adding one, ONE boolean 2384/3313: +1kb => 1% mem... One new key in dictionary costs 1kB...

Exactly. Now imagine a "list" setting with 40 or more complications...

And nice feature grouping of settings still doesn't work - I've checked it a moment ago.