dosyago / browsercontrollers.store

:zap: BrowserController - A new distribution channel for your apps. More control than a browser extension, more lightweight than an Electron app. Just as powerful as Node.

dosyago

Special

browsercontrollers.store's Issues

You're making a game company

You seem to be developing most of the experimental tools that I envision being inside of my Multiverse for the games I'm developing at my non-profit game studio. All projects are going open source after design and prototyping etc, I'm managing marketing and Ai, Ideally having this system as the universal portal to download my apps would be ideal. Unfortunately, my tech knowledge is a novice , beginner if anything so integrating your source code to my project has been a pain. If you ever have time for a call to advise, what would you charge and how do I contact you?

Clarification

There should be 1 browser controller that opens and shuts chrome and manages the devtools port.

This controller can register plugins or whatever they're called.

Alternately they could be the controllers and the manager is the orcehstrator.

In any case there should not be multiple binaries all handling chrome.

There should be one. And the browserctontroller boilerplate is for the plugins to that system.

Basically, it's like go language. You install a plugin by pulling it from source, and running it's node.

You get a little entry in the "plugins" page or whatever where you can switch it off, remove it, whatever.

That's a great idea I think.

Take it further with cloud browser

Eventually this system can be run along side a cloud browser so you can install the plugins to your browser in the cloud.

The "browser interface" (skateboard) for a cloud browser is basically a plugin anyway, a very sophisticated plugin, but one nonetheless.