The killer feature of the iOS-based remote is two-way communication between components and the remote. Currently, remotes send commands to commands, but the components do not communicate with their remotes. One of the many consequences of this fact is that one component can be controlled by multiple remotes. This is a disaster in a world where everyone owns an iPhone, iPad, iPod touch, or any combination of these devices. Two-way communication opens the possibility of pairing components to their remotes so that the owner of the component decides who controls the component.
This pairing and two-way communication is something I hadn't considered. Can I discuss this and cite you in a blog post?
Comments
NFC or some kind of always-on exchange protocol may be really cool on this. We'd be able to pay with the watch on our wrist.
Quote:
Originally Posted by Mr. Me
The killer feature of the iOS-based remote is two-way communication between components and the remote. Currently, remotes send commands to commands, but the components do not communicate with their remotes. One of the many consequences of this fact is that one component can be controlled by multiple remotes. This is a disaster in a world where everyone owns an iPhone, iPad, iPod touch, or any combination of these devices. Two-way communication opens the possibility of pairing components to their remotes so that the owner of the component decides who controls the component.
This pairing and two-way communication is something I hadn't considered. Can I discuss this and cite you in a blog post?
I still want my AppleTV (true tv). I love my AppleTV (set top box). I wouldn't mind a watch that is combination of the two though