Feedback on 1Password v8

Hey, folks. Thanks for the comments. I get it, I promise, and I'm frustrated with the current status too.

I just read through some of the internal discussion again, and the main thing that is complicating the effort right now is handling Unicode. We're trying to make sure that search works for all users, not just English-speaking users. Unfortunately, addressing the complexities of searching with Unicode characters has had the effect of making plain old ASCII search worse.

I'm confident we can overcome the challenges, but it's going to take time and effort. And while it feels like a step backwards, I do like that we're starting with a foundation that supports other languages well and building and optimizing from there, rather than treating other languages as second class.

I hope that helps.

1P_Rob - Thanks for your reply. I totally understand that certain features are difficult to code. However, search was working in v7 - flawlessly.

If I typed in "529," I would get ALL results with 529 anywhere in the string of any field.

Now, with v8, I have to type the entire string to get a result. So, a search for "529" will return zero results because nothing in my vault starts with 529. I have to search "Virginia529" to get to my 2FA for the 529 entries.

It worked in all versions prior to v8...that's what's so baffling. Clearly, it's not as simple as "copy the old code into the new program." (CURSE YOU STACK OVERFLOW FOR "TRAINING" ME TO COPY PASTE!)

It really is a step back from v7. A HUGE step back...especially for those of us who use 1Password A LOT because it's awesome and we love the protection it affords us. But, having to remember what exact text string I used to title something can be challenging.

Search works great in the iOS mobile app as well. It's just the Mac Desktop app that is woefully behind.

I think that's what we're all trying to get across here.

Thanks.

1P_Rob I'm using search in v7 all the time and it just works. Of course this is just my limited point of view.
It's not only the missing sub string search in v8. It's the whole search experience in v8 that's just awful. In v7 I start typing and the list is immediately filtered/searched. In v8 I get results that rarely match my expectations and even worse it's not even showing all results but a fraction of it sorted by relevance - whatever relevance may be in this context. On top of that the results are not presented within the list of elements but in a separate window and I have to press CMD+Enter to all results.

Understood but the desired behavior is how it worked in 1PW 7, so there’s that

Hey, @jwessler. Search is one of those things that's been hard to get just right. There are ongoing conversations about how to make it better internally, but from what I understand so far, it's not quite as simple as just matching any part of a string.

We're experimenting with some different approaches and I hope we'll end up with something great, even if it doesn't make it into the first official release of 1Password 8 for Mac.

ref: dev/core/core#9056

@ag_kevin and @ag_ana - any update on the search feature? It's still very much not useful. I have to search by the exact string instead of having search find characters inside of other strings.

Is this a feature you are going to be bringing back or am I just out of luck on getting back to the other search functions?

Thanks so much for your answer!

Thank you for chiming in on this too dtoub, noted :+1:

+1 for having to authorize twice (even if 1PW is unlocked, I have to unlock the browser extension, which is a regression).

Hi @jwessler ,

Thank you for taking the time to write in with your feedback. We've raised a few internal development issues to tackle these problems, and hope to get them solved as soon as possible.

Cheers,
Kevin