New answers tagged

0

Well it depends on the number of elements that are being cycled and the purpose of the cycle. In most cases with not a huge number of elements going seamless to the beginning is a life saver. For example the ⌘ Tab I am not even aware of the order of the apps until I have already started cycling so it is easy to go past the app that I was interested in so I ...


0

Another approach which you can take is your each item is section, layout in horizontal manner. On selecting each section you can layout your list below it in vertical list.


0

The question is framing the situation well, and I can come up with two different possible solutions. One of them is shown below as I'll explain and the other one is a bit different version of the same solution, so that you may alternatively develop a version of the solution provided here. Basically, you should indent subItems in contrast to Items and it ...


0

I think the chevrons make it quite clear that each item is expandable and they do so without making the screen look too crowded, in my opinion. However, I do think that you should ditch the chevrons next to the items in the expanded menu, in favor of some smaller arrows or filled in triangles pointing to the right or something. Having very similar icons for ...


0

OPINION: If grouping elements is a common action for your user I do not see a problem with your implementation in the demo. Would the people using this app be considered "power users" would they already be familiar with these actions required? A helpful question to ask yourself is; Would the user require training to know how to complete this grouping task? ...


1

I think the problem comes because you're mixing READING and EDITING screens. If you're editing, you need to make it very clear. Your action buttons (please do not confuse with CTA) make sense on an edition page, but of course, they're not needed if the user is viewing data. This is why you're facing this problem: in one screen you have nothing to save, ...


1

It would help to see a bit more context about how this list is to be used in your UI, but I would consider the following: A long list almost certainly shouldn't be displayed in one go, such as in a dropdown - https://lawsofux.com/millers-law.html If the list is to be used in the same way as something like gmail addresses (small area of screen real estate), ...


1

Having it in a list view just as you have it is intuitive. However, I would suggest that you add a border around the 'protocol' just like you have it on the 'remove' button. The remove button can now be replaced with an icon just beside the protocols. That way, you can save more space for longer protocol titles and have the protocols easily identifiable.


Top 50 recent answers are included