Hacker News new | past | comments | ask | show | jobs | submit login

They "block" it by reimplementing the entire videoplayer UI. This is unfortunate because it's inferior to the system provided videoplayer UI, and not just due to lack of AirPlay support.

Notice how touching the screen causes the UI to appear immediately, instead of the delay you'd normally expect. Also, the seek bar is much more sensitive and difficult to use.

I've been wondering why they went through the trouble of trying to make a nearly identical video player UI, but I suppose blocking AirPlay seems like a good explanation.




Apple engineers specifically recommend against reimplementing the movie player UI as well.


That might be the way they block it, but it must not be the only reason for customizing their UI.

For movie playback there is a simple allowsAirplay property, and for mirroring they could draw an empty view (or whatever) across the 2nd screen.


I think a better explanation would be that they used the same video decoding for all devices and tried to implement a UI for that rather than re-encoding their entire library.




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

Search: