Re:Testing Netflix on Android
by bri3d on Wednesday March 14, 2012 @10:49PM
(#3706512)
The media decode pipeline on Android is nearly 100% different from the media decode pipeline on any other flavor of Linux I can think of. I don't know how having Netflix running on Android is really relevant to having it running on vanilla desktop Linux - the effort required is still large and the upside still simply isn't worth it to them, so they don't do it.
[ Parent
| on HN ]
Re:Testing Netflix on Android
by groovy2shoes on Thursday March 15, 2012 @12:13AM
(#3706799)
The decode would be largely the same unless it were written completely in ARM assembly. A quick disassembly of the Android libs suggests that it's largely C++ (based on calling convention and name mangling). In that case it's the UI and the rendering that would be quite different.
Coding a UI and some video isn't a zero-time process, but it's practically trivial (i.e., they could have an intern or two do it).
Releasing a product of any sort is not trivial when you're someone like Netflix - your product needs to be thoroughly vetted by your partners (who are interested in content protection), tested, and supported by real people.
Re:Testing Netflix on Android
by groovy2shoes on Saturday March 17, 2012 @08:19PM
(#3718654)
I never said releasing the product would be trivial, I just conjecture that coding it would be. As far as content protection goes, they already have DRM code that they've already released and their partners have already vetted. Now all they need is a GUI of some sort.