I just finished banging out a new Electron app (https://getpolarized.io/ https://getpolarized.io/) It's an offline-first app for managing and annotating PDF an

I just finished banging out a new Electron app (https://getpolarized.io/ https://getpolarized.io/) It's an offline-first app for managing and annotating PDF and web documents. The idea was that with Electron I can have direct access to the filesystem and be fully integrated into the browser as well. For the most part it works. The users can easily browse the local filesystem and also access some operating specific features. But let me tell you -it's rather schizophrenic to use something like Electron. It just doesn't know whether it's a browser or a web server and then there's the issue of dealing with process communication within Electron. Chrome is its own process and node the main process and you have to communicate via message passing - not super fun. Now we have PWAs and they're far from idea but it might be that an API like this, along with PWAs, and maybe a bit more functionality could replace Electron for building these types of hybrid apps.