> it was obviously not written by someone who has spent a long time in a support I have been in call centres and watched users many times. > The way that I would word it and would mentor people to say is "go to 'my…
Yep, once you go down the path of in context filters, there are a whole bunch of challenges. I need to do another post on that :D
Yeah I can see your view on this. It’s the trouble with naming things.
I wondered this too.
The only downsides to in context filters (is taking up space next to the results). But I think that is the right trade off to make for sure. Certainly my user research/usability testing has shown that to be true.
Thanks for sharing, the problem with this is that it pushes the results down. That’s a real downside.
Yep, totally, if you have 100 facets (filter categories) then you’d want to curate them and progressively reveal more as they become relevant. Tricky, but that is definitely one of the trade offs. Luckily for me, the…
Exactly, that was my intention with the article.
I have a whole chapter on this in my book. You’re that it’s tricky but luckily it’s doable. In short, you partially overlay the current list/results with the filters. Way quicker than going to a separate page (and all…
You have explained it exactly right ha. Thank you. I also agree that my article is way too late and I did actually want to write about it 5 years ago. I’m a little slow :D In terms of Google, they still have a separate…
Yeah, the difference is the user has to understand "advanced search" and go to a separate out of context page to use the filters. Some people think of advanced search as what they type into a box. Fair enough, naming…
I found it interesting and I’m glad the article was useful for you.
What do you suggest instead?
I’m sure like you say there can be times for the other. For example, if users are used to going to a separate advanced search. But in context filters basically is advanced search without the pitfalls of advanced search.
Yeah, I mean ideally you’re nav is so simple that you don’t need search beyond Google. But it’s not always possible. Take an ecommerce store where the user wants to drill down on particular facets. That needs search…
I wouldn’t no. I’d look to sort out the root cause (slow server perf) in this particular case. But obviously we’re talking in the abstract. Advanced search is bascially the same as in context filters without the…
Yep, I have a whole thing on how to design filters for small screens. But in short, partially overlay the screen. There’s nothing else you can really do without having downsides. But like you say discoverability goes…
Thanks for sharing those resources. Will have a read.
Glad you shared this experience with us. I agree with the approach :)
Yep :)
Unfortunately, lots of site break the back button making this a problem. First make sure the back button works correctly and offer a link to go back. People should trust those more than hitting the browser's back.
Yes it was based on a percentage increase to conversion with the new checkout flow.
A summary panel is useful here (on each page). We did this for Kidly (one of the examples in that post).
It's not just using the scrollbar to scroll. The size of the scroll bar indicates the length of the page, something which helps the user.
> it was obviously not written by someone who has spent a long time in a support I have been in call centres and watched users many times. > The way that I would word it and would mentor people to say is "go to 'my…
Yep, once you go down the path of in context filters, there are a whole bunch of challenges. I need to do another post on that :D
Yeah I can see your view on this. It’s the trouble with naming things.
I wondered this too.
The only downsides to in context filters (is taking up space next to the results). But I think that is the right trade off to make for sure. Certainly my user research/usability testing has shown that to be true.
Thanks for sharing, the problem with this is that it pushes the results down. That’s a real downside.
Yep, totally, if you have 100 facets (filter categories) then you’d want to curate them and progressively reveal more as they become relevant. Tricky, but that is definitely one of the trade offs. Luckily for me, the…
Exactly, that was my intention with the article.
I have a whole chapter on this in my book. You’re that it’s tricky but luckily it’s doable. In short, you partially overlay the current list/results with the filters. Way quicker than going to a separate page (and all…
You have explained it exactly right ha. Thank you. I also agree that my article is way too late and I did actually want to write about it 5 years ago. I’m a little slow :D In terms of Google, they still have a separate…
Yeah, the difference is the user has to understand "advanced search" and go to a separate out of context page to use the filters. Some people think of advanced search as what they type into a box. Fair enough, naming…
I found it interesting and I’m glad the article was useful for you.
What do you suggest instead?
I’m sure like you say there can be times for the other. For example, if users are used to going to a separate advanced search. But in context filters basically is advanced search without the pitfalls of advanced search.
Yeah, I mean ideally you’re nav is so simple that you don’t need search beyond Google. But it’s not always possible. Take an ecommerce store where the user wants to drill down on particular facets. That needs search…
I wouldn’t no. I’d look to sort out the root cause (slow server perf) in this particular case. But obviously we’re talking in the abstract. Advanced search is bascially the same as in context filters without the…
Yep, I have a whole thing on how to design filters for small screens. But in short, partially overlay the screen. There’s nothing else you can really do without having downsides. But like you say discoverability goes…
Thanks for sharing those resources. Will have a read.
Glad you shared this experience with us. I agree with the approach :)
Yep :)
Unfortunately, lots of site break the back button making this a problem. First make sure the back button works correctly and offer a link to go back. People should trust those more than hitting the browser's back.
Yes it was based on a percentage increase to conversion with the new checkout flow.
A summary panel is useful here (on each page). We did this for Kidly (one of the examples in that post).
It's not just using the scrollbar to scroll. The size of the scroll bar indicates the length of the page, something which helps the user.