1Password v8 is a Mistake

Is it possible, not to upgrade to 1p8 and remain on version 7 forever? I see version 8 is a step backwards with a lot of issues and you have killed the mini.

1P_Rob

Unfortunately the use of Electron is inherently a mistake - it has never worked well on macOS and will never work well on macOS.

Hey folks, sorry for the delay, we've been a bit swamped. :)

@FCNV polish and performance are things we'll continue to improve through the early access and beta periods. We're certainly not done yet. As for consistency with the OS, we're doing some things on Mac like the beautiful translucent sidebar that not even version 7 has. But overall, you are right, we've made a decision to have consistent design language across our apps.

How long do you plan on supporting 1PW7 on the Mac before forcing customers to switch to 1PW8? I’d be willing to switch from Dashlane if I had enough time to see how this all shakes out.

@jlsobraske there aren't any plans in place to end support for 1Password 7. That's not to say it will never happen, just that it's not something we're looking at right now. Version 8 is not even likely to ship this year, so there's plenty of time to get your feet wet and see what you think.

gussic thanks for the kind words, and I'm sorry to see you go. I similarly hope we can prove with time that using Electron is not inherently a mistake. :)

Hi all

If you reach out to the billing team they will work with you to give you pro-rata refunds on your subscriptions.

I hate to do this but it seems the 1P Team aren’t really hearing the feedback - I suspect the only way this will change is if people start voting with their feet and wallets.

To the dev team I am sorry, you guys are awesome and seem like great people but this Electron and refusal to acknowledge you’ve done the wrong thing/made a mistake is just a deal breaker.

I sincerely wish you the best of luck - if you decide to dump electron and do macOS properly I’ll be back.

Cheers

editing as my other post FINALLY showed up.

Thanks for the link to the video, roustem . Definitely more than just a “web app.”

For me, the biggest requirements are that my password app is highly performant (i.e., no latency in either the UI or the functionality) AND consumes minimal resources. The look and feel are less important (just don’t make it too cartoon-y like Microsoft’s apps).

How long do you plan on supporting 1PW7 on the Mac before forcing customers to switch to 1PW8? I’d be willing to switch from Dashlane if I had enough time to see how this all shakes out.

roustem

Again, I think you are in a dangerous echo chamber here. I'm not personally taking the caveman stance "Electron app bad!" but definitely understand the criticism. I actually don't care what you write it in. I just use it for password management, not rendering Pixar movies. But I still think it's important that whatever language or framework you use, it:

1. Is polished in ways your previous apps were and this one is not.
2. Feels consistent with the OS experience it is on. I know you want to standardize the look across platforms because it is easier, but there is a benefit to making it feel whole with each OS. Mac users value this experience, as you may know.
3. It is performant. We've seen reports of this thing taking up 3-5x resources as 1Password 7.

Please don't be dismissive of these things just because it makes it easier to forge forward with your roadmap. I know it sucks now, but someday you'll be able to look back and tell the story about the time you made a mistake with 1Password 8, listened to the feedback, and made the right decisions with the roadmap and product, even if it wasn't the easy decision. The same way Mark Zuckerberg talks about their misstep with web apps on mobile and t

roustem: I took the time to watch it. Great presentation to show the effort necessary to rip out all of the things and solve the issues nobody asked for when writing a solid application (Node, Browser, code injection as a feature, ...). But I kept asking myself why you would want to do that? You wouldn't have had any of those challenges (but others) when going for native apps for every platform.
Definitely and interesting talk that mentions a whole lot of issues and reasons around why not to use Electron. There was no mention of even a single security benefit it might bring. Is this because there is none?

And to go with the end of the talk: It might not be impossible to write a secure and good Electron based app - but it's possible to do it without Electron as well.

@jlsobraske Thank you ❤️

Your comment about the web app reminded me about the talk that we did at the NorthSec conference this year. I think if you have a few minutes to watch it you will see that the new 1Password 8 is certainly not a "web app":

https://www.youtube.com/watch?t=5110&v=_P6qI4ahBVk&feature=youtu.be

roustem

So far, the main complaint is that "it is an Electron app, and it is unacceptable to me because I am a Mac user". There were a few valid points about memory usage and a few notes about visual elements. The new mini (Quick Access) is obviously not finished but it will be. What else am I missing?

Here is a list (note these can/are either bugs or issues with the new format)

1. touch Id not automatically firing
2. the padding, lack of dividers making viewing content difficult. Again I can't stress the absolute ridiculous padding. See picture below
3. lack of native UI components. Why is everything inside the main window. Please separate at least some on the critical elements. The "+ New Item" is a huge one. There are other things I could nitpick but the dropdowns are such a pain in the ass.
4. you've switched how user's switch vaults. The new process is more button clicks, overall it's just a worse design. Either switch it back or let us decide. It makes no sense why it was moved as the old way was absolutely perfect. It also gave us a visual que of what vault we were currently on. With "Vaults" minimized, we have no idea except the text in the search bar.
5. The performance lag, which you've already said you'll look at but it's fairly bad and a massive step backwards
6. quick access not being able to be summoned on any other space. This is huge, again, I've spoken about this a lot but I'm just grouping all the complaints I have // have seen into one large comment. This absolutely needs to be fixed, it's awful to use currently.
7. I still disagree with 1P mini being dropped for quick access, so I'm putting this bullet point here and will die on this hill.
8. quick access at the VERY least needs to be summoned via one click in the menu bar (easy fix)
9. There is an absolutely hilarious bug when you're using 1P8 and RDP. If you summon 1P on top of your RDP full screen, the app somehow merges with RDP. Mission control can no longer access or see it. It's maddening. See image below.
10. quick access not allowing vault changes
11. no local vaults (roustem, we've already have convo's about this so I'll leave it)
12. no QR scanning (I know it's a beta)
13. no custom shortcuts (I know it's already an issue being worked on)
14. setting modal instead of windows. I'm sorry but I hate them. They remove the ability for me to multitask and are so jarring in macos as nothing else uses them.

There are others but It'll look like I'm just fishing for complaints if I list them.