7 ms·

If I were unfamiliar with 1Password, I'd imagine the product is an absolute dumpster fire from your post. In reality, the macOS and iOS clients work fine. I h

If I were unfamiliar with 1Password, I'd imagine the product is an absolute dumpster fire from your post. In reality, the macOS and iOS clients work fine. I have a dozen friends and family members using the product with no complains on those platforms. I surely haven't seen any performance or UI problems that aren't worse on different services. Sure, there is some current confusion between the use of the 1Password X and classical browser extensions, but it's hardly "a mess."

bredren 6y ago
The iOS app is stable and fine. The MacOS native / extension interaction and choice is a mess. From a UX perspective, the single most important thing the product can do is interact with the browser effectively. Embedded in this "feature" is that the product is stable, and responsive in behavior. If you go to the chrome web store, 1password extension page and sort by recently updated, you'll see review after review of 1-3 star, carefully explained problems with this product. https://chrome.google.com/webstore/detail/1password-%E2%80%93-password-mana/aeblfdkhhhdcdjpifhhbdiojplfjncoa https://chrome.google.com/webstore/detail/1password-%E2%80%9... Regarding inconsistent messaging, their support is promising they're working on native app integration but there is no timeline for this. That's why this news is kind of a bummer. The product that I'm subscribed to is competing with this new product for resources.
- jackweirdy 6y ago
  There’s also 2 native apps - if you install from the App Store, you don’t get all the same OTP features as an install from the website download
  - bwoodruff 6y ago
    That is a limitation imposed by the App Store's rules. We're unable to use the screen recording system permission to look for QR codes on screen. Otherwise all of the OTP features are there. You can drag and drop a QR code onto the reader to add an OTP to a record, for example. - Ben, 1Password
    - bredren 6y ago
      Ben, can you address what is going on with the password save UX / convert to login flow?
      - bwoodruff 6y ago
        I can try. Would you mind elaborating on what the issue is? What are the steps you're taking, and what is or isn't happening as expected? I don't work on our extensions directly, and it may make more sense to put you in touch with the folks who do, but I'm happy to take a look.
        autoconfig 6y ago
        Hey Ben, I'm not the person you're replying to but I'm a long time paying customer and I have observed the same problem. See this post https://news.ycombinator.com/item?id=26799379 https://news.ycombinator.com/item?id=26799379 below that explains the issue in detail. Creating new login items is a needlessly complex multi-step process that involves converting a password item to a login item and manually filling in your username. It's really hard for me to understand how you can have an otherwise great product but are failing at what I would argue is one out of the two most important features (creating logins and autofilling).
        bwoodruff 6y ago
        Thanks for the pointer! It looks like my colleague Oliver, who is on our extensions team, replied there. :) I hope what he had to say helps.
        autoconfig 6y ago
        Thank you for the response. I didn't realize there was a different version of the chrome plugin. Will give it a try!
    - joshspankit 6y ago
      I’ve used 1Password for years and had no idea you could drag/drop a QR code on to the reader.
