Unique User Ident / Serialnumber

There is really nothing in the SDK for this right now. It has been discussed several times, but I haven't seen anything to indicate that it is happening.

Honestly, if you are capable of doing simple web service stuff, you should be able to build a webapp (say in Google App Engine) that would allow a user to create an account (or associate with an existing facebook/google/twitter account) and register each device. Your app could authenticate with the web service, and verify it has access and then cache the unique key provided by the service. It sounds complicated, but it isn't horrible.

Or, of course, you could wait until the functionality is implemented and is made available.

Travis

Travis - can you shed some light if this method would be able to uniquely identify the device each and every time? (including after an uninstall and then a reinstall?)

Take for instance the DWMap application which nessacitates a login and then a pairing. But i don't use this app all the time, only when I want to use it do I install it and then uninstall to save CIQ slots. After each of this process, i will need to repair my device (it's the same watch - to be clear) and then what ends up in the website is multiple instances of the (same) watch having DWMap installed.

It didn't like - "I know that this is the same device and you've just reinstalled me and thus I will re-download all your previous settings and such back to your watch and you do not need to do another round of setup"

things like that.

I personally find this rather distasteful.

It didn't like - "I know that this is the same device and you've just reinstalled me and thus I will re-download all your previous settings and such back to your watch and you do not need to do another round of setup"

It seems to me that would be the ideal situation. Would you rather re-enter your device settings every time you re-install the app?

I haven't actually implemented this, but I'm working on something similar. It works as long as you assume that a user doesn't have more than one device with the same partNumber.

• The watch app would check to see if it has a unique identifier in the object store.
  
• If not, it sends the device partNumber to the web service.
  
• The web service receives a request with the partNumber from the device.
  
• The web service creates an authorization record which has the partNumber and a generated device token.
  
• The web service then sends the device token and a url in the response.
  
• The device receives the response, prompts the user to visit the url with the given device token, and then starts polling the web service to see if the given device token is authorized.
  
• Meanwhile, the user visits the url, and is transitioned through the login process, and enters the device token.
  
• The web service now has an authenticated user and a device token. It finds an authorization record with the given device token that isn't associated with a user, and looks at the partNumber. If the user has an associated authorization record that has the same partNumber, the the device token from the unassociated authorization record is copied to the associated record, and the unassociated record is tossed out.
  
• Upon the next request by the device to verify authorization, the search for an associated authorization record succeeds, and the unique identifier for that record is returned.
  

Travis