Why do some non-touch devices support complications?

flowstate said:

Because accepting a press to open the associated app is just one aspect of complications.

I can understand the confusion from the topic starter. If I were part of the design team I would have suggested 2 api's to implement the functionality. I'm not a big fan of api's that implement more than 1 behavior/functionality. 

The Api is now very much designed from the view of the FaceIt app, but connect iq apps have other wishes than FaceIt apps. 

From a connect iq watch face I would like to be able to launch apps that do not publish complications, where I can see that a faceit app would never want to do this.

As it's already implemented I guess it's too late now, but what I would like to have seen was:

- opening System.Intent for watch faces to handle the exitto behavior 

- a new api for the data sharing aspect

This would allow for a cleaner implementation with a clear view on intent + it would allow you to launch apps that are not complication publishers. 

flowstate said:

The main idea is to show data from the publishing app. 

If I have to choose for me the main functionality is the fact that you can exit to an app, as that's what I like most about the complication class.