There are no “supported devices”, but there is a database of IR commands. More and more I’m using IP commands. Unfortunately, I’m not aware of a general database of IP commands, you need to dig them out from each manufacturer and this can be tedious. I find that IP commands are more responsive, complete, and reliable than IR and you don’t need to fuss with IR emitters. For example, Yamaha MusicCast provides a complete set of IP commands that you can use to essentially duplicate their controller’s data on your screen. ROKU also has a decent set of IP commands.

Lots of nice details are possible with IP commands. For example, many devices can be interrogated. I regularly check Volume levels. This allows the controller in hand to show Volume changes initiated by other controllers. It is also possible for controllers to share data via the cloud.

One of my favorite interactions is with a cable box. I’m very fast when touching channel numbers — often causing the cable box to crash. With TouchControl I can accept the buttons at any pace, then meter them out at a pace that will not crash the box. Of course you can have channel icons too, but you’ll need to pace button presses here too.

I also have a scheme for channel icons that presents scrolling groups of channels. For example: “Local”, “Movies”, “Kids”, “Sports”, etc. Channel icons can be shown in multiple lists, if appropriate. The user simply touches a button, such as “Sports”.  A master database of channels and their artwork is maintained in a very ugly spreadsheet. I have separate columns for Verizon and Comcast. I copy the appropriate column into a file that the HTML button fetches. Changing from one cable service to the other is a single copy and paste. I started this UI approach in Pronto, even used it in RTI, but it was extremely tedious to maintain.

There are still bits and pieces of my Pronto code scattered about.

As I said, you are mostly limited by your imagination.