UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36

Steps to reproduce the problem:
This feature proposes to simplify the steps for developing, distributing and using desktop applications based upon the webstack.

The same way as "Trusted Web Activity" allows developers to use the web inside Android Apps, "Trusted Desktop Activity" would allow the use of desktop features on the web platform, by using the browser for rendering the UI and nodejs for giving desktop features to the web application (PWA).

With "Trusted Desktop Activity", instead of relying on external tools like nw.js/electron, a user may give a PWA access to nodejs API directly from the webpage.

The communication between the browser and nodejs could be done via the process pipe via  a RPC system, the same way as googlechromelabs/carlo (1) is doing, but instead of launching chrome from node, it would launch node from chrome.

The chrome devtools could be used to debug the application on the node side as well, like GoogleChromeLabs/ndb (2)is already doing, but directly from within the browser.

The already installed nodejs of the OS could be used, or down the line, a streamline version of node independent of the VM could be shipped with chrome.

On other browsers, this node version could work with other VM like it is already demonstrated with node-chakracore for the edge browser.

(1) https://github.com/GoogleChromeLabs/carlo
(2) https://github.com/GoogleChromeLabs/ndb

What is the expected behavior?
This would allow for in-browser cross-platform distribution of desktop applications and give more capabilities to actual PWAs.

What went wrong?
The issue solved is the one of the actual complexity of developping and distributing cross-platform desktop applications built upon the webstack.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 70.0.3538.102  Channel: n/a
OS Version: 10.0
Flash Version: