Search address bar function is confusing to new users

tzarebczan commented

2017-10-11 23:30:21 +02:00

(Migrated from github.com)

The Issue

Many users who initially try to search will type in the term(s) and then click enter. When this happens, it goes to the exact claim typed. The search function works as expected when something is typed, but enter is not clicked.

Would be awesome if we could add some type of hint to clear this up in the App or find some other UX friendly way to convey the search functionality.

## The Issue Many users who initially try to search will type in the term(s) and then click enter. When this happens, it goes to the exact claim typed. The search function works as expected when something is typed, but enter is not clicked. Would be awesome if we could add some type of hint to clear this up in the App or find some other UX friendly way to convey the search functionality.

btzr-io commented

2017-10-12 03:20:42 +02:00

(Migrated from github.com)

why don't just type the exact uri?

why don't just type the exact `uri`?

btzr-io commented

2017-10-12 03:21:39 +02:00

(Migrated from github.com)

I mean don't auto add the lbry:// to the search...

I mean don't auto add the `lbry://` to the search...

tzarebczan commented

2017-10-12 03:23:25 +02:00

(Migrated from github.com)

Both features are needed... They are 2 different use cases for the same component.

btzr-io commented

2017-10-12 03:29:21 +02:00

(Migrated from github.com)

What I mean is that -> always do search unless user type the exact uri lbry://cats:

User search-query: cats -> multiple relevant results...
User search-query: lbry://cats -> Go to uri...

What I mean is that -> always do search unless user type the exact uri `lbry://cats`: - User `search-query:` cats -> multiple relevant results... - User `search-query:` lbry://cats -> Go to `uri`...

tzarebczan commented

2017-10-12 03:31:48 +02:00

(Migrated from github.com)

I think it's useful to be able to type @lbryio and get the exact claim without going through a 2nd click. I thought it was a feature lol. I could be wrong. I'll defer to @kauffj

👍 1

btzr-io commented

2017-10-12 03:41:15 +02:00

(Migrated from github.com)

@tzarebczan then I guess we can add an exception for channels

tzarebczan commented

2017-10-12 03:45:52 +02:00

(Migrated from github.com)

