The Cast button in Yonto Player's phone app looks like one feature. Behind it are three receivers that have almost nothing in common: a Chromecast, an AirPlay screen and a DLNA TV. They speak different protocols, find the phone in different ways, and play different files.
This post is about the part I find most interesting, which is not the protocols. It is the question every cast has to answer before it sends a single byte: what exactly should the receiver be given?
The receiver fetches the video itself
All three work the same way at the top. The phone does not push video frames to the TV. It tells the receiver an address, the receiver fetches the video from that address, and the phone becomes a remote with a play button, a slider and a stop button.
So the phone has to answer two things first. Can the receiver reach the video where it already is? And can the receiver actually play what it finds there?
For the first one, the app serves the video itself when the receiver cannot just fetch it.…