New answers tagged input
0
There's no particular name for it. Inputs in HTML5 can have a value of multiple email addresses separated by a comma:
<input type="email" value="foo@example.com, bar@example.com">
For what it's worth, the newer gmail compose UI uses a 1 row textarea inside a table instead of an actual "input"
0
I really like the solution of Microsoft Outlook:
They have a combo-box, where frequent time-values can be easily picked:
If you want something more accurate, you can edit the textbox directly, where the units needs to be specified. It auto-completes with the most probable unit:
It looks like it's able to support most cases; you can quickly set from ...
1
The problem with having such locale-dependent and non-constant things as months and years is their inherent ambiguity. "Does a month equal 28, 29, 30 or 31 days?" "Are we talking about the bankers' year of 360 days, or 365, or 365 1/4 or 366 days? (putting aside more weird numbers)" With this in mind, a combination of numerical controls seems to fit the ...
0
As is the case with may UX issues, the "best" solution depends on what you expect will be in your users' minds as they use your UI.
Going along with your three cases:
Pre-determined ranges - These might be great in your case, since it sounds like you're dealing with the "period" of a repeating operation. However, it would be terrible if you were ...
0
So the real question is how great a need do your users' have for custom intervals? Do your users NEED to be able to input one month and 2 days? Probably not all that likely and you don't really want to design for exceptions.
Sliders are fun but can be a time consuming to QA and of course have accessibility issues to overcome.
In the case of one month and ...
0
In my experience, when I still have no clue on how tech-savvy will these users be, a balance between the two is best.
However, I must admit I tend to use placeholders. Also, whenever I can (when there is only one or very few input fields), I choose a suggestive design and then limit user input.
I try using placeholders as a way to show what is valid and ...
0
If an input field has limited length or limited allowed characters, I would have some kind of client side validation for it, that would show immediately if the input doesn't match the format or exceeds the max length.
I've had to tackle/see others tackle so many typos/incorrectly formatted data from database rows, because there's been input fields without ...
2
I prefer to let the user type and somehow indicate the error with a formatting or length indicator. Twitter is a good example.
The benefit of this approach is particularly apparent in message entry fields where the user might just need to get their thoughts down then edit for length. In the case of data-centric fields (like phone numbers) it simply avoids ...
0
Do you like [product name]? is too vague, example:
Did you like this restaurant ?
- Yes (but the waiter was the worst)
- No (the waiter was the worst, the rest was good though)
Yes and No are not useful, therefore comments are sufficient.
Yes/No are useful if you ask about the value of your product/service.
What is interesting for you is asking for ...
0
Keep it simple. A simple text based entry would give the user the idea that he has freedom to enter what ever he wants. I do understand this might make data analysis much more difficult since you have to read to see what he has written but its a single field to answer and to force him to conform to a definitive yes or no answer or even a maybe answer would ...
0
The yes/no question is leading (of sort). You are directly asking for the user if he liked your product or not. If you want honest feedback, I would avoid such questions since experiments have proven that people tend to be polite when reviewing/giving feedback, especially if they are doing so in person.
If you want good feedback, keep the questions ...
2
As you mentioned, the user cannot select both SD and HD formats. Why not roll up into a single group annotated as "Format Type". All options can then be listed within the group as radio buttons. This may work better but takes up slightly more space.
download bmml source – Wireframes created with Balsamiq Mockups
0
I just came across the same problem while designing a sign up page.
I agree the answers above. I am also surprised the see few new websites like newmyspace.com using the same.
Probably we should be able to find skin to input that give visual cue to users while have only border in the bottom but has some depth(inner shadow or something) inside the input ...
4
Two things are possible:
Do not force the application to gain focus. Show the message and keep waiting till user switches to the application.
Implement blinking notifications. This is OS dependent. May or may not be feasible in other OS but in Windows operating system, there is system tray (systray in short). Application can be coded in such a way that if ...
3
My view is prevent applications being 'arrogant' and demanding immediate attention. A well mannered application will wait it's time whilst somehow making you aware it's there. On macs this is done by bouncing the application icon. Too many applications assume they have your full and undivided attention when, increasingly, we're bouncing beween multiple ...
0
Use a linear gradient to represent whatever colors you want and the use markers to represent points.
Something like this with markings for different points rather than entire boxes for individual points.
When you use box, you are essentially creating a discrete value rather than a continuous scale.
3
Some ideas:
Join the buttons with some sort of bar.
Crank down the color. It's hard to spot what's selected
I think the transition from saturation = click me to saturation = currently selected option is confusing. I'd represent the transition with two different metaphors.
Here's a quick idea:
3
Since there are different type of roles it is probably a good idea to separate their management.
You could use something like that for roles that are unique :
I'm of the assumption that the administrator knows the users she want to be Finance and Legal.
download bmml source – Wireframes created with Balsamiq Mockups
If it is relevant you can ...
3
A radio button would be ideal, but you do not want to confuse the user by using check box and radio button in the same row.
You can de-highlight the options when any user is selected. Grey out the remaining options when any user is selected. (There is some confusion with this approach, since it might lead to the user thinking that his option is locked and ...
2
The first interaction pattern that you show is very close to the way that apple handle it in their built-in apps. The difference being that they don't have an "add new row" item. They use a clear + button in the navbar to achieve that - which is the right way to go.
If you use an item at the end of the list to add new items, you are not only breaking user ...
6
How about this layout?
download bmml source – Wireframes created with Balsamiq Mockups
I guess the users need to decide if they want either SD or HD so this should be the main option. Then, secondary, they can select whatever other option you offer.
This solution also enables you to set a default for users. You could work with radio buttons ...
10
Unless you can proceed without selecting (leave the field blank) one SD options, I would suggest you go with a radio button.
You layout remains consistent if you are using the same input mechanism for similar tasks. Making it easy for the user to proceed quickly.
Radio buttons are faster (easier also in many cases) than using a drop down menu. The ...
0
Rather than group by question, you should try grouping by course.
Since, in the current view, the flow is like:
Question 1 -> think about course 1 in context of question -> think about course 2 in context of question -> think about course 3 in context of question -> think about course 4 in context of question.
Question 2 -> think about course 1 in ...
3
To confirm sensible results, I have taken surveys that use anti-questions:
download bmml source – Wireframes created with Balsamiq Mockups
Number 1 and 4 are "anti-questions". If a survey taker answers in a corresponding way (more or less the same meaning) on those two questions, it is more likely that he or she has read the questions carefully ...
6
You could indicate under the selected response the actual value - as in the image below, so that users get immediate (but non blocking) feedback in-place for the response they just selected.
If users meant to be very Satisfied they will likely spot the mistake and correct it
Also you might try not putting the header in inverse colours as that slightly ...
2
Maybe the design is not explicit enough before the question is answered and that is why people are confused.
There is enough questions in this form, since we all know answering those surveys are a pain, you do not want to had others by asking for confirmation.
Maybe something like that would help :
download bmml source – Wireframes created ...
2
Here is a quick mockup I did thinking bout your problem:
Introduce a list of addresses which will contain a predefined list of addresses you need to collect. If address is incorrect or incomplete - highlight it's alias in address list with one color (red for example) and a icon, if it is correct/completed - highlight it with other color (green for ...
0
You probably can gain some space since there are too many fields in this form.
You probably do not need a title, Name and Surname are enough.
How relevant is the date of birth in this address form? (I mean the first one, because the other two on the foot are probably a mistake)
The 5 first fields of the address can be condensed in two : address 1 et adress ...
1
You can disable one of the combo-box until a selection is made and you can populate the second combo-box.
download bmml source – Wireframes created with Balsamiq Mockups
2
There is no such thing as "one solution to fit em all" for this case (as probably there is no such thing as universal solution for many other problems in UX design). My advice is never to combine comboboxes though - it is messy and misleading.
You need to think about what do you want your user to achieve. Next try think about what you try to achieve.
Lets ...
4
Long lists or where unavailable options don't matter
When you have long lists, or where unavailable options don't matter, you can simply leave them out.
Airline flight booking is an example of this. If I chose a starting point, I only care what my possible destinations are, and so this is far better than a list of all possible destinations with everything ...
1
Combining comboboxes is only a good solution if there is a very limited, static set of items. Say you had three options: Print -> To File, Print -> To Printer, Don't Print. Two comboboxes (print/no, file/printer) is a bit of a waste there. But if there is a large number of possible options a single combobox largely becomes unweildy as you have to list all ...
0
if its a form, my opinion would be to show compatible values in the 2nd/output drop down..
just imagine if there are 20-25 values in the 1st dropdown and 40-45 values in the 2nd/output dropdown..
you can see one good example here: http://www.acer.co.in/ac/en/IN/content/drivers
, you can consider this option too.
3
Grey out the invalid/not-available options in the output field.
It is similar to the contextual menus we are so used to. Just make sure the user is aware of the relation between the two combo-boxes.
Inthe mockup, C is selected for input and correspondingly, 1 and 4 are disabled in output.
When you grey out the options, they are still visible, but, ...
1
I see a larger UX question here - why ask your users to do data entry?
You don't want to do that product data entry manually. It'd be terribly boring.
However, neither do your users.
The companies who manufacture these products surely have spreadsheets or databases where they've already captured all the information you need. There must be some source ...
0
I had a similar issue, albeit the project wasn't finished by me.
Question in your case is, wether measurement always stay the same per resource - eg: is the measurement always gallon for Fertilizer X, or shall the same resource be measured sometimes in weight, sometimes in volume?
In our case, it was a small one-man shop of home made cosmetics. Think of ...
1
First of all, I would say that it is not helping anyone to propose different types of measurement. Conversion from kilos to pounds is useful because there is a cultural difference. But weight and volume ?
It is commonly accepted that liquids are in volumes and solids in weights. But lets imagine that one measurement is for use and the other for ...
0
Once you have the conversion ratio, can you not freely convert between weight and volume?
When adding a resource, require users to specify a permanent volume-to-weight conversion rate. Again, this would be permanent, as changing the method would prevent us from calculating inventory amounts.
This seems to be your best option. Each resource type has ...
1
I'd have to imagine there would be some text somewhere around this field that would explain a little about your mailing list (e.g. how often to expect emails, what kind of content to expect, etc.). If not, you should really consider adding this. I struggle to imagine many visitors clamoring to enter something into a random field with very little context.
...
3
Replace the button text
Go
with
Join or Join our mailing list.
Because that is what the button is doing.
Put an example email like your@email.com on the textbox (or input), if thats a webapp you can safely use the placeholder element.
Replace
Don't worry, !! we respect your privacy we never spam.
To
We never spam.
Remember that ...
3
I would say give it a label.
Also, as a side note, "go" doesn't seem like the right CTA on the button. "Submit", "enroll" or "sign-up" would all be better options. "Go" implies you'll be moving the user to another page for next steps, while language that indicates this is a submission field would make more sense. If you actually are taking them to a page ...
12
It does need a label, not just visually for people viewing the site but for people using assistive technologies (screenreaders etc). If there is no label then people visiting do not know what the field is for, or what goes it it.
From W3C Guideline 3.3 Input Assistance: Help users avoid and correct mistakes.
3.3.2 Labels or Instructions: Labels or ...
0
How about this ?
The water mark can still be shortened without losing the meaning
Top 50 recent answers are included
