Like many Mac users, I was greatly disappointed to read that 1Password is moving to Electron. I firmly believe that Electron is a bad framework for app development, and the 1Password 8 beta does not change this opinion. I’ve compiled a list of issues, as I see them. Some are endemic to Electron, while others are simply stylistic choices by the dev team. I will try to omit complaints that are purely personal preference, such as specific color usage.

\n
• The lack of rubberband/elastic scrolling is jarring and unpleasant.
\n
• There isn’t enough visual feedback that the window is out of focus. In particular, the “New Item” toolbar button should fade to a lighter blue when unfocused.
\n
• Many interactions in the app do not have the animations they should, including list expansions, menu displays, checkbox toggling, and modal dialogue appear/disappear.
\n
• Unnecessary reliance on modal dialogues is antithetical to native Mac app development. In particular, the “Preferences” and “About” windows should be … well, windows, not modal dialogues.
\n
• It is unusual for a Mac app to have the “About” page be part of the preferences dialogue.
\n
• When unfocused, 1PW 8 lacks hover states. In order to copy a field when the app is unfocused, you have to click into the window, then click the field again. 1PW 7 only requires a single click and properly displays hover state when unfocused.
\n
• 1PW 8 no longer shows the number of items in a tag/category.
\n
• There is seemingly no longer an easy way to mark or unmark an item as a favorite.
\n
• The account name at the top of the sidebar has a disclosure triangle in the down position, indicating that clicking it will collapse the sidebar entries for that account. Instead, clicking it brings up a popover menu with various actions. (I don’t know whether this behavior is different when you have more than one account. My point is that this behavior is unusual for this type of UI element.)
\n
• The app uses almost 2x the memory footprint of 1PW 7 and 10x(!) the idle CPU usage.
\n
• The app is noticeably slower. Scrolling a long list introduces a delay in displaying icons that is not present in 1PW 7. Additionally, there is flicker and occasional slow loading when changing filters, vaults, and tags. (1PW 7 also has flicker at times, notably when changing login items. It’s far more prominent in 8, however.)
\n
• There’s too much list padding. With windows of identical dimensions, 1PW 7 shows me 10.5 items; 1PW 8 shows me only 7.5.
\n

Are these things ultimately minor? Yeah. Complaining about a preferences window becoming a modal dialogue is about as first-world a problem as you can get. At the same time, I’m paying money for this, and now it feels like I’m going to spend money on a downgrade.

1Password 8 is probably the most native-feeling and best Electron app I’ve used, but that’s like saying the McDonald’s by Disneyland is the best McDonald’s I’ve eaten at. I’ve been a 1Password user for years (I started with 1Password 3) and always held the app up as the only app I unreservedly considered worth a subscription. Now it’s pretty likely I’ll move to something else.

1Password Version: 80200056
\nExtension Version: Not Provided
\nOS Version: macOS 11.5.1

Like many Mac users, I was greatly disappointed to read that 1Password is moving to Electron. I firmly believe that Electron is a bad framework for app development, and the 1Password 8 beta does not change this opinion. I’ve compiled a list of issues, as I see them. Some are endemic to Electron, while others are simply stylistic choices by the dev team. I will try to omit complaints that are purely personal preference, such as specific color usage.

\n
• The lack of rubberband/elastic scrolling is jarring and unpleasant.
\n
• There isn’t enough visual feedback that the window is out of focus. In particular, the “New Item” toolbar button should fade to a lighter blue when unfocused.
\n
• Many interactions in the app do not have the animations they should, including list expansions, menu displays, checkbox toggling, and modal dialogue appear/disappear.
\n
• Unnecessary reliance on modal dialogues is antithetical to native Mac app development. In particular, the “Preferences” and “About” windows should be … well, windows, not modal dialogues.
\n
• It is unusual for a Mac app to have the “About” page be part of the preferences dialogue.
\n
• When unfocused, 1PW 8 lacks hover states. In order to copy a field when the app is unfocused, you have to click into the window, then click the field again. 1PW 7 only requires a single click and properly displays hover state when unfocused.
\n
• 1PW 8 no longer shows the number of items in a tag/category.
\n
• There is seemingly no longer an easy way to mark or unmark an item as a favorite.
\n
• The account name at the top of the sidebar has a disclosure triangle in the down position, indicating that clicking it will collapse the sidebar entries for that account. Instead, clicking it brings up a popover menu with various actions. (I don’t know whether this behavior is different when you have more than one account. My point is that this behavior is unusual for this type of UI element.)
\n
• The app uses almost 2x the memory footprint of 1PW 7 and 10x(!) the idle CPU usage.
\n
• The app is noticeably slower. Scrolling a long list introduces a delay in displaying icons that is not present in 1PW 7. Additionally, there is flicker and occasional slow loading when changing filters, vaults, and tags. (1PW 7 also has flicker at times, notably when changing login items. It’s far more prominent in 8, however.)
\n
• There’s too much list padding. With windows of identical dimensions, 1PW 7 shows me 10.5 items; 1PW 8 shows me only 7.5.
\n

