Tag Info

Hot answers tagged

50

Emails were never intended as a form of chat type messaging. Remember that they are electronic versions of mail, so trying to modify them to be something they weren't designed for is a mistake. As to the reasons why we write the subject line first: The subject line is part of the header of an email (see the original RFC822 and the newer RFC5322), and ...


35

Do not update what users enter when they're still typing. It fuddles up their ability to edit as they type, and it makes the field a moving target. If you were to type 25000 straight, no typo's, no backspacing, it might make sense to format it right when you're done. However, what happens when you enter a 0 between the 2 and the 5? Or when you hit backspace? ...


31

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 ...


20

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 - ...


18

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

Firstly, the thousands separator is not common among all regions of the world. When in doubt the recommended solution (SI/ISO 31-0 standard) is to use a non-breakable thin space as a separator. You also have to take into account that not all countries group by thousands. From Wikipedia: In China, comma and space are used to mark digit groups ...


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 ...


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 ...


11

We had the same question and after a lot of heated discussion we decided to not format while the user was editing. While the user type he can add grouping or decimal separators if he would like and as soon as he blurs we add them if the user didn't. so the user can type 100000 100,000 100,000.00 100000.00 but as soon as he blurs we format it as ...


9

This may be similar to the question Why don't ATMs give you cash before your card?: Users follow the tasks in sequence, but regard the task as completed once they have achieved their goal. Subsidiary steps are easy to abandon at this point. The goal of writing an email is conveying information. Once the message body is complete that goal is supposedly ...


9

I'd like to approach this question from a bit of a different perspective than that of other answers. What's In An Order The essential question posed is questioning the philosophy and methodology of ordering form fields. On the one hand, one might wish to order them in the order that the author would be expected to write them. This is a perfectly sensible ...


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

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.


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

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

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 ...


6

As a reader, I want to know "Why are you sending me this email?" so I know whether it is worth my while reading it now, instead of doing all those other important things on my to-do list. As a reader, I expect the writer to know why they are sending me the email, and more to the point, I hope they will know why they are sending me the email before they ...


6

I think all of these are quite functional, but there are pros and cons for each one: 1st: may need a lot of vertical space. 2nd: does not consume any additional space at all, but will disappear once user enters this field. It's quite popular though, and not a bad practice. 3rd: again, should the example text be longer, it may force you to make the left ...


6

If .yoururl.com is not editable, it should be removed from the input bar. download bmml source – Wireframes created with Balsamiq Mockups Give an example to reinforce what the expected input is and also, if you want, what the output will look like. On second thought, you can let the user type in the entire URL. URL parsing isn't a ...


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

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

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

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

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 ...


4

Be careful that this notation is not common for all users. Simplified table of numbers formatting : 1000000 < nobody that cares about readability 1 000 000 < Sweden, France 1,000,000 < UE 1.000.000 < Germany Is it going to be an amount of money ? Because if its so I would recommend you to input right to left (have a look to currency ...


4

Client-side validation can be helpful, but you need to be very careful how you implement it; it's easy to make it unhelpful to the user. For example, if you silently ignore non-numeric characters, then a user quickly typing '12.34' might not realise that the field has ignored their decimal point and accepted the text as '1234'. Another example; if you ...



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