Sure — Awesome question. Despite being unable to run a browser, we are able to author a fully native (c++) application that is deployed once to the device. This native app is able to use WebRTC (consuming it as a dll — more info here) and render to a display, so it’s able to meet our needs.
It’s probably worth noting that the “no browser” constraint can be thought of as a business constraint, not a technical one. Unfortunately I can’t get much into the details of why that constraint exists at this time.