The sender and receiver SDKs have mature APIs for playing video. The session and media channels&#x2F;objects are well documented and leveraging them on your custom receiver ensures far easier integration on the senders (iOS, android, and web). If you venture out of the cast-a-single-video experience, it can get pretty complicated as there are best practices for how to handle multiple senders, how to fetch a playlist and continue autonomously if the sender disconnects without stopping the cast, and maintaining a good user experience on all senders that represents current state of receiver. You could (and would be advised to) handle all this via the provided &quot;media&quot; channel.<p>More to the point of the article, there is also a custom messaging channel, you can create your own interactive experience (the receiver is just a website displayed in a chrome tab). Here&#x27;s an example of tic-tac-toe: <a href="https:&#x2F;&#x2F;github.com&#x2F;googlecast&#x2F;Cast-TicTacToe-chrome" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;googlecast&#x2F;Cast-TicTacToe-chrome</a>. 
You can already develop a custom receiver for an in-store search feature or something more interactive and playful. 
You can connect to it via the same wifi. 
I don&#x27;t understand what additional value nfc provides in this case as you&#x27;d still need to maintain an open&#x2F;persistent connection to the receiver from the sender, would nfc be able to provide that?