Is Electron That Bad? | Hacker News

1) Non native cross platform frameworks. This includes QT, JavaFX/Swing, Flutter and others. While they are probably more snappier than Electron apps, you can't really call them native. A lot of the criticism of Electron in terms of UI/UX, can be directed at those as well. 2) Native. This means I need to develop at least 2 different UIs to capture 98% of the market, and being a former Linux user and understanding the struggle of lack of good apps in Linux, I can't ignore that platform. So 3 times the development time, 3 times the bug fixes, 3 times the support. 3) Electron. We all know this one. While I agree that big companies like Slack, Microsoft or Spotify can (and should) invest money in proper app development for each platform; solo developers like me, rarely have the luxury to do so. So I'm left with either choosing one platform to focus on (in my case its Mac since I'm a Mac user) and ignoring all others (at least for now) or settle on semi-native solutions. I'm a perfectionist and I have a vision. But because I'm a power user, doesn't mean everybody else is like me. So to all the people who say that Electron is not native and breaks their UI/UX - is this really an issue among non power users, or is it just us, developers, being frustrated (and I share this frustration) over minor issues like keyboard shortcuts or lack of native Mac text fields?