home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
General
Chromecast
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Oxan" data-source="post: 1015379" data-attributes="member: 97484"><p>Ah, so you still have three way communication: keyboard/IR-remote/mice/bluetooth-controller <--> Android Dongle <--> MPExtended. That reduces the difference with the Chromecast to two points: the input type ('conventional' remote vs phone/tablet) and where the app runs (the remote vs the dongle). </p><p></p><p>Personally, I think the chromecast wins on both points: I'd much rather use a clueful phone/tablet which can show information and adapt to the context as remote than a conventional remote, and running the app on the remote makes it possible to have different preferences for everyone. However, others can have different preferences and thus want a different solution, and that's fine. However, that doesn't make the other solution better by definition (as you say).</p><p></p><p>Also, what is already developed isn't relevant for this discussion. Adding Chromecast support to aMPdroid and/or WebMP is quite easy and will probably happen <s>soon</s>in the not too distant future.</p></blockquote><p></p>
[QUOTE="Oxan, post: 1015379, member: 97484"] Ah, so you still have three way communication: keyboard/IR-remote/mice/bluetooth-controller <--> Android Dongle <--> MPExtended. That reduces the difference with the Chromecast to two points: the input type ('conventional' remote vs phone/tablet) and where the app runs (the remote vs the dongle). Personally, I think the chromecast wins on both points: I'd much rather use a clueful phone/tablet which can show information and adapt to the context as remote than a conventional remote, and running the app on the remote makes it possible to have different preferences for everyone. However, others can have different preferences and thus want a different solution, and that's fine. However, that doesn't make the other solution better by definition (as you say). Also, what is already developed isn't relevant for this discussion. Adding Chromecast support to aMPdroid and/or WebMP is quite easy and will probably happen [s]soon[/s]in the not too distant future. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
General
Chromecast
Contact us
RSS
Top
Bottom