Affiliate Disclosure
If you buy through our links, we may get a commission. Read our ethics policy.

Users lobby 1Password to abandon new Electron version

1Password 8 for Mac promises improvements, but will be based on the unpopular Electron platform

Last updated

The forthcoming 1Password 8 for Mac is now in beta, but instead of a regular Mac app, it uses the resource-intensive Electron system — and users are objecting.

Agilebits, the developer behind password management app 1Password, has decided to move its macOS app to Electron. It's part of a plan to make the forthcoming 1Password 8 use the same codebase across all platforms, meaning all features are on every device. But it has caused consternation among Mac users.

"The decision of how to build 1Password 8 for macOS was probably the most complicated one we had to make," wrote 1Password's Michael Fey in a blog post.

"Ultimately we decided for a two-prong approach," continued. "We would build two Mac apps. One written in SwiftUI that targeted the latest operating systems and another using web UI that allowed us to cover older OSes."

Given that an aim was to reduce the number of different versions of 1Password that the company had to maintain, though, doing two Mac ones proved untenable.

"Despite the fact that SwiftUI allowed us to share more code than ever between iOS and macOS," said Fey, "we still found ourselves building separate implementations of certain components and sometimes whole features to have them feel at home on their target OS."

"Ultimately we made the painful decision to stop work on the SwiftUI Mac app and focus our SwiftUI efforts on iOS, allowing the Electron app to cover all of our supported Mac operating systems," he said.

It's possible that Apple's SwiftUI was not yet able to provide all that 1Password needs. However, in abandoning that for Electron, AgileBits is using a platform that is notably resource-heavy and generally less reliable.

The Electron platform made it easy for other apps such as Slack and Discord to have a Mac presence, but performance and stability are typically poorer.

Consequently, 1Password 8 users are objecting to the use of Electron and asking the company to reconsider. In a Reddit AMA with the development team, the issue was raised but reportedly not answered.

"I understand the 1P8 is better on the other platforms," wrote a Reddit user named "Cosste." "But the mac has always been the mac and deserves its own native client. Be it an AppKit app or a Catalyst app made from the iPad version."

"As you can already see, many of us are seriously p***** by the move to Electron, the degrading of the current experience, the new memory usage, the usability problems and the non native feeling," continued the user. "And no, we don't want you to make a better Electron app, we want you to continue to build on the native app."

Other users have complained about the company being "dismissive of the current problems." Users claiming to be on the 1Password 8 beta report that it is slower and less responsive.

It is a beta release, however, and generally final shipping versions are faster. Fey describes all of the 1Password 8 versions as an "incredibly strong foundation" for the next decade of the app.

"We remain committed to creating top tier user experiences on all of our platforms," he concluded.

AppleInsider has reached out to AgileBits for comment.



84 Comments

darkpaw 15 Years · 212 comments

I'll wait until the next version is out of beta and released before I chime in on how it performs, but if it's rubbish I'll switch to a different app. I'm generally quite loyal to companies, but if I get a degraded experience then I'm happy to move away. I think a lot of others will, too.

barthrh 16 Years · 142 comments

Based on my experience with apps using it, Electron is terrible. Flash terrible? Not quite, but working hard towards it. Microsoft is abandoning it for Teams, with the new 2.0 release expected to use 50% of the resources. 1P's native approach to Mac was a huge selling point. If that's gone, then I'll definitely take a look at alternatives.

flydog 14 Years · 1141 comments

SwiftUI and Electron are both unmitigated disasters, but 1Password's explanation for choosing Electron doesn't make sense since SwiftUI is not required to create universal apps. The decision was likely based on cost-cutting/laziness, and 1Password is trying to shift the blame. 

J0na17anT98 8 Years · 11 comments

flydog said:
SwiftUI and Electron are both unmitigated disasters, but 1Password's explanation for choosing Electron doesn't make sense since SwiftUI is not required to create universal apps. The decision was likely based on cost-cutting/laziness, and 1Password is trying to shift the blame. 

SwiftUI is not a disaster. The problem is that many apps that have been here a long time already use Objective C or Swift so adding SwiftUI would be a pain because now you are adding a third language into the mix. For apps that are purely Swift, it’s not that difficult to just wrap the UIKit components to work with SwiftUI until SwiftUI is mature enough to not have a need to do that anymore. This decision to move to electron is purely based on money and laziness as you said. They don’t have to spend as much on development if they can share the same codebase, which sucks because generally doing so results in a poorer experience for everyone. 

bakerzdosen 16 Years · 185 comments

barthrh said:
Based on my experience with apps using it, Electron is terrible. Flash terrible? Not quite, but working hard towards it. Microsoft is abandoning it for Teams, with the new 2.0 release expected to use 50% of the resources. 1P's native approach to Mac was a huge selling point. If that's gone, then I'll definitely take a look at alternatives.

The idea of Teams having a better implementation on the Mac than 1P is almost laughable, but here we are...

Hopefully 1P plans on shifting that money they're "saving" from development to support because they're going to need it there.