Electron

Count me in as another decade-long customer who's disappointed in this change.

Resource usage can be an issue, but it's certainly possible to address, like how Slack was finally able to get memory use down from multiple GB to hundreds of MB with a major engineering effort.

However, what concerns me the most is that this indicates a product direction of breadth versus depth.

For example, taking Slack as an example: while many users have multiple workspaces they need to join, the app has no concept of multiple windows. Like 1Password 8, even opening preferences completely blocks all chats. It's horrible if you're helping a colleague with a question on preferences! Prior chat platforms all had ways to pull channels or chats into separate windows, which Slack (like many Electron apps) completely misses out on. As well, for some reason Slack can't use the macOS spell checker, which means custom words don't carry over. Their support said it was a "limitation of the platform Slack is built on", which of course means Electron. How many of these types of issues will 1Password face with this rewrite?

If anything, I would have expected that the direction would be more, not less native apps. Build a SwiftUI app for macOS! Build a UWP app for Windows! Build a GTK / QT / whatever is great over in Linux-land for those users. Electron should be the "escape hatch" to allow the web UX to work locally for low-use platforms, not the primary target for (what I assume still is) the primary platform.

One more note: our team at work is planning on migrating from LastPass to something else, primarily due to UX issues. In initial discussions, 1Password was a leader due to it's great native apps on iOS and macOS, which is what most of our team uses. With this change, our evaluation will change from "a leader and challengers" to a set of equals competing very much on price, and not quality.