4 ms·

We added spellcheck and text transformations options recently. Our team contributed a few patches to Electron to enable better macOS integration. For example: h

We added spellcheck and text transformations options recently. Our team contributed a few patches to Electron to enable better macOS integration. For example: https://github.com/electron/electron/pull/32024 https://github.com/electron/electron/pull/32024 I believe the UX performance in 1Password 8 is better than any other app we built in the past: https://twitter.com/mitchchn/status/1491253916004147203?s=20 https://twitter.com/mitchchn/status/1491253916004147203?s=20 Would love to learn more about the standard shortcuts that are missing — good keyboard shortcuts is a huge priority to us! -- Roustem 1Password Founder

trvr 5y ago
Not looking for a fight here, but it seems like there is a disconnect between 1Password/AgileBits praising version 8 while also trying to bury the fact that it is an Electron app. It seems like you are proud of what you are building (and that's awesome), but the Releases page for beta [1] doesn't contain the word Electron. 1: https://releases.1password.com/mac/beta/ https://releases.1password.com/mac/beta/
- judge2020 5y ago
  Electron is effectively a UI and code framework, much like SwiftUI or just Swift with AppKit; I don't see why either would need to be a marketing point or referenced in the changelog. 1Password 7[0] doesn't say what it's made in either. 0: https://support.1password.com/explore/whats-new-mac/ https://support.1password.com/explore/whats-new-mac/
  - brailsafe 5y ago
    This is a specious argument imo. The beta does mention that some part of it is written in Rust, why exclude Swift/Objective-C to JavaScript if you're in the business of talking up implementation changes?
- mynameisvlad 5y ago
  Why jump to "trying to bury" if you're not looking for a fight? There are many reasons for not specifying what framework an app is built in, the most obvious of which is that the general public both has no clue what Electron is nor a desire to find out. Just because something isn't listed doesn't mean it's "buried". Like the other commenter said, you don't routinely see users of other frameworks and languages put it front and center, why should that expectation change with Electron?
  - trvr 5y ago
    That's fair. I just found it odd that they specifically called out Rust.
Y-bar 5y ago
That's some good news (though it looks like you linked to another github issue), but my real-world experience unfortunately stands in stark contrast to your claims. I don't know who to trust, my senses or your words. Previous version is noticeably snappier still. Will you add support for increased contrast again? (it was removed in v8, and was one of the many regressions that made me effectively give up on 1Password)
halostatue 5y ago
I have filed a couple of issues on the community board, but there are two things which are dealbreakers to me (most of the rest of the issues — including the attachment data leak — have been resolved). 1. I despise the binding of ⌘- and ⌘+ to zoom, and even more ⌘0 to zoom reset. I know that those are standard Electron things, but there’s absolutely no reason to make them priority bindings for 1Password. Beyond the zoom binding, I find the default size too big, so I am running at two zooms down by default. Every time I go for the ⌘0 (all "displayed vaults" in 1Password 7), my zoom resets because of this nonsense. What would make more sense is to: (a) remove those bindings; (b) let one of the collections or accounts be marked as a _default_ collection or vault and bind the display of the default to ⌘0; (c) offer zoom sizes either in the view menu or preferences; and maybe (d) offer the zoom-in zoom-out functionality only in the menu. 2. I absolutely cannot deal with the fact that preferences, collection editing, and a few other things are pseudo-modals that block the use of every other part of the 1Password 8 UI. It’s the #1 thing that calls 1Password 8 out as an Electron app, and it makes me so not ever want to touch these things, which makes them far less useful on a day-to-day basis. If you are unwilling to fix the fact that these things are garbage, at least enable multi-tab capabilities (I would love to see a tabbed 1Password interface). That allows VS Code to be less immediately annoying. These are in order of annoyance, not priority. I consider the pseudo-modal issue to be more important because it makes the new features that you and Dave speak of unpleasant to configure. Fix these, and I’m back to recommending 1Password 8 wholeheartedly. I’m even missing 1Password mini less and appreciating the replacement a bit more (it’s still not _quite_ as good, IMO, but it’s getting there).
- roustem 5y ago
  Thank you so much for the feedback! 2. It might look silly but we actually had an internal debate about making the preference for floating preference window. I personally do not mind the single window approach because it makes things easier for the non-experienced users. I watched my mother-in-law losing the preferences window when she tried to configure 1Password 7. I know there are certain articles claiming that all Mac apps must have a floating Preferences window but there are quite a few counter-examples as well. Anyway, that preference might still happen. 1. I certainly relate to the pain about muscle memory when it comes to the keyboard shortcuts. At the same time, having an option to easily adjust the zoom settings for an app is such a great feature. I used 1Password on a 13" laptop and on Pro Display HDR and I love the ability to change the zoom factor. I now wish I could do this in every app. Perhaps a solution could be to make all keyboard shortcuts customizable?
tgamma 5y ago
The first thing that I noticed and really bugs me is the absence of the alt key to quickly reveal the password.

trvr 5y ago

Not looking for a fight here, but it seems like there is a disconnect between 1Password/AgileBits praising version 8 while also trying to bury the fact that it is an Electron app. It seems like you are proud of what you are building (and that's awesome), but the Releases page for beta [1] doesn't contain the word Electron. 1: https://releases.1password.com/mac/beta/ https://releases.1password.com/mac/beta/

judge2020 5y ago
Electron is effectively a UI and code framework, much like SwiftUI or just Swift with AppKit; I don't see why either would need to be a marketing point or referenced in the changelog. 1Password 7[0] doesn't say what it's made in either. 0: https://support.1password.com/explore/whats-new-mac/ https://support.1password.com/explore/whats-new-mac/
- brailsafe 5y ago
  This is a specious argument imo. The beta does mention that some part of it is written in Rust, why exclude Swift/Objective-C to JavaScript if you're in the business of talking up implementation changes?
mynameisvlad 5y ago
Why jump to "trying to bury" if you're not looking for a fight? There are many reasons for not specifying what framework an app is built in, the most obvious of which is that the general public both has no clue what Electron is nor a desire to find out. Just because something isn't listed doesn't mean it's "buried". Like the other commenter said, you don't routinely see users of other frameworks and languages put it front and center, why should that expectation change with Electron?
- trvr 5y ago
  That's fair. I just found it odd that they specifically called out Rust.

Y-bar 5y ago

That's some good news (though it looks like you linked to another github issue), but my real-world experience unfortunately stands in stark contrast to your claims. I don't know who to trust, my senses or your words. Previous version is noticeably snappier still. Will you add support for increased contrast again? (it was removed in v8, and was one of the many regressions that made me effectively give up on 1Password)

halostatue 5y ago

I have filed a couple of issues on the community board, but there are two things which are dealbreakers to me (most of the rest of the issues — including the attachment data leak — have been resolved). 1. I despise the binding of ⌘- and ⌘+ to zoom, and even more ⌘0 to zoom reset. I know that those are standard Electron things, but there’s absolutely no reason to make them priority bindings for 1Password. Beyond the zoom binding, I find the default size too big, so I am running at two zooms down by default. Every time I go for the ⌘0 (all "displayed vaults" in 1Password 7), my zoom resets because of this nonsense. What would make more sense is to: (a) remove those bindings; (b) let one of the collections or accounts be marked as a _default_ collection or vault and bind the display of the default to ⌘0; (c) offer zoom sizes either in the view menu or preferences; and maybe (d) offer the zoom-in zoom-out functionality only in the menu. 2. I absolutely cannot deal with the fact that preferences, collection editing, and a few other things are pseudo-modals that block the use of every other part of the 1Password 8 UI. It’s the #1 thing that calls 1Password 8 out as an Electron app, and it makes me so not ever want to touch these things, which makes them far less useful on a day-to-day basis. If you are unwilling to fix the fact that these things are garbage, at least enable multi-tab capabilities (I would love to see a tabbed 1Password interface). That allows VS Code to be less immediately annoying. These are in order of annoyance, not priority. I consider the pseudo-modal issue to be more important because it makes the new features that you and Dave speak of unpleasant to configure. Fix these, and I’m back to recommending 1Password 8 wholeheartedly. I’m even missing 1Password mini less and appreciating the replacement a bit more (it’s still not _quite_ as good, IMO, but it’s getting there).

roustem 5y ago
Thank you so much for the feedback! 2. It might look silly but we actually had an internal debate about making the preference for floating preference window. I personally do not mind the single window approach because it makes things easier for the non-experienced users. I watched my mother-in-law losing the preferences window when she tried to configure 1Password 7. I know there are certain articles claiming that all Mac apps must have a floating Preferences window but there are quite a few counter-examples as well. Anyway, that preference might still happen. 1. I certainly relate to the pain about muscle memory when it comes to the keyboard shortcuts. At the same time, having an option to easily adjust the zoom settings for an app is such a great feature. I used 1Password on a 13" laptop and on Pro Display HDR and I love the ability to change the zoom factor. I now wish I could do this in every app. Perhaps a solution could be to make all keyboard shortcuts customizable?

tgamma 5y ago

The first thing that I noticed and really bugs me is the absence of the alt key to quickly reveal the password.