Tag Info

New answers tagged

1

I see both as possible solutions, though it depends more on your goal. If you're looking to drive better content and currently have people managing all content going in, then you have the opportunity to drive better content. You can do this by offering verification, which is like a status symbol to your users. This helps in three ways: The verified user is ...


1

EDIT: I realized that my answer is much like Stephen Keable's. Don't know how I missed his! Will you only have users from US and UK? I'm from Sweden and my address neither contain a province nor a state. If this is a webform you could do a geo IP detection to detect the country and then use this information to automatically change the form. If for some ...


0

Rather than using the Checkbox to decide, could you perhaps initially show just a country drop down. Which after selecting shows the other fields and appropriate labels for the selected country. Try this fiddle for an example You could even pre select the country option based on IP address (with ability to override). I would also recommend using drop ...


2

If the system can determine if the data is a Identity1 or Identity2, I recommend you to have only one field and only one submit button, and add a label (or placeholder) to explain that you can give a Identity1 or Identity2. For example, assume that Identity1 is a name and Identity2 is an address, you can have : More generally you can have something like ...


3

As I understand, the user knows what he’s searching. So the user has to deside if it’s a task-search or a user-search. If the system is able to decide whether the input is a task-number or a customer-number one field would be better because the user would not be forced to decide. In the case, that there are hits on customers and on tasks you could ask the ...


0

Can you first tell us on what grounds you decided what the future users of the interface with those search boxes will need? As you know, we are here to design for users, but you said that your team is more convinced by one or the other solution. I'm quite sure that you should test it with users of this specific industry. It's not a common scenario and we ...


0

Do both fields behave differently or are the exactly the same but the user will want to put in multiple search items? If the user just wants to add multiple search criteria you could use an input with that accepts multiple inputs like Select 2.


2

From my testing, I have learned that you NEVER, EVER, use a single empty field to represent a phone number (or credit card, or any other multi-part field). I've watched users often make mistakes when typing one long number, then not being able to find the mistake they made. With a multi-part field, they pinpointed the mistake easier ("oh, the first number of ...


2

Since you've specified that you will only be using this form for a US audience, I don't really see a problem with guiding the user towards using a particular format. However, using multiple text fields might not be the best way to go about that. Let's study some existing websites as examples: Papa John's Pizza uses multiple fields for their account ...


3

My guiding principles for this are as follows, vis-à-vis users: Show them what you expect Take whatever they give you Show them what you’re taking The best way to accomplish all three with HTML5 and jQuery is to borrow this plugin. I’ve added type="tel" mainly to give mobile users a keypad instead of a keyboard, and placeholder="(999) 999-9999" as a ...


4

I would suggest you keep one input field, but use a mask for the text: -You can use Placeholder attribute from HTML5 (If you are working in a web App) for showing a example number.


1

Option 1. + input mask An input mask (this type, not a password field) allows the user to type in their number in one go (as if they were dialing for example), yet have the number formatted before it is submitted. This reduces the physical effort (navigating to the next input) and the mental effort (splitting up the number and context switching to the task ...


0

One form field, such as the one presented in option one, is a better experience. You could make the input flexible by allowing the user to enter their phone number in whatever format they wish and using logic to clean it up for the database. For example, a user could enter 123-456-7890, (123) 456-7890, 123.456.7890, etc and they would all be valid.


1

I'd opt for option 1 due to the ease of use from purely a responsive view point and like said earlier, if you plan to use the area code etc to some how collate your data and categorizes phone numbers. The last thing you would want is that number in separate inputs stacking on mobile or device although it wouldn't be a complete disaster again the con of ...


2

Force a more conscious choice on between system defaults and custom values. On form 2, I would have a checkbox that says "use defaults" or "use system calculated values", selected by default, and make the values grayed out and uneditable when this is selected. If this option is selected, a user will would expect the defaults to change to whatever is ...


2

Go with Example 1. One field for the phone number. Do some quick client side regex on the number the user entered, to account for any egregious errors to save an unecessary call to your server for 800 digit entries or garbled text. Ultimately, you are validating the web form data on the server and sanitizing it before dropping it into your database.


8

A single input field is always easiest for the user — whether it's for a phone number, first and last name, social security number, or any other value that you may think of as being divided into "parts". Luke Wroblewski has written many articles about this with plenty of data to back it up. Design your page for the user, not the database. If you ...


30

When a person dials an actual phone number with their phone, do they type 1-555-555-555 or do they type 15555555555? The only reason for forcing a fixed format is because your back-end can't determine the format it needs. Which is an implementation problem and you're forcing the lack of technical nous onto the end user. That's like saying "we aren't capable ...


0

i think this is the textbook case for they the <output element was implemented in html5. i've seen a few examples styled as knobs, which shows both display input and output: the knob has a marking in one position, showing the user where the input is at all times; as it turns on the dial, the output element is used to illuminate the selected volume at the ...


1

I think you are introducing extra complexity just for the sake of it. A user hates filling out forms and extra time figuring out which fields are optional, mandatory and recommended is just extra cognitive load. Split the form into two sections, mandatory at top, optional at bottom. You can indicate that some of the optional fields are recommended by ...


-1

This would be a really simple approach. In order to ensure maximum clarity, you should be displaying a line of text somewhere next to the form (preferably above it), explaining meaning of what different designations. For recommended fields, you could another, similar designation, perhaps (+). Then you'd have the following: ( * ) - required ( + ) - ...



Top 50 recent answers are included