Not entirely sure of the architecture of this app, after a quick look. Using CEF and C++, with a client and a proxy. But where does the CEF sit, and how is it controlled by the client?
I made something similar in Node.JS using headless Chrome, that targets mobile and desktop browsers. The "proxy" runs anywhere, and a client (that runs in the web browser) connects using Remote Debugging Protocol[0], passing along the user interaction intents by converting them to the wire protocol of RDP. The remote browser server then, like this project ( I think ), passes back pixels from screenshots of the rendered web.
It's a safe but not particularly fast way to do it. MightyApp[2] are doing some sort of MP4 streaming of a remote browser, for speed, I think.
I like the retrocomputing focus of this, and the screenshots and image of the modern web running on an old ThinkPad like machine look really awesome. The focus of my project[1] was more an open-source remote isolated browser, for security, and automation uses.
I made something similar in Node.JS using headless Chrome, that targets mobile and desktop browsers. The "proxy" runs anywhere, and a client (that runs in the web browser) connects using Remote Debugging Protocol[0], passing along the user interaction intents by converting them to the wire protocol of RDP. The remote browser server then, like this project ( I think ), passes back pixels from screenshots of the rendered web.
It's a safe but not particularly fast way to do it. MightyApp[2] are doing some sort of MP4 streaming of a remote browser, for speed, I think.
I like the retrocomputing focus of this, and the screenshots and image of the modern web running on an old ThinkPad like machine look really awesome. The focus of my project[1] was more an open-source remote isolated browser, for security, and automation uses.
[0]: https://chromedevtools.github.io/devtools-protocol/
[1]: https://github.com/dosyago/RemoteView
[2]: https://mightyapp.com/