Tag Info

New answers tagged

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


1

For new OS this is a way how dropdowns are displayed (it is probably also a concern for Apple designers - I do not know why it was changed). For you - it is best to use design it as close to native as possible. For Mac - use up/down icon, for Windows - triangle-down icon. All because useres got used to it on their devices. For Windows users it will be ...


1

For very long lists, it's better to use a different UX for mobile Multi-select is a complex operation, so it's difficult to use the same interface for both web and mobile. You already recognize this because you've outlined two different layouts. Your mobile design is problematic because: It requires users to tap once to add an item, and then select ...


0

I'd suggest using something similar to the iOS "Select" functionality in Camera Roll. User taps a button to activate a "selection" state. User selects all the items List A items they want to move to List B. User taps a button to move items to List B. I'd also pair this with a search box that allows the user to easily filter out the names they want. That ...


3

First of all - not ABCD... but autocomplete in search (consider Cyrillic, Greek or other alphabets). Drag-n-drop is a beautiful feauter, but consider dragging aprox. 50 elements. I will be extremely time consuming. Clicking on item on the left to assign it to group will be much easier. For mobile my proposition is to switch view between Available <-> ...


1

If we're talking about mobile, maybe override the default web scroll element and implement a scroll with a native-like behaviour and then show a tag list above it. To add something to list B from list A, click on a row in list A. To remove from list B, click on the tag on list B or click again on the row in list A. download bmml source – ...


0

The UX answer for this would be that a user action should be mapped to only one function; otherwise things can get confusing, the function can be ambiguous, and the result of the action can be unpredictable. If I take your proposal, how would you explain such behaviour in a manual? You'll have ifs and thens and you introduce logical complexity. ...



Top 50 recent answers are included