Tag Info

Hot answers tagged

60

I would progressively reveal details to a user as they need them. Consider what would your smart defaults would be? Are there assumptions that you can make that would get most users most of the way there? A couple you could consider: Sunday and Saturday are typically off days for US workers. Is this true for you? If so, then let's go ahead and default them ...


42

Don't do that, there are different approaches to filling out values, and for some it would be disruptive. For example if the user just wants to change the last digit... A good, non-disruptive alternative would be a small "clear input" button.


36

You could have the input value selected when the user clicks on the input. This way the user can just press backspace or start typing to change the value or copy the value instantly.


36

I would try to use the Google Calendar approach. You spread out the days with an acceptable level of detail/resolution and then the users just drag to mark the time ranges. If a higher level of detail is required, they can fine-tune each time. It took me about 5 seconds to enter these 6 time ranges.


34

As a Stack Overflow / Stack Exchange employee, my guess is that this was a Google Forms doc put together for the specific purpose of gathering addresses this one time. We do this internally a lot to gather information. Using a product like Google Forms allows anyone to get something done without having to involve developers or designers. I imagine the ...


24

In theory the correct answer is no upper limit for name lengths. Allow the user to enter whatever their name is using whatever characters are available to them so that you will never run into a circumstance where someone is prevented from entering their valid real name. In practice that is not possible to implement. There have to be limitations. These ...


21

You'll often find that users will just fill in all fields on a form regardless of whether they're required or not. People don't really read instructions and don't want to risk encountering an issue if they haven't filled in any fields, so they'll often just fill in them all regardless. (This has been somewhat supported by testing by the Baymard Institute - ...


19

Date pickers are helpful when your concerned dates fall within the context of a month or so but not several years apart as jumping between years would require laboriously many clicks. Date selectors are not just helpful in reducing the typing errors but they also standardize the formats when several correct variations are possible. For Americans, the ...


18

Though I don't have an answer behind why all the fields were named the same, I think the idea was to ensure that all potential international addresses could fit into the form design without designing custom forms for every international address. Here are some examples of international addresses Amazon also a generic international format as mentioned in ...


14

6-line addresses (or rather 7-line, including the name of the addressee) do occur. Consider for example a typical UK residential address: Miss S Pollard name 1 Chapel Hill building number and street name Heswall locality BOURNEMOUTH town with a post office BH1 1AA postcode UNITED KINGDOM ...


9

Unfortunately people read less and expect more during action. So regardless if all fields or only a set of fields are required, fields that need input need indication in some form. Every field in your case.


8

It should be a short hint (in you example "Type your username") rather than an example data (ChuckNorris). The reason for this is that Placeholders have the potential to be mistaken for pre-completed fields, especially at a glance. If you have placeholders showing sample data then that increases the possibility of people thinking the field has already been ...


8

Other reasons for using a calendar widget (besides taking care of format): Picking date ranges: from/to, start/end, depart/return dates. Providing custom presets for dates and date ranges such as: "A week from now" or "Month to date". Associating date and time (when time is required). They are inseparable in real-life, why separate them (in different ...


7

You should add a check box that indicates that the number of things are limited. (Thus: An unchecked box indicates that there are unlimited number of items). download bmml source – Wireframes created with Balsamiq Mockups


7

I think it mimics iOS UI style (at least I don't remember such a component before iOS, please correct me if you have some other information): source It is UITableView with style Grouped. Or you can call it "text field group".


7

I would agree repeating the blue button isn't ideal, and not just for the reason it feels cluttered and overwhelming. Also it feels laborious because you have click each button in order to submit it. Basecamp provides a really nice option here for you. Here they give a few lines to input a few email addresses and once you put in 3 email addresses, the form ...


7

Every example you gave would work. One might work better within your design than the other. Your users won't really care about the way the search input pops up. The best search fields are bug free are easy in use give relevant results help users find what they are looking for (auto fill or alternatives) So I would focus more on functionality and less on ...


6

They could be referred to as Grouped Form Fields. It is partly a design trend. I think most people would argue that while it may be visually pleasing, it is not great from a usability standpoint. You could closely group fields without needing to combine them in that way. For example, someone may not realize that they need to tap again to type in a second ...


5

As Luke Wroblewski points out in "Web Form Design", the size of of an input field can help provide your form fields with affordance. The way you've adjusted the field lengths in the billing and shipping sections are good because they provide the user with an idea of what they're expected to enter. It would be a good idea to be consistent and have the input ...


5

There is a very useful part of the Google Places API for this, called Places Autocomplete. You can simply add the event listener to an input box and it will generate place suggestions as you type just like it does on Google, and you can extensively customise the way it shows the search results through the JavaScript API. You then have the option to take the ...


5

The main challenge with inline editing are: Discoverability Clarity of state/When does system save For discoverability, you want to bring up the field outlines when the user moves around naturally. In your example, I would suggest do it on mouse over of the specific bar in the graph and not just the text label. Then on click it should become edit field. ...


5

WHEN They are extremely useful for planning events in the future or for exploring times in the past as well as planning ranges for examination of some sort. Use it anytime you could see your user going to their calendar on the wall and attempting to plan the future or examine past events. WHY The calendar is probably one of the greatest examples of ...


5

As a user, I will automatically think that a disabled text input field (or anything looks like this) means that the field is ultimately editable. Either the data that I supply on other fields makes it invalid for editing, or I have insufficient permissions to change the field's value. Bootstrap CSS does have the form-control-static class that you can use to ...


5

The size of the input field should visually present the length of the data the user is asked to put in. If you're asking for a date, no reason to have 300px wide input box, it will only confuse the user when the text to input is only 10 characters (~80px -100px). Same with postal codes, and other "short" data. No need to make the user think "do I really ...


5

Given the diversity of names, I wouldn't... set a floor or ceiling limit on name length, OR even break the name into two separate fields. Depending on the country / cultural background of a person, they may have a more Westernized [first-name] [surname] name, but they may not. Why possibly bar users from entering their complete name because of arbitrary ...


5

Pre-filling input elements with valid default values is a great idea. However, deleting those values when you click on the element is an extremely poor UX choice. You are making the assumption that the only reason someone 'clicks' on an input element is to change the value. That's not so. Entering a field via the keyboard triggers the same events as using ...


5

What I've come up with is using this slider, I've set the default values to 8:00 and 17:00, i think this is much easier to use than having to type in dates manually. Also I might overriding the start/finish default times with the average from previously filled in forms once we have some data to use, but that's just an idea at the moment.


5

The goal of indicators like this is to inform the user when something is different. So, let the form tell you how you should approach it. In general if most of your form is required, state that up front and then flag Optional fields accordingly. Inversely, if most of your form is optional but a few are required, flag the required fields. This short post ...


4

As I rule, I try to avoid using hover for any actions that the user might want to perform. Hover is great for giving out extra information, but an action (or access to an action should be available on click. What will happen if the user is on a touchscreen without hover capabilities? Will that option not be available for him/her?


4

I don't think that both options should be visible at the same time. Having a control that allows to view one option at a time greatly simplifies interface and reduces cognitive load. You need to make a decision which option should be a default one based on business requirements and past usage analytics. I believe tabs allow to solve this problem quite ...



Only top voted, non community-wiki answers of a minimum length are eligible