Emotely Turns your Phones into Wireless Controllers

  When you say you don't need different apps for different phones ("Controllers are built using just HTML, CSS, and Javascript."), you do need some "native" code at the other end (what is being controlled).

We're trying to make it zero install for the receiving end, but there has to be fallback. But there are certain where it is almost unusable if you maintain that goal.

  Do you have a protocol worked out? Or is there one ready to use?

People always have different definitions of protocols. So to be clear: The transport is abstracted for getting messages between devices. As far as the SDK user's code is concerned it's just getting input events like in a regular input loop.

  Cheers,
  Stephan

Thanks for the questions.