What was the final result of this? From a widget, is it possible to get a unique ID for the device? In my case, I wan't to log on a server the devices making http requests and customize the returned data based on the user/device settings on the server.
Why can't you have the server give the client a unique identifier on the initial response, then require the client send that identifier back to the server with every request?
Why can't you have the server give the client a unique identifier on the initial response, then require the client send that identifier back to the server with every request?
I certainly could but I assume that value would be lost if the watch got reset or the widget re-installed. There are certainly ways to attach an ID but all more complicated than if the device id (which already exists in the watch) were to be used.
I was thinking about this just today, but from a develop and testing perspective...
For a developer, they could check the device serial number with CIQ, and if it was the developer's own device, could do things like turn on logging, turn on a feature still in test, or maybe display debug info on the screen for something that's in the app store. (and could also include the S/N of someone testing something for you!)
