I was mostly meaning if you have an existing Chrome App or wanted to rely on existing JavaScript libraries.
Electron gets a huge amount of hate on HN but I personally see the native route as very unappealing. With less developer resources (and perhaps a slightly worse UI; I think people really over exaggerate here), you get fairly simple cross platform support, an update system, access to a huge JavaScript ecosystem and your code can be shared between desktop, mobile, web and server-side.
As a developer, I don't see the appeal of e.g. QT, Java or OS specific implementations at all compared to the above. In my opinion, you're trading a small increase in UX and improved system resource usage (which most users won't notice) for a massive increase in developer resources. This is an order of magnitude worse if you're going to do a separate implementation for each platform as well as now you're going to need platform specific libraries, testing frameworks, development workflows etc. for each OS.
Unless you have lots of money, it's not practical to support multiple platforms with a 100% native experience using the minimal amount of CPU and memory possible. If you have an existing web app, moving to Electron isn't a big leap but that isn't the case if you want to have multiple native apps.