cloogshicer 6y ago
Disagree. Currently the product IS a dumpster fire imo. On macOS, half the time auto fill doesn't work. Saving a password is very inconsistent. When you auto generate a password, the least resistance UI workflow is to first save and fill it - but then when you create the account it is saved again, making it a duplicate. And don't get me started on the Windows client - on my fast gaming PC it takes forever just to unlock the vault. I've cancelled my subscription and won't renew once it runs out.
- bredren 6y ago
  Yes the password save, something that should be the bread and butter of UX is so awkward. It’s painful.
  - bwoodruff 6y ago
    Sorry. :( We've made some big improvements here recently. This post may help: https://news.ycombinator.com/item?id=26805943 https://news.ycombinator.com/item?id=26805943
- karlshea 6y ago
  And the “Convert to login” button is hidden away now for some reason.
dmart 6y ago
I wouldn't say the product is a dumpster fire, but core workflows are a mess. This is how you generate and save a password for a new site: 1) Extension button > Generate Password > Save & Copy 2) After creating account, extension button again > select entry > Edit 3) Click Save in opened modal 4) Click Convert to Login in opened modal 5) Click Edit in opened modal 6) Manually type in the username/email you used on the site 7) Click Save in opened modal 8) Close the modal And this (generating and storing passwords for new accounts) is the main workflow of the product!
- bredren 6y ago
  Yes, this convert to login only after the item being saved makes little sense. It took a few times of catching the button being shown to figure out the pattern of clicks needed to do this fundamental aspect of what the product is intended to do.
  - oliverdunk 6y ago
    There are a few threads related to saving, and I wasn't sure which to jump in to, but I wanted to share a few of the ways we've tried to make saving better in the newer extension. First of all, we have a new "Generator History" section, which contains passwords created by the generator. These are always available if you need them, but don't show up alongside other items, so are less important to clean up. We've also been working on a brand new saving experience which is currently in beta. If we miss a field from the page, you can add it before you save. You can also add tags, and when updating items, see a side by side diff of the changes. There's a screenshot here if you're curious: https://twitter.com/oliverdunk_/status/1382302050369875969?s=20 https://twitter.com/oliverdunk_/status/1382302050369875969?s... It sounds like you have a subscription so if you haven't already, I'd encourage you to give the new extension a try. I totally understand that native app integration might be a requirement for you there, and I'm sorry that it felt like you were getting mixed messaging. Really both things are true - we don't have a timeline for this, since it's a big bit of work and we want to get it right. Support are absolutely correct too though - we're actively working on this, and the integration with 1Password for Linux's beta is the first step, with support for other operating systems very much on our mind. - Oliver, 1Password

bredren 6y ago

The iOS app is stable and fine. The MacOS native / extension interaction and choice is a mess. From a UX perspective, the single most important thing the product can do is interact with the browser effectively. Embedded in this "feature" is that the product is stable, and responsive in behavior. If you go to the chrome web store, 1password extension page and sort by recently updated, you'll see review after review of 1-3 star, carefully explained problems with this product. https://chrome.google.com/webstore/detail/1password-%E2%80%93-password-mana/aeblfdkhhhdcdjpifhhbdiojplfjncoa https://chrome.google.com/webstore/detail/1password-%E2%80%9... Regarding inconsistent messaging, their support is promising they're working on native app integration but there is no timeline for this. That's why this news is kind of a bummer. The product that I'm subscribed to is competing with this new product for resources.

jackweirdy 6y ago
There’s also 2 native apps - if you install from the App Store, you don’t get all the same OTP features as an install from the website download
- bwoodruff 6y ago
  That is a limitation imposed by the App Store's rules. We're unable to use the screen recording system permission to look for QR codes on screen. Otherwise all of the OTP features are there. You can drag and drop a QR code onto the reader to add an OTP to a record, for example. - Ben, 1Password
  - bredren 6y ago
    Ben, can you address what is going on with the password save UX / convert to login flow?
    - bwoodruff 6y ago
      I can try. Would you mind elaborating on what the issue is? What are the steps you're taking, and what is or isn't happening as expected? I don't work on our extensions directly, and it may make more sense to put you in touch with the folks who do, but I'm happy to take a look.
      - autoconfig 6y ago
        Hey Ben, I'm not the person you're replying to but I'm a long time paying customer and I have observed the same problem. See this post https://news.ycombinator.com/item?id=26799379 https://news.ycombinator.com/item?id=26799379 below that explains the issue in detail. Creating new login items is a needlessly complex multi-step process that involves converting a password item to a login item and manually filling in your username. It's really hard for me to understand how you can have an otherwise great product but are failing at what I would argue is one out of the two most important features (creating logins and autofilling).
        bwoodruff 6y ago
        Thanks for the pointer! It looks like my colleague Oliver, who is on our extensions team, replied there. :) I hope what he had to say helps.
        autoconfig 6y ago
        Thank you for the response. I didn't realize there was a different version of the chrome plugin. Will give it a try!
  - joshspankit 6y ago
    I’ve used 1Password for years and had no idea you could drag/drop a QR code on to the reader.

cloogshicer 6y ago

Disagree. Currently the product IS a dumpster fire imo. On macOS, half the time auto fill doesn't work. Saving a password is very inconsistent. When you auto generate a password, the least resistance UI workflow is to first save and fill it - but then when you create the account it is saved again, making it a duplicate. And don't get me started on the Windows client - on my fast gaming PC it takes forever just to unlock the vault. I've cancelled my subscription and won't renew once it runs out.

bredren 6y ago
Yes the password save, something that should be the bread and butter of UX is so awkward. It’s painful.
- bwoodruff 6y ago
  Sorry. :( We've made some big improvements here recently. This post may help: https://news.ycombinator.com/item?id=26805943 https://news.ycombinator.com/item?id=26805943
karlshea 6y ago
And the “Convert to login” button is hidden away now for some reason.

dmart 6y ago

I wouldn't say the product is a dumpster fire, but core workflows are a mess. This is how you generate and save a password for a new site: 1) Extension button > Generate Password > Save & Copy 2) After creating account, extension button again > select entry > Edit 3) Click Save in opened modal 4) Click Convert to Login in opened modal 5) Click Edit in opened modal 6) Manually type in the username/email you used on the site 7) Click Save in opened modal 8) Close the modal And this (generating and storing passwords for new accounts) is the main workflow of the product!

bredren 6y ago
Yes, this convert to login only after the item being saved makes little sense. It took a few times of catching the button being shown to figure out the pattern of clicks needed to do this fundamental aspect of what the product is intended to do.
- oliverdunk 6y ago
  There are a few threads related to saving, and I wasn't sure which to jump in to, but I wanted to share a few of the ways we've tried to make saving better in the newer extension. First of all, we have a new "Generator History" section, which contains passwords created by the generator. These are always available if you need them, but don't show up alongside other items, so are less important to clean up. We've also been working on a brand new saving experience which is currently in beta. If we miss a field from the page, you can add it before you save. You can also add tags, and when updating items, see a side by side diff of the changes. There's a screenshot here if you're curious: https://twitter.com/oliverdunk_/status/1382302050369875969?s=20 https://twitter.com/oliverdunk_/status/1382302050369875969?s... It sounds like you have a subscription so if you haven't already, I'd encourage you to give the new extension a try. I totally understand that native app integration might be a requirement for you there, and I'm sorry that it felt like you were getting mixed messaging. Really both things are true - we don't have a timeline for this, since it's a big bit of work and we want to get it right. Support are absolutely correct too though - we're actively working on this, and the integration with 1Password for Linux's beta is the first step, with support for other operating systems very much on our mind. - Oliver, 1Password