Suggestion Better Search

pwannh

I would love to see 1Password for Android support the Search function the same way that the Mac version does. On Mac, I can search for any part of an entry's name. On the Android, I must give give the beginning of the name.

Nik

Thank you for the suggestion!

GeneY

Hi pwannh,



Thank you for your suggestion, I 'd like to notice that as a rule the search functionality on Android works and looks different than on iPhone.

I did some thinking on which way to go and decided to stay consistent with Android way.I like to see all items with matching name

instantly shown in the drop as you type. However, if it is so desired by the users, I can implement a wildcard search on the search button click.

For ex entering *Bank Account* will show no items in a drop but on Search Btn click will select My Bank Account and Your Bank Account in the list.

Not sure though if customers find it useful.



Please let me know what you think.

Best Regards,

Gene

Android Developer

jlnd

Better search is definitely needed. I have several logins that all begin with "Google". My main account is "Google main account". On the desktop (and iphone) app, by the time I type "ma" into the search box, the list is slimmed down to a couple of accounts, with the one I want at the top. With the current version of 1Password for Android I have to type "Google M".



The changelog for b1.5.4 says "added wildcard search", but it doesn't seem to work. I tried typing "Main" and "*Main" and "*main" and clicking the magnifying glass icon, but they all resulted in "No Records to show!".



My preference would be that search would show any entry containing the search string in the live updating results without typing a wildcard symbol *. At that point, if you click on the magnifying glass, the search bar would go away and only the filtered records would show (as it does now). I believe this is consistent with the way "Search Contacts" works in the Android contacts app.

GeneY

Hi jlnd,



1.5.4 Beta has a wildcard search option, search on %oo% and Google and Google.com will be selected.

Search on %.com and coogle.com, live.com be selected.



There is no intention to implement a full regular expression support,

however, you got an idea on how to use %.



BTW, notice that iPhone and Android have somewhat different approach to search, in Android we show all matching items

in the list.



Please let me know if you need more info.



Best Regards,

Gene

jlnd

Tried it out and got wildcard search to work. For my example, I type %main% to get the results I was looking for. One word: yuck!



