As Leon says, “casting requires Internet access time. Downloading (I didn’t know this!) And allow the AppID for the recipient URL. After the listing has the download URL and resolves the hostname in the URL to IP address, it no longer requires the Internet IF everything is configured correctly on the local subnet.
For example, I develop applications for home applications. Suppose I registered my application and the user recipient associated with it is located in https://10.0.0.5/basil_app1/reciever.html
(or in the host name that allows public DNS for private IP 10.0.0.5, which I actually use, is the host name).
Then, if my application needs to load other media, it can refer to it either by the already resolved host name, or by IP, served again from the host in 10.0.0.5
It sounds a bit like you don’t know how to set up and interact with a private network and a web server, which is really not a Chromecast problem.
For me, if I had to make a demonstration of Chromecast (for example) on the client’s site and was not sure of the network situation, I would install Chromecast to use the private Wi-Fi network provided by my mobile phone and all the web resources necessary for work from my laptop, again configured on a private Wi-Fi network. Again, this is not really a "throw programming problem."
Basil source share