Guidelines and checklist for text input (Windows Store apps)
Follow these guidelines for adding text input controls to your Windows Store app.
Text input controls let users enter and edit a text or numeric value. Consider these questions when deciding whether to use a text input control.
- Is it practical to enumerate all the valid values efficiently? If so, consider using one of the selection controls instead.
- Is the valid data completely unconstrained? Or is the valid data constrained only by format (constrained length or character types)? If so, use a text input control.
- Does the value represent a data type that has a specialized common control? If so, use the appropriate control instead of a text input control. For example, use a DatePicker instead of a text input control to accept a date entry.
- If the data is numeric:
- Do users perceive the setting as a relative quantity? If so, use a slider.
- Would the user benefit from instant feedback on the effect of setting changes? If so, use a slider, possibly along with an accompanying control.
There are single-line and multi-line text input controls. The next section describes when to use single-line text input controls, and later sections describe multi-line text input controls.
For short strings, use a single-line text input control. This table describes when to use the different types of text input controls.
|Basic data input||
Use single-line text input controls to gather small pieces of text from users.
The following example shows a single-line text box to capture an answer to a security question. The answer is expected to be short, and so a single-line text box is appropriate here. Because the information collected does not match any of the specialized input types that Windows recognizes, the generic "Text" type is appropriate.
|Formatted data input||
Use a set of short, fixed-sized, single-line text input controls to enter data with a specific format.
|Assisted data input||
Use a single-line, unconstrained text input control to enter or edit strings, combined with a command button that helps users select valid values.
|Numeric input||Use a single-line, number input control to enter or edit numbers.|
|Password and PIN input||
Use a single-line password input control to enter passwords and PINs securely.
Use the single-line email input control to enter an email address.
When you use an email input control, you get the following for free:
|URL input||Use the URL input control for entering web addresses.|
|Telephone number input||Use the telephone number input control for entering telephone numbers.|
Use several single-line text boxes to capture many small pieces of text information. If the text boxes are related in nature, you should group them together.
|Provide placeholder text in your single-line text boxes if you believe users need additional instructions for entering a value.|
Make the size of your single-line text boxes slightly wider than the longest anticipated input. If doing so makes the control too wide, separate it into two controls; for example, you could split a single address input into "Address line 1" and "Address line 2".
Set a maximum length. If the backing data source doesn't allow a long input string, limit the input and use a validation popup to let users know when they reach the limit.
Don't use a textarea with a row height of 1 to create a single-line text box. Instead, use the input type="text" element.
Don't use placeholder text to pre-populate the text control. Text boxes clear placeholder text when users use the control. Use the "value" attribute instead.
Don't use a text box as a search box. It's common practice in web pages to use an input element to create a search box. However, you create a much better and more consistent experience when you use the Search charm instead. The Search charm provides a consistent searching experience that your app can plug into. For more info, see Adding search.
Don't put another control right next to a password input box. The password input box has a password reveal button for users to verify the passwords they have typed. Having another control right next to it might make users accidentally reveal their passwords when they try to interact with the other control. To prevent this from happening, put some spacing between the password in put box and the other control, or put the other control on the next line.
When users need to enter or edit long strings, use a multi-line text control. There are two types of multi-line text input control: the plain text input control (the textarea element) and the rich text control (an element, such as a div, that has its contenteditable attribute set to true).
- If the primary purpose of the multi-line text box is for creating documents (such as blog entries or the contents of an email message), and those documents require rich text, use a rich text box.
- If you want users to be able to format their text, use a rich text box.
- When capturing text that will only be consumed, and not redisplayed at a later time to users, use a plain text input control. For example, suppose you have a survey; the user completes the survey and the data is sent to some server, but the user doesn't ever see it again. It is generally unnecessary to allow users to style this text.
- For all other scenarios, use a plain text input control.
|Use a font that represents the feel of your app.|
|Make the height of the text control tall enough to accommodate typical entries.|
When capturing long spans of text where users are expected to keep their word count or character count below some maximum, use a plain text box and provide a live-running counter to show the user how many characters or words they have left before they reach the limit. You will need to create the counter yourself; place it near the text box and update it dynamically as the user enters each character or word.
|Don't||Don't let your text input controls grow in height while users type.|
|Don't use a multi-line text box when users only need a single line.|
|Don't use a rich text control if plain text is adequate.|
Build date: 11/29/2012