Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't see why Apple would do this when the chromecast is out there...making a useful device and creating strong network effects for iOS and OSX hardware by making streaming anything from those devices onto tvs seems like a wiser choice than bending over for the media companies. It isn't as if labels will pull their music from iTunes Store at this stage of market penetration; if they were going to withdraw their consent they would have done it early.


ChromeCast has been breaking apps written to push to it as well: http://www.engadget.com/2013/09/21/airplay-mirroring-android...

And honestly, if Google had any intention of having generally open access to it, they would have started with DLNA support, which would have allowed many phones to push to it out of the box. Instead expect it to stay heavily locked down and to only provide good support for getting users on to Chrome and Google Play.


Chromecast's API hasn't been finalized and their are huge warnings all over the documentation telling you to not release an app until the API is final. Apple has never released an API and has actively tried to stop things like Airfoil from working.


I'm successfully pushing local content to my Chromecast. The developer in question was using an undocumented API. If you use the documented APIs, things work just fine.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: