1Password v8 is a Mistake

@roustem it's also not fair to degrade the experience mac users have in order to serve this market. This tweet, written 2 years ago, is pretty on point today https://twitter.com/rjonesy/status/1195032113340387329.

My absolute no-go is that it will be an Electron app. I am so fed up with Electron apps. They almost always feel wrong. They never behave like native apps. On top of that, they are miserable resource hogs. If you compare Electron apps with their native counterparts, you usually end up with several times the resource requirements.

I will definitely NOT switch to an Electron version of 1Password. Either I have to look for an alternative, or I can continue to use v7 in the future.

1Password on macOS and Android and Firefox.

I think a lot of these complaints could be solved on the mac if they just brought back the native mini menu app.

@shepstl There is a bit of a truth here. I think the business/enterprise side is important for us.

You can see over that over the past few years every major vendor — Google, Apple, Microsoft have built their own password manager. Once something becomes essential, there will be a free option. Remember when Netscape used to sell the web browser and now it is something that we all expect to be free?

If we want to survive, we have to provide something more. Support for businesses (and families!) is a big part of it.

Now, both Dave and I are still using 1Password everyday. We are Mac users and we want to have the best experience for ourselves.

We agonized over the Electron choice and how it will be received by the community. Yesterday wasn't easy and some of the feedback did hit our team pretty hard. I still think/hope we could pull it off and people will come around 🤞 I know I did — while there is still work that needs to be done, I can't imagine using the old app today.

I use VScode at work tooI use VScode at work as well. Apart from the fact that the resource consumption is subterranean bad, it is IMHO the only usable Electron app. But only because editors are a bit special anyway.

And it is NOT enough to programmatically imitate the host system as best as possible. For one thing, I have never once seen it REALLY behave natively.

I don't really have the impression that it's easier to develop NATIVE cross-platform applications with Electron than e.g. via C++/whatever + the respective native GUI kit. Handbrake and Transmission are positive examples where this works. Some have to painstakingly (and unsuccessfully) mimic OS behaviour, others have it easy.

We use Teams at work and the thing is just pain-in-the-ass.And on each platform (Windows, macOS and Linux) the thing behaves differently. The respective feature sets are different. On none (Windows being the closest) does Teams feel native. And here too: it eats up resources without end.

@blankspace The Quick Access option is supposed to be the new mini. It is still in early development and needs more work though, we merged it into main branch just three days ago.

@roustem That's all well and good. You have to say that, you work for 1password. But don't kid yourself. Given the option between a native app and an electron app, with the same functionality, you'd choose the native app every single time. There is nothing that electron can do that native technologies can't, except make it cheaper for you to go cross-platform. Which, hey, that's your decision as company. That's not why we became customers though and that is what will make some of us leave.

@shepstl I appreciate the feedback!

I still think there is a lot of FUD that was built up over the years. I doubt we will be able to change that. I use VS Code over a few "native" text editors on my Mac. I also remember the "native" Hipchat app and it could never come close to Slack or Discord.

And you are absolutely right that the perception and how people feel about the product matters.

@roustem, yeah, but lets say Microsoft first released the app as a native app, had great performance and fit with the OS, then they decided to change to resource-heavy, non-native electron (and be honest, despite VS Code being a decent electron app, and so is azure data studio, it is still very resource heavy. more than it needs to be), you would also be questioning the decision because you know the real drawbacks of electron. I know you have to defend electron because that's what the company chose, but c'mon. You would not choose it if all other options were available. Pretending you would is disingenuous.

I get that @roustem Ugh....

Fine, I'll give you guys until release as I owe you guys that. However, you guys need to give the "quick access" option a lot of love.

Please also let us define a specific vault since it's supposed to be all done by typing.

Example

• Activate via shortcut
• Type {vault}:then the query
• Example work:figma
• the : or whatever key should automatically turn the {vault} into some sort of tag or something. Think of teams or something to give power user's a bone.

I'd be happy with another option as well, this is just an example.

Teams example.

Please also look into the issue of activating quick access snaps you out of the current space. It's supposed to be a quick access menu. It shouldn't force me back to the space 1password is open in.

https://cln.sh/UeLoVo