Design language

@claus Ultimately, we’re the vocal minority. AgileBits believes—rightly, I fear—that most users won’t notice; or if they do, they’ll just accept the slow and gradual decline because it doesn’t matter much to them.

@cyberskier From using a dozen different Electron apps in the past, it seems there are several qualities that are simply endemic to the framework. Remember that Electron is just a stripped down version of Chromium plus a Node.js runtime. This goes beyond higher resource use and extends into actual UX. I’m not confident they’re fixable, or at least one app would have fixed them by now.

To the team’s credit, 1PW 8 is easily the most native-feeling Electron app I’ve used. Granted it’s not an especially high bar to clear, but I can tell effort has been put in to make it as close as possible, given the inherent limitations of the framework. Personally? I don’t like it. There have been a lot of heated words in this topic, and I don’t want to add fuel to the fire, so I’ll leave it at that. Right now, I’m considering whether to keep using 1PW 7 or migrate to another service.

A question for the team: Any insights as to why Catalyst wasn’t chosen? It’s also imperfect, but I would prefer to use that than Electron.