I would prefer it if wildcard searching were the default (as if the %'s were added implicitly).



In order to type a % on the touch screen keyboard, I have to long-press the letter I key. So the routine is I,[wait],M,A,I,N,I,[wait]. And since the wildcard search isn't valid until the final % is typed, I'm likely to spell out the whole word. Whereas if wildcard search were the default, I would type M,A, and by then I'd see my intended target in the list.



...And that's only for people like me who (now) know how to do a wildcard search. The average user isn't going to know or want to figure out the syntax for a wildcard search. He'll just type M,A,I,N (like he always has on the desktop or iPhone app) and get no results and think it's a bug (or worse, he'll think 1password didn't save the login in question).



Also, when you enter the 1password app and login, "All types" appears to be selected (orange background). But as far as I can tell, that has no meaning. You actually have to click it before you can search the "all types" list. In fact, if you click "all types" and then search, it works, but if you just click the search button it goes to the android quick search. I'd like it if as soon as you login if you click the search button it would default to "all types" (as it seems to indicate with the orange bar).

GeneY

Hi jlnd,



First of all, I am glad that wildcard search works the way it is.



Not sure if wildcard search should be a default functionality, many users just want to search on the beginning of string.

I personally search on "My" and expect to see "My Bank Acct1" and "My email Acct 2" and don't want to see

"Database MySQL: credentials". I agree that wildcard "%" is an extra typing but there is also an extra functionality too.

(search on occurrence or on end ).

When we do a google search and type something, it doesn't do search on the string occurrence but searches on the begginning of string.



I expect most users will expect same kind of behavior from 1P for Android Search.

I don't want to introduce a complete RegExpr support, that will be an overkill for majority of users and will create confusion

(most users are not familiar with Regular Expressions).However, some simple wildcard search is definitely helpful.



I completely agree that Help should be updated with the explanation on the wildcard search, it will be done in the next release.



Please let me know what you think

Regards,

Gene









[quote name='jlnd' timestamp='1282160743' post='9113']

Tried it out and got wildcard search to work. For my example, I type %main% to get the results I was looking for. One word: yuck!



I would prefer it if wildcard searching were the default (as if the %'s were added implicitly).



In order to type a % on the touch screen keyboard, I have to long-press the letter I key. So the routine is I,[wait],M,A,I,N,I,[wait]. And since the wildcard search isn't valid until the final % is typed, I'm likely to spell out the whole word. Whereas if wildcard search were the default, I would type M,A, and by then I'd see my intended target in the list.



...And that's only for people like me who (now) know how to do a wildcard search. The average user isn't going to know or want to figure out the syntax for a wildcard search. He'll just type M,A,I,N (like he always has on the desktop or iPhone app) and get no results and think it's a bug (or worse, he'll think 1password didn't save the login in question).



Also, when you enter the 1password app and login, "All types" appears to be selected (orange background). But as far as I can tell, that has no meaning. You actually have to click it before you can search the "all types" list. In fact, if you click "all types" and then search, it works, but if you just click the search button it goes to the android quick search. I'd like it if as soon as you login if you click the search button it would default to "all types" (as it seems to indicate with the orange bar).

[/quote]

jlnd

I agree that full RegExpr support isn't needed. Wildcard search is enough. I'd just like to see wildcard be the default.



I guess my problem is that I've been using 1Password for so long that I've gotten used to the way it has always worked for me. When I login to a new site and 1Password asks me if I'd like to save the login, I don't pay much attention to the title that 1Password gives it, because I know that it's in there and I can get to it later. But on the iPhone version and the desktop version, I've always been able to type a word that occurs anywhere in the title and have it displayed in the list, so when I moved to android and typed in the same old things that I had always had and got a blank screen it seemed like a bug. I think it will to other people too.



A few examples:



Login title: "becuonlinebanking.org"

Search for "bank"

Desktop: Found

iPhone: Found

Android: Not Found



Login title "http://www.godaddy.com"

Search for "go"

Desktop: Found

iPhone: Found

Android: Not Found

Now, of course, the Desktop and iPhone versions found way too many results, so I had to keep typing. But by the time I type "goda", the list is slimmed down to the one I want.



Login title:"forum.agile.ws"

Search for "agile"

Desktop: Found

iPhone: Found

Android: Not Found

OK, I don't really have this one in my 1Password database because I sign in with Twitter, but it's a good example. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' /> And I do have a few login titles that start with subdomains.



Login title: "My T-Mobile Login"

Search for "t-mobile"

Desktop: Found

iPhone: Found

Android: Not Found



I'm not sure I understand your comment about doing a Google search. I'm not sure that's a good analogy. If I search for "obile" it doesn't find results for "mobile", sure, but if I search for "t-mobile" (or even "tmobile" for that matter) it will find occurrences of T-mobile anywhere on the web page. It doesn't have to be the first word on the page. If you're referring to the Quick Search within Android, try searching for one of your contacts by her first name. The contact will be found. Last name? Found too. I have 6 contacts named John, so when I want to find one, I'll start typing his last name. If I could only search by full name that would suck.



Even your example is a good one. If I wanted to find "Database MySQL: credentials" I'd be likely to search with "My". If I wanted to find "My Bank Account 1" I'd be likely to search with "Bank". If I wanted to find "My Bank Account 1" and I searched with "My" it wouldn't annoy me that I could also see "Database MySQL: credentials" because I'd just click on the one I wanted. If the list were to long, I'd type another character or two and it would slim the list down. With live updating search results it's always better to have too many results than too few.



Maybe it's just me, but as more people start using this app I think you'll get more "the search doesn't work" feedback. I'm willing to wait to be proven right or wrong though. Until then, thanks for your hard work.

GeneY

Hi jlnd,



Thank you for your detailed feedback, you have very strong points.

I totally agree that there are always several approaches to any single issue, that is for

you, application users, to decide which one is better and more convenient.



Let us wait and see what other users may add to the Forum on this topic.

Later on I will summarize all feedback about Search and implement the most

popular option.



Thank you again

Best Regards,

Gene