{"id":488,"date":"2013-06-09T17:44:58","date_gmt":"2013-06-09T17:44:58","guid":{"rendered":"http:\/\/www.w3.org\/community\/forum\/?p=488"},"modified":"2013-06-15T07:12:46","modified_gmt":"2013-06-15T07:12:46","slug":"remote-dom-adding-second-screen-remote-screen-capabilities-with-an-open-web-standard","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/forum\/2013\/06\/09\/remote-dom-adding-second-screen-remote-screen-capabilities-with-an-open-web-standard\/","title":{"rendered":"Adding second screen \/ remote screen capabilities with an open web standard"},"content":{"rendered":"

I’d like to propose a new group for a new standard: The Remote DOM<\/a>.<\/p>\n

Apple has AirPlay<\/a>, Google (technically: The WiFi Alliance) has Miracast<\/a>\u00a0– the web has none of that.<\/p>\n

The possibility to have a second screen<\/a>\u00a0opens up interesting possibilities – for instance displaying a presentation on a beamer or a big screen or working with your mobile device, like you would normally work with your PC or laptop.<\/p>\n

Smartphones and Tablets are getting more and more powerful, the PC is deemed dead<\/a>\u00a0– using a bluetooth keyboard \/ mouse and a big screen, one can replace her workstation with a simple tablet or smartphone.<\/p>\n

This makes it interesting for web apps, such as email, document editors, cloud development environments (e.g. Cloud9 IDE) to leverage external screens.<\/p>\n

Similarly to how the Shadow DOM paved the way for custom elements using web technologies, a “Remote DOM” could allow display of portions of the web app to be displayed on “remote” (i.e. “external”) devices, such as screens, Smart TVs, etc.<\/p>\n

We also have a proof of concept implementation:<\/p>\n