Hey Team,

Not sure if I'm thinkin' this out correctly, but it seems that instead of relying on OpenWatch and since you guys are developing a 1st party app, it'd be nice to expose inPulse-specific APIs for us to develop Android apps (maybe ala Locale/Tracker plugins?) to interface with the watch, but running on the phone. OpenWatch is great, but it seems to me the exposed APIs are pretty limited and I think more designed for the one-line MBW watches, certainly not a full screen monster like our wonderful inPulse

I'm considering a way of getting my (read our) RememberTheMilk shopping lists to the watch, then use the button to indicate "complete", instead of having to keep my phone out or in-n-out of my pocket.

All the heavy lifting would be on the phone (and why not..lol). I think I'm going to take a look at the FB check-in since RTM has similar APIs available, but having gone through that there should be room for improvement (I seem to recall "wrestling with the Facebook API" in the writeup).

Thoughts?
N

Could you give me an example of the entire text that you would like displayed on the watch? We definitely are looking into a push framework, most likely using the Google cloud2device system.

Hi Eric,

RTM is basically a bunch of lists, and the idea came to me seeing the list of emails on my watch.

Top Level list is the different task lists:
Droid
HoneyDo
Grocery
Target

Selecting one of those would yield the members of the list. Say I select grocery:
Cukes
Olives
Lettuce
Carrots

Selecting one of those would mark it completed on the RTM list, so the watch would get repopulated with the updated list:
Cukes
Lettuce
Carrots

RTM would be doing all the comms between the phone and the cloud (mine syncs immediate post update), so I'm just looking for an easy way to reference interaction between the phone and the watch. I figure the custom code (app or plugin, I'm thinking plugin since it would require the Allerta app's presence) would make use of the notification protocol since we wouldn't want to have to load a dedicated app on the watch. Stopping the plugin (maybe a disabling of the plugin) on the phone would cease those specific communications with the watch.

From a grander scale, maybe the Allerta app has a directory it references to run notifications. We stick in a file of code for default notifications, then we as software devs and add to that local directory, enable or disable within the app, etc. I think it would well for RSS feeds, default replies to sms or IM, stuff like that. To make it super-accessible, make the "code" for the plugins be XML in nature. lol.

I dunno - I'm kinda workin' stream-of-consciousness here, so I'm sure it's not nearly clear enough to be actionable, but hopefully you'll get the idea.