Design language

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.