Tag Info

New answers tagged

0

Show the scrollbar Usability must come first, and the scrollbar is necessary to show users how to use the legend. Once you establish the UX priority, you can then work to calm the layout. Your legend has different colors, fonts sizes, font weights, shades, and difficult non-grid alignment. All of these create UX clutter, which is why you feel like the ...


0

Putting buttons at the bottom and top of the widget is a bad idea. In my opinion that would signal to the user that scrolling is not an option, and reduce the discoverability of the scrolling feature. You have advanced users, and a complicated interface, so I'm guessing that learnability is not as important as efficiency. Personally, I think your design is ...


0

Use AutoCompleteTextView entries only If you have too much entries for a spinner, this is the best known way currently. An implementation solution is on stackexchange


0

your problem could be solved using the Breadcrumb method. combined with dropdown list and auto complete input box if you have a long list. here you are what I mean. and the result will be shown as the following the second pulldown list will filtered from the first list and third one is filtered from the second one. I mean nothing will show in the ...


1

Yes there are alternatives Since you only have two views, a common approach that is also applicable to Material Design is to provide a toggle icon or word (map or list) in the topbar. This avoids the need to take up valuable real estate with a tab control, and may help you avoid the awkward scrolling design by enabling a fixed topbar. This approach is ...


1

I have to agree with Micky Duncan : I think searching/grouping/filtering are not at all suited for this task. You don't want to search and select a few items from a big list. You want to select about half of all items on the list. If the user has to select half of the items, the user will want to make sure he has selected all candidates and not missed ...


1

Never ever update when user is deciding. It is just to frustrate your user while using your app There is no status when the alarms are generated, how do the user know what alarm was generated at what time Don't steal control of the selection from user Here is my visual solution


0

You can try dividing the screen into two scrollable sections. something similar to a date picker ?


2

The problem with drag-and-drop is that you can't be sure about the user recognizing this a functionality. If you provide some kind of "first time tutorial", and the lists tend to fit in the screen, it's the best option. Comparing d&d with the arrows, the latter are more intuitive but also more tedious because of the number of taps that might be ...


0

Don't implement your own double click logic. How do you find this approach? Select one item by single click on the checkbox - you're now in a selection mode Select further items by single click on the whole item area Cancel selection mode by cancel button Directly play an item by click when not in select mode Demo: ...


1

Long click and drag seems to be the best solution. One or two below: If you have a long list - long click and scrolling list as a background with clicked element above. For short list - long click and drag. Also consider clicking - icon on the right side indicating, that you can change order. After click moving up / down is activted. I'd consider some ...


10

I would try something like GMail tags. You have a filter and the list of checkboxes inside a scroll area Other good option is something like Pocket Chrome plugin You have a filter and the selected items become a tag


3

I had to face same problem a few days ago, and came with this solution ! In my cases list weren't that long so I used a tag system so user can have a list of the items that he/she selected.


0

I think a side-by-side list widget would be appropriate for this situation. It goes by many names. See: Name for widget with side-by-side available/selected listboxes? Also, you should provide a search box to dynamically filter the list of available items as the user types.


17

This is where UX is being tasked to fix something that isn't fixable at the UX level. I'd go as far to say this is where a back end system is unfairly asking a user to make decisions that they shouldn't have to. If the issue is that people enter items they sell under a different name than what's already in the system, then the proper solution would be a ...


0

Consider the content to be displayed in the app; you're displaying lists. This means that when thinking about navigation, the most natural way to start is by 'listing' your list choices. Your heirarchy is fine, and the tabs are a good starting point in this case. A good convention when designing for tablets is a vertical bar design, like google uses for ...


0

Your two suggested solutions represent two very different types of interfaces. The list approach uses a "conversation" metaphor, where the user indirectly "talks" to the application, while the second approach uses a "model-world" metaphor, where the user can directly interact with domain objects (in your case "cards" and "decks"). Using a model-world ...


0

I'd recommend to go with boxes first, probably your amount of "decks" will increase with time, so you could actually add the feature to select both views in a future upgrade. Boxes fits perfect for little amounts of items, but eventually a user will find more useful to select from a list. I also noticed the boxes have a star, is that a "favorite star" to ...


0

I'll totally agree with your co-worker and here I'll explain you why: Inside your Downloads tab you should have just downloaded music. If you want to add also music that has been introduced in the device by other means (usb, sd carc,etc), the "Downloads" tab is not an appropiate title, it's inconsistent. Expandable lists are very close to each other, so ...


1

Would this work for you? Merging the two lines into one, but not sacrificing too much space?


0

It seems like you have a lot going on here. One way to slim down the cognitive overload is to ditch the modal path. If alarms are an important part of the interface, make them persistent. An option to collapse this persistent view is better than forcing everyone to click the button. With a persistent view, the nature of the dynamic loading (whether top or ...



Top 50 recent answers are included