New answers tagged

0

All of you are ovelwelming about this. Is simply. Apple Picker View, Android Dropdown. Is hard to stend ?


0

On first wrong input give a error message and ask user to use the tooltip. Which shows valid and invalid numbers (invalid greyed out)


0

Possible options: Tapping/clicking anywhere on the image to enlarge and have smaller navigation buttons that allow users to navigate left or right Tapping/clicking anywhere on the image to navigate left or right and have a smaller enlarge button somewhere on the image that allows users to enlarge the image On mobile, consider having a one time only hint ...


1

The user should not be bothered with your historical reasons for limitations. Prepare a mapping between valid values and consecutive numbers, e.g.: Id: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 Valid value: 1, 2, 3, 4, *, 6, *, 8, *, 12, *, 16, 17, 18 and present the Id's to the user only ("pick a number between 1 and 50"). Behind the screens ...


1

Allow only 1 to be locked at a time Essentially make them radio buttons. It looks like the three variables (rise, run, grade/angle) are one of three things to the user: I know this value I'm trying to find out this value I'm experimenting with this value If any two of them are the first, allow the user to put them in directly (just have four number input ...


62

I think a horizontal slider with: Graduations (tick marks) showing the possible values A handle with a triangle end pointing to those tick marks Snapping to the closest possible value when you drop the handle A feedback of the actual value Of course, the ability to manipulate with the keyboard Optionally, the ability to use arrows or +/- to move to the next/...


1

If you can combine a normal number input with a drop down menu that greys out invalid number, and centers on the number entered, with up and down arrows that go to the next valid number, that strikes me as the most intuitive.


74

The user is entering a number. That some values are invalid for technical reasons does not change the nature of the user interaction. I would go with an option that is the most natural to enter a number Perhaps keep a regular number field, but when the user finishes their input, nudge the number to the closest valid option with a minor message to go with it?...


6

Elementary factor seems to be fixing the error. You need some intelligent code that will loop after the collection from * and if it encounters a hole, enter a value less than (index - 1) and greater than (index + 1). Also: Dropdown with 50 options is too mundane(but it's possible to implement search inside) DatePicker - sounds reasonably, 2 interactions ...


0

This is a broad question that covers a number of different aspects, so I won't go into detail here. However, these are some general areas that will hopefully help with initial research and reading for you. In terms of Information Architecture, conveying information to a user efficiently involves the effective use of chunking to group information into ...


0

If you can group your field logically, and distance groups from one another You can place validation / number of digits input in the field so it is auto validated You can signalize length of the number to be typed in, with the size of the field. One with 8 digits should be longest Place fields one below each other. If you can sometimes group them, place ...


0

o-lot]1, I recently designed some forms that share similar layout concerns with this. Here are some visual explorations you might consider: If you really need the form to be shorter, you can sure play around reducing the heights of the input fields or the margins between them. I hope this helps.


1

So, is there any UX reason for doing something like this, or is this just bad design? There is a definite reason for this in my eyes, the learnability of interface and the predictability of the resulting behaviour. If I have a phone / car etc with "chunks" of fuel, I can begin to learn how long a chunk lasts, "I'm on one bar on my phone" that means I have ~...


0

I'm not a fan of using lorem at all (except in apps for designers). Users can be confused and distracted by this dummy text and it might not accurately model the context that the user is making these text adjustments too. It's best to use an actual example, though not necessarily "live" text, so users can get an accurate preview of how their settings would ...


0

If your summary includes a progress bar, it will be easy for the user to visualize where they left and go back to this step quickly. If the progress bar is present in each step, you might not even need the initial wizard.


0

Edit: For example Task A (Importance: 500, Category: II) Task B (Importance: 200, Category I) Users: User A - Attendance: 50, Skill: 14, Categories: I,III, Value: Low User B - Attendance: 250, Skill: 5, Categories: I,III, Value: Medium User C - Attendance: 175, Skill: 14, Categories: II, Value: Medium This system should be build on conditions and ...


1

Look for all the ways your data can be presented and consider facts as : how many users will you poke the most and the least. Can I poke 500 users or 50000 users ? What is important for me to see ? Who I poked or who responded or what the response is ? That will lead you to a more condensed view. Maybe a chart with filters and hover to show info. It ...


1

Vertically below each other in an order that makes sense to your users. The issue with putting fields horizontally next to each other is that they are sometimes missed. Have a search for LukeW, he is a UX researcher at Google and has some amazing content on form best practices.


0

I am a lefty and having the scroll bar on the right drives me crazy. I have to move my mouse positioned on the left side of my desk across the screen to get to my scroll bar. Why not use the scroll wheel on the mouse, you say? Because when touching the left side your screen you will not have any free space for scrolling. Touching usually results in ...


0

Free Users don't need to access Premium Calculators because they cannot access them. You just want them to know they exist (and desire them so they pay). Premium Users probably paid to access the Premium Calculators, so prioritise their availability for Premium Users. That said, a neat solution could be to show the Free Calculators as Tabs until a Free ...


0

"so for that bigger screen size and density, I should be making controls larger right?" NO. It depends. If you are hellbent on achieving the same ratio of whitespace then yes, but that is a stupid endeavor to invest in. Using Density Independent metrics (dp and sp) will help you to achieve the same physical size of widgets, and that is what is most ...


3

This is essentially the same as the answer above by @Mohammed Yaseen Ganai, but I felt that some more explanation was in order to really help you understand the suggestion. The most important thing here is not breaking convention unnecessarily - there already exist UI elements to do exactly what you want to do: Radios and Checkboxes. Radio buttons Radio ...


1

Switches are generally used when there are only one or two options. In this case, there a four options so checkboxes would work better. The options could be made more user-friendly and understandable with the addition of a verb: Allow multiple valid answers [checkbox] Allow multiple attempts [checkbox] Shuffle questions [checkbox] Shuffle answers [...


0

Standard behaviour for a switch is when the action takes effect instantly, a checkbox takes effect after a submit button is pressed. I suggest you change the options you have for multiple attempts etc to checkboxes. Then move down the option for multiple answers to just above where you select the correct answer, here a switch makes sense. Group things that ...


0

It's like yes/no question to answer this without any further explanation but, giving the user ability to make their choice simply whenever it's possible, way more practical instead of making user having an interaction more than once in case of selecting from input dropdown rather than doing it with a single click. As a user I'd prefer the first choice of ...


0

we can display their role somewhere under my profile section with a list of permission available for that role, no need to display in front always. In case the User has multiple roles then it has to login with different credentials or a better way is to create a new role based on a new set of permissions given to the user, so a user can use the single ...


0

I think the word you're looking for is "Tag Cloud". Additionally, the size of the cloud (circles, in your example) usually depends on pre-defined parameters. For example, you can visit Stackexchange's website: https://stackexchange.com/sites and notice that the size of the box depends on the number of people in the community (and other parameters as well, ...


9

Remove the toggle for multiple choice. Keep radio buttons for single answer questions. Keep check boxes for multiple answer questions.


0

This is commonly refferred to as bubble chart. Probably the most common package for charts (for web-design) is chart.js var myBubbleChart = new Chart(ctx, { type: 'bubble', data: data, options: options }); As for floating and bouncing, I doubt that. Then it's no longer a chart. But it shouldn't be too hard, you probably might wanna use canvas ...


1

Maybe you should concretize the option's choice a bit, this will help you not to spread too much in a multitude of variants. I think the beginning you raise in your options is almost infinite: choose a font. There are millions of fonts. Instead I would propose something more generic like choosing a global style so this style can come with some default fonts,...


0

It does serve the purpose of a segmented control, so I guess it must be one. I have not seen any other app using it at the bottom of the screen, especially right above a TabBar which can be a bit confusing. However, it you refer to the Human Interface guidelines for iOS, it is not mentionned anywhere that there is a prefered location for a segmented control.


Top 50 recent answers are included