Are these things ultimately minor? Yeah. Complaining about a preferences window becoming a modal dialogue is about as first-world a problem as you can get. At the same time, I’m paying money for this, and now it feels like I’m going to spend money on a downgrade.

1Password 8 is probably the most native-feeling and best Electron app I’ve used, but that’s like saying the McDonald’s by Disneyland is the best McDonald’s I’ve eaten at. I’ve been a 1Password user for years (I started with 1Password 3) and always held the app up as the only app I unreservedly considered worth a subscription. Now it’s pretty likely I’ll move to something else.

1Password Version: 80200056
\nExtension Version: Not Provided
\nOS Version: macOS 11.5.1

@FezVrasta

We found an unused animation that was running constantly in the background, eating up CPU time. We've removed that. The change should be in the latest nightly build. Please let us know if the higher than expected usage continues after you've had a chance to try a version with this change.

Ben

Thanks for the encouraging words, @Generic1PasswordUser! I don't have any contacts at Microsoft, but I'm very glad you like the direction 1Password 8 for Mac is headed. Stay tuned, there's plenty more to come. :)

Well I have to say, I'm coming around to version 8. I've just got a new M1 Pro and performance is really good, especially for an electron app. I also switched to the Nightly builds and I have to say I've been pleasantly surprised.

Would I like a truly native app? Sure, but after seeing the progress of v8 on the Nightly builds I may finally have an electron app that is good!

(BTW, please can you inform Microsoft how you've done this as they're very much in the terrible Electron camp with Teams.)

Hey @FezVrasta - no current plans to release an SDK for our back-end, no. Also, just FYI, we no longer use 1Password X for the current browser extension; it's just called https://support.1password.com/getting-started-browser/.

@cantgetagoodsn that's a nice list of applications or to be more correct websites / wrappers for websites. But none of them has created a desktop program or application. So you are comparing different things.
\nI think absolutely no one including Apple is expecting developers to follow the HIG exactly word by word. But there is a huge difference between interpreting the HIG in order to optimize the UX/UI or completely ignoring the most basic UI principles like closing a window top left or top right.
\nI've been using the early access version almost from day one on a separate partition/test installation and whenever I switch between my 1PW7 installation and the early access version I'm more than happy to leave early access as soon as possible. We got plenty of updates but not a single one has really changed even small parts of the UI on macOS to make it feel more naturally. And even pretty big regressions like the broken search, non working shortcut assignment on non English keyboard were fixed.

@Lars the home app is indeed a pretty bad example of Apple's own apps. Ironically it's a badly ported catalyst iOS app quite similar to AgileBits Electron approach with it's custom UI.

@soshiito Some of the best cross-platform apps are at once familiar across platforms, but also adapt to each platforms specific UI guidelines. A perfect example is Microsoft's own Office Suite. And Mac users aren't \"fanatics,\" but we do appreciate good design more so than Windows or Linux users - something that AgileBits used to share.

The standalone browser extension

@FezVrasta : What is 1Password X?

I just wanted to share my feedback on 1Password 8.

Right now it uses 370 MB of RAM on my MBP (M1 Max), and, idle, it uses 6.3% of CPU...

For comparison, 1Password 7 takes 84 MB of RAM and uses, idle, 0.1% of CPU

\n

Is this expected? Honestly I don't feel comfortable running a software that provides such \"simple\" functionalities but takes so much resources. If 1Password 7 is going to be deprecated I'll probably switch to the 1Password X in order to save some resources.

The problem with Electron is that 1 Electron app runs fine, two Electron apps run fine, but right now I'm running: VS Code, Slack, Linear, and 1Password 8. With an average of 300MB per app, I need 1.2GB of RAM just to run these 4 apps. Of course, that's actually way more, since VS Code takes almost 1 GB alone, Slack is at 400MB, and Linear, luckily, is \"just\" at 220MB...

I'm wondering if you plan to release a public SDK for the Rust backend so that third parties can write their own native UIs on top of it?

@cantgetagoodsn - thanks for the observations and the kind words; I've passed them along. And FWIW, I agree -- Apple has always excelled at design, but following the HIG to the letter isn't something even Apple themselves do (we've mentioned the Home app already at least once in this thread).