And any inputs with the full claim information (claimname#claim_id or claimname:sequence)?

Are there more modifiers? I'll document it in a FAQ

And any inputs with the full claim information (claimname#claim_id or claimname:sequence)? Are there more modifiers? I'll document it in a FAQ

👍 1 🎉 1

kauffj commented

2017-10-12 15:40:12 +02:00

(Migrated from github.com)

I have mixed feelings about the behavior of enter. We are trying to teach people about the concept of addresses, and that the bar is both an address bar and a search bar.

wilsonk commented

2017-10-12 23:14:43 +02:00

(Migrated from github.com)

From a new user point of view it is really odd to not just be able to type in "flame"->hit enter and get back some results of videos that have "flame" in their title or description or the publishers name.

I understand that we may want to teach people about addresses, but it will be very hard for really new (or overall novice internet) users to grasp this without getting frustrated.

I think requiring '@' or 'lbry://' or '...#...' or '... : ...' to do an address lookup is the way to go. Any other search terms followed by the enter key will just to a simple search. Do a regex on the incoming string and it should be good to go.

This is in line with a web browser where you can type in the exact address of 'http://myfakesite.com' or just a couple words and hit enter to get a search to run.

Just my two cents.

Thanks
Kelly

From a new user point of view it is really odd to not just be able to type in "flame"->hit enter and get back some results of videos that have "flame" in their title or description or the publishers name. I understand that we may want to teach people about addresses, but it will be very hard for really new (or overall novice internet) users to grasp this without getting frustrated. I think requiring '@' or 'lbry://' or '...#...' or '... : ...' to do an address lookup is the way to go. Any other search terms followed by the enter key will just to a simple search. Do a regex on the incoming string and it should be good to go. This is in line with a web browser where you can type in the exact address of 'http://myfakesite.com' or just a couple words and hit enter to get a search to run. Just my two cents. Thanks Kelly

👍 3

kauffj commented

2017-10-12 23:55:32 +02:00

(Migrated from github.com)

To be clear, I don't disagree at all that this is confusing and I think a change is warranted.

I just don't know precisely what it is, because I also think it's important that people have an easy and intuitive way to get directly to a URL, and having to type lbry:// before everything is not that.

In a more standard browser omnibar, we can tell the difference between a search and a URL by whether or not a TLD is included. In the case of LBRY URLs, there's no equivalent.

To be clear, I don't disagree at all that this is confusing and I think a change is warranted. I just don't know precisely what it is, because I also think it's important that people have an easy and intuitive way to get directly to a URL, and having to type `lbry://` before everything is not that. In a more standard browser omnibar, we can tell the difference between a search and a URL by whether or not a TLD is included. In the case of LBRY URLs, there's no equivalent.

WaveringAna commented

2017-10-13 01:25:07 +02:00

(Migrated from github.com)

add a big search bar, then a tiny go bar, like the old safari browser but the inverse

WaveringAna commented

2017-10-13 01:25:32 +02:00

(Migrated from github.com)

http://blogote.com/wp-content/uploads/2011/09/safari_mac_browser.jpg

hackrush01 commented

2017-10-23 03:00:17 +02:00

(Migrated from github.com)

Instead we could have a key combo(e.g. CTRL + Enter) to go directly to the
claim, and hitting only Enter would initiate a search. And we could make a
tooltip pop-up whenever the user clicks on the wunderbar too, as a
reminder, as this is not particularly intuitive.

-Regards
-Amit Tulshyan

On Oct 13, 2017 4:55 AM, "Procrastinator" notifications@github.com wrote:

http://blogote.com/wp-content/uploads/2011/09/safari_mac_browser.jpg

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/671#issuecomment-336308326,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQxPZlDR4OCn8ZyKWQFOeA1gEgAOcroKks5srp_tgaJpZM4P2J7F
.

Instead we could have a key combo(e.g. CTRL + Enter) to go directly to the claim, and hitting only Enter would initiate a search. And we could make a tooltip pop-up whenever the user clicks on the wunderbar too, as a reminder, as this is not particularly intuitive. -Regards -Amit Tulshyan On Oct 13, 2017 4:55 AM, "Procrastinator" <notifications@github.com> wrote: > http://blogote.com/wp-content/uploads/2011/09/safari_mac_browser.jpg > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/lbry-app/issues/671#issuecomment-336308326>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AQxPZlDR4OCn8ZyKWQFOeA1gEgAOcroKks5srp_tgaJpZM4P2J7F> > . >

kauffj commented

2017-10-23 22:05:04 +02:00

(Migrated from github.com)

CTRL + enter is too obscure. Keep throwing ideas out though, we'll get there.

Maybe we need to focus on what aspect of the UI/UX is causing people to think they need to hit enter in the first place?

If you were showed search results immediately after typing, maybe no one would hit enter?

CTRL + enter is too obscure. Keep throwing ideas out though, we'll get there. Maybe we need to focus on what aspect of the UI/UX is causing people to think they need to hit enter in the first place? If you were showed search results immediately after typing, maybe no one would hit enter?

WaveringAna commented

2017-10-23 22:07:54 +02:00

(Migrated from github.com)

They hit enter because thats what google trained them yo do. If people want
to directly go to a link, they can prepend lbry:// that way we can keep
enter for search.

On Oct 23, 2017 4:05 PM, "Jeremy Kauffman" notifications@github.com wrote:

CTRL + enter is too obscure. Keep throwing ideas out though, we'll get
there.

Maybe we need to focus on what aspect of the UI/UX is causing people to
think they need to hit enter in the first place?

If you were showed search results immediately after typing, maybe no one
would hit enter?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/671#issuecomment-338780093,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJmmkeIM8nq2_2xuhsjlIVBlHyBXWy-gks5svPFygaJpZM4P2J7F
.

They hit enter because thats what google trained them yo do. If people want to directly go to a link, they can prepend lbry:// that way we can keep enter for search. On Oct 23, 2017 4:05 PM, "Jeremy Kauffman" <notifications@github.com> wrote: > CTRL + enter is too obscure. Keep throwing ideas out though, we'll get > there. > > Maybe we need to focus on what aspect of the UI/UX is causing people to > think they need to hit enter in the first place? > > If you were showed search results immediately after typing, maybe no one > would hit enter? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/lbry-app/issues/671#issuecomment-338780093>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJmmkeIM8nq2_2xuhsjlIVBlHyBXWy-gks5svPFygaJpZM4P2J7F> > . >

kauffj commented

2017-10-23 22:27:52 +02:00

(Migrated from github.com)

@aayanl Google has trained them that if they hit enter they magically get what they want, whether that was a domain or a search.

Also, when typing in Chrome, I never see results until I hit enter. In our app, you will see results just from typing, so it's possibly that if they came even faster, people would stop hitting enter.

@aayanl Google has trained them that if they hit enter they magically get what they want, whether that was a domain or a search. Also, when typing in Chrome, I never see results until I hit enter. In our app, you will see results just from typing, so it's possibly that if they came even faster, people would stop hitting enter.

nikooo777 commented

2017-10-25 00:54:42 +02:00

(Migrated from github.com)

i think the best approach is to follow what most of the browsers do.

That is:

If an address is typed (and this is easy to detect here since we have the prefix lbry://) then once enter is pressed it should bring up the claim right away.
if anything else is typed and enter is pressed, then a search should be performed

in addition, having a live-search as you type is good (that's similar to instant search on google.com), however I wouldn't go as far as thinking we can train people in doing something they have never done when we have giants such as google/mozilla/apple that push for other standards.

my 2 cents

i think the best approach is to follow what most of the browsers do. That is: - If an address is typed (and this is easy to detect here since we have the prefix `lbry://`) then once enter is pressed it should bring up the claim right away. - if anything else is typed and enter is pressed, then a search should be performed in addition, having a live-search as you type is good (that's similar to instant search on google.com), however I wouldn't go as far as thinking we can train people in doing something they have never done when we have giants such as google/mozilla/apple that push for other standards. my 2 cents

👍 2

kauffj commented

2017-12-11 22:46:37 +01:00

(Migrated from github.com)

@seanyesmunt I believe our search service now has an autocomplete endpoint, which you can use to help improve the searching user experience.

https://lbryio.github.io/lighthouse/

(this may need to be merged first https://github.com/lbryio/lighthouse/pull/42)

@seanyesmunt I believe our search service now has an autocomplete endpoint, which you can use to help improve the searching user experience. https://lbryio.github.io/lighthouse/ (this may need to be merged first https://github.com/lbryio/lighthouse/pull/42)

lyoshenka commented

2017-12-11 22:47:37 +01:00

(Migrated from github.com)

its merged. example: https://lighthouse.lbry.io/autocomplete?s=lbry

neb-b commented

2017-12-11 23:08:19 +01:00

(Migrated from github.com)

Nice

On Dec 11, 2017 4:47 PM, "Alex Grin" notifications@github.com wrote:

its merged. example: https://lighthouse.lbry.io/autocomplete?s=lbry

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/671#issuecomment-350869083,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQGcjt8o0QbhqrQLNDaPzi9LUBVj1C-Rks5s_aL7gaJpZM4P2J7F
.

Nice On Dec 11, 2017 4:47 PM, "Alex Grin" <notifications@github.com> wrote: > its merged. example: https://lighthouse.lbry.io/autocomplete?s=lbry > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/lbryio/lbry-app/issues/671#issuecomment-350869083>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AQGcjt8o0QbhqrQLNDaPzi9LUBVj1C-Rks5s_aL7gaJpZM4P2J7F> > . >

neb-b commented

2018-01-09 02:46:45 +01:00

(Migrated from github.com)

This will continued to be improved, but the basic implementation is in the redesign branch

Search address bar function is confusing to new users #671

The Issue