Tag Info

Hot answers tagged

6

Neither seem consistent The first big difference I see appears when the user have a list of maybe 15 items and they enter the page to add another one, I don't think it's a good idea to make them scroll to reach the New Item button. In the other hand placing the New Item button in the top isn't very familiar, plus the input point would descend 1 place to ...


6

I don't think you'll find something about this because the premise seems to be incorrect, since sorting is a way of filtering, thus the answer is already included in the question. However, if you consider filtering as an action with sorting and filtering(n) as sub-actions then you could recognize some patterns, which will vary with amount of data, ...


5

Personally, I think you should leave it up to what users are most used to which is the 'sort bar' you have in your second picture. Alternatively, you can do what sites like Amazon do and just provide the sorting options in a dropdown menu like so: These two methods are the most common and users are likely to be used to them. Deviating too much from them ...


3

Instead of displaying a "load more" button, you can easily just put a phrase that says something like "end" such as: download bmml source – Wireframes created with Balsamiq Mockups Obviously, wording can change, but as long as they know that there is nothing more to show. Heck, even not displaying a button anymore can be sufficient enough.


2

For me the only reason to avoid the single search (2nd option) would be to have several columns with similar content, thus leading to an inefficient search. If that's not the case I would totally go with the single search: There's only 1 entry point for search, thus less cognitive load. The users only have to think what to search, not where to search ...


2

I completely agree with the reasoning in Oztaco's answer about expected behaviour, and will add an alternative solution: You mentioned you want to avoid clutter - you could add a 'sorting' icon such as the one below, which could open a dropdown or expand to show sorting options.


1

Some good ideas here already, but in case you decide to go with the single list, you could add a filter button at the top (could also be a checkbox):


1

I think there is a great reason to use the single list with two sections. The user doesn't have to switch screens to view the alternative blutooth devices, and are more likely to want to use the ones that are on in the first place. Even with the scrolling, it seems less complicated. People seem like they would be less likely to try to access something that's ...


1

since you tagged your own question with the Material Design tag, I'd suggest using actions that fires bottom sheets for each of your alternatives. This way, you could clearly display both options on same page, providing the user with simple and direct access and displaying the alternative paths an user can follow on a single screen. This being said, tabs ...


1

I would have your design follow the path/user story you describe- you said users want to see devices in range, or they want to request permission to connect to a new device. I would have a single screen/tab- the left screen is visible at first, but a button or clickable hyperlink at the bottom that says "Or request access to new device". That would open the ...


1

There's a very good article on UXMatters about filtering information in tables. Although old, it still makes a lot of sense. A few options have been considered, like data filters above a table: filters to the left of the data or tabular format in case the number of filters is low There's also a good discussion about consistent availability and ...


1

I find the search box more intuitive for search. However, the text boxes provide a way of advanced filtering. So, the question is - do you want your users to search or filter? If you want both, you may consider the following intermediate solution, Amazon is using the same. Your search box searching all columns by default but the user has the option to ...


1

And why not have the possibility to insert a line at any place the user wants ?. If the end of the list is really bad place with bad ux for the user when he has got a huge list if you fix the field add on the top of the table while the user scroll he can reads his table and scroll in to check an existing value for example. And when he doesn't see the value ...


1

The answer to the question is based on the fact that whats more important to your users, for them their old items in the wishlist might mean more to them and they would want them at the top (and add the new ones to the end of the list). The another approach, which I can say is more preferable in case of wishlist is, the newer the entry the more it is ...



Only top voted, non community-wiki answers of a minimum length are eligible