Design language

Hey @StevenBedrick

This works in 1Password 8 for Mac as well. :)

Ben

This would be a really good opportunity for Quick Answer to step up to the plate. Not only should it be contextual related to the app and/or webpage that you’re on, it should have contextual options and adjustments based on the item type. I just searched for one of my credit cards and it had ⌘ShiftC to copy my password. Now, maybe that means my PIN (but should probably be the CVV as that is what is required far more often), but that label should not be static. The right arrow shows me this for the same credit card.

Great feedback, austin! I am sure we could do this better.

Quick Access is completely useless compared to 1Password Mini (it should never be searching all vaults unless that is what I tell it to be searching; I have a collection that contains the vaults I want searched; it should allow switching between collections or accounts).

The work already started to get this improved.

Having read this entire thread, I can see that I'm in the minority but I really like new design. It feels cleaner and more modern to me, and if I'm being honest that is probably because my UIs tend to look the same (soft colors, a little extra whitespace, etc).

Obviously that is as subjective as everyone else's opinion.

I can't argue with the Electron opinions though: it is hard to find a shining example of Electron-based UIs on the Mac. On Windows, terrible UIs are so common that most people don't even notice them; Mac users are quite a bit more picky in that regard.

I hope that 1P ends up being one of the (very, very few) standout Electron apps in the world because its really is my favorite password manager but it's going to be an uphill battle. Look at the wreck Evernote made of its Mac user base attempting to do the same thing. What 1P might have going for it, is that it's a simpler application. There are less functions, less menus, less overall complexity.

So here's hoping you pull it off!

Interesting to see how picky many users seem to be - I see differences in UI, but I simply use the software and don't really care about these minor app aspects. Important is the functionality of an app. If edges are rounded or not, if scrolling has momentum, if ui elements have animations - this is totally unimportant for my perception of an app.
Important for me are facts:
- does the app do for what I got the app
- as password manager, is the app designed with security in mind
- the app is not complicated to understand
- are the most used functions fast and convenient to use

If an app is beautiful, it's nice, but a password manager doesn't need to be beautiful. I don't buy a password manager because it's beautiful or more beautiful than a competitor. I get it, because it's fulfilling its role as password manager better than its competitors.

I feel AgileBits would be criticised whatever they did. They had released 1PW8 for Linux, which was well worth doing, and also for Windows, which was probably also worth doing. They had tried to produce a native version for Mac using SwiftUI but failed (I don't think anyone has said why, but it may be a problem with SwiftUI itself). If they had started again with another approach, or waited until SwiftUI worked better, then they would have got loads of criticism for leaving Mac users behind compared with Linux and Windows users. Releasing an Electron version was probably their best option, even though it is not very satisfactory.

I definitely agree about the drop downs. The native drop downs already exist - they appear when you right-click. The left-click menus should use those same native drop downs. It's strange to have two different looking menus that do the same thing.

On the subject of menus and command discoverability, one advantage of using native OSX menus (vs. in-Electron simulated menus) is that standard OSX menu items are automatically searchable and discoverable using the system-wide "Help" menu. So in 1P7, if I am not sure whether a given command lives under "File" or "Item", I can instead select the "Help" menu, start typing the command's name, and then by hovering over the matching search result, I will be shown exactly where to find the command. I've attached a screenshot but it's not an ideal way to demonstrate the behavior. It's one of my favorite subtle features of Mac OS, though- it's incredibly useful!

1P_Rob Ideally, the lack of contextual edit menu options as shown by @KirkMcPike will be considered a regression. It is a regression in functionality and should come back in some way, even if it isn’t in the menu (the items aren’t very discoverable there, but I do consider the lack of menu items as compared to 1Password 7 a step backwards).

This would be a really good opportunity for Quick Answer to step up to the plate. Not only should it be contextual related to the app and/or webpage that you’re on, it should have contextual options and adjustments based on the item type. I just searched for one of my credit cards and it had ⌘ShiftC to copy my password. Now, maybe that means my PIN (but should probably be the CVV as that is what is required far more often), but that label should not be static. The right arrow shows me this for the same credit card.

Even worse, it show the exact same thing for a document, which literally has nothing that can be operated on that way. I’ve raised other issues about the regressions for document handling (save to the ~/Downloads folder should not be the default option, although it should probably be an option), but this is somewhat ridiculous.

I think that there's been way too much assumption of bad faith by commenters; I do think that this public early access release was way too early because while I’m successfully using 1Password right now, it’s only because I’ve installed all of the other pieces in all of the other browsers and the new(-ish) Safari extension. My familiar keystrokes are missing. Quick Access is completely useless compared to 1Password Mini (it should never be searching all vaults unless that is what I tell it to be searching; I have a collection that contains the vaults I want searched; it should allow switching between collections or accounts). The modals block use of the application in ways that are fundamentally wrong, especially for a Mac app.

I think things can be improved. But there are flows that are so substantially broken that when I am done with my testing here, I will be going back to 1Password 7 and the other browser plug-ins and not upgrading again until I see that a number of the wrong-for-Mac and simply-wrong design items here are resolved. What I’m not sure of is that you can meaningfully have a single Electron codebase that runs on macOS and Windows and Linux. The latter two? Sure. The two types of GUI systems work similarly enough that it really doesn’t matter. If you fix the things that I and others have suggested, you’re not going to see any benefit from a single codebase.

1P_Rob: "... and the reason we have an early access is to get feedback to guide our next step."
I am sorry, but this is not an "Early Access" version! Early access would have been before Linux/Windows, sometime in spring/early summer. But not releasing it the month before the final version will be released - and more or less all GUI and functionality is "written in stone".
For me it seems that you knew that Mac user will complain a lot (as we can see now), but now it is easier to say that the final v8 will be (more or less) as it is now. No chance to go in another (and better) direction.

Thanks Rob, and that makes sense...Catalina broke a bunch of stuff. Good news is that Mojave will be EOL in October 2022, so that's not that far out. Is it really worth all the electron effort/pushback for something that has a one-year overlap? 1P7 could easily cover that as it dwindles.