We've release an "official flow" for using Electron with Expo for web. It'll also make its way into the SDK 36 docs.
There are a lot of great points and counter points in this thread so I'll quickly address some of them.
> Why Electron?
We're currently investigating react-native-windows but that'll be a huge project. We want to support many different options and give developers the ability to choose which stack they want to use. This means having at least some Electron support, Microsoft is also working on improving Electron a lot so I imagine it'll get much better in the near future.
That said, I think we'd much rather have a solid native solution so we won't be pouring too much time into Electron.
We created expo/electron-adapter so that anyone who wants to use Electron has to opt-in to the workflow. This is important because it'll prevent extra node modules from being installed in every project and the CLI.
> not as much as need for such an expo flow either
- Think of this more like a dead-simple way to use react-native-web with Electron and Webpack.
- Expo SDK does have some native module overlap with Electron, things like FileSystem for instance.