A form is a group of controls that collect and submit data from users. Forms are typically used for settings pages, surveys, creating accounts, and much more.
UNV 60101 Universal Self-Adhesive Permanent File Folder Labels UNV60101 Universal Self-Adhesive Permanent File Folder Labels Universal 60101 Typewriter-Compatible File Folder Labels, 3-7/16' x 9/16', White, 248/Pack, Labels. Univision univision noticias universal studios orlando universal orlando university of phoenix unsv univox surveys universal studios university of delaware unsw. Uv 5re unv 60101 univ 6 unv 60101 template unsy 601 uns 66286 uns 603 uns 636 uns 65007 uns 6-48 thread uns 620 unsy 605 unv 60101 label template uns. Universal Labels provides fast online printing for both homes and businesses. We provide high quality address or shipping labels, postage labels, thermal labels and direct thermal transfer labels Imp Links.
This article discusses design guidelines for creating XAML layouts for forms.
When should you use a form?
A form is a dedicated page for collecting data inputs that are clearly related to each other. You should use a form when you need to explicitly collect data from a user. You might create a form for a user to:
- Log into an account
- Sign up for an account
- Change app settings, such as privacy or display options
- Take a survey
- Purchase an item
- Give feedback
Types of forms
When thinking about how user input is submitted and displayed, there are two types of forms:
1. Instantly updating
Use an instantly updating form when you want users to immediately see the results of changing the values in the form. For example, in settings pages, the current selections are displayed, and any changes made to the selections are applied immediately. To acknowledge the changes in your app, you will need to add an event handler to each input control. If a user changes an input control, then your app can respond appropriately.
2. Submitting with button
The other type of form allows the user to choose when to submit data with a click of a button.
This type of form gives the user flexibility in responding. Typically, this type of form contains more free form input fields, and thus receives a greater variety of responses. To ensure valid user input and properly formatted data upon submission, consider the following recommendations:
- Make it impossible to submit invalid information by using the correct control (i.e., use a CalendarDatePicker rather than a TextBox for calendar dates). See more on selecting the appropriate input controls in your form in the Input Controls section later.
- When using TextBox controls, provide users a hint of the desired input format with the PlaceholderText property.
- Provide users with the appropriate on-screen keyboard by stating the expected input of a control with the InputScope property.
- Mark required input with an asterisk * on the label.
- Disable the submit button until all required information is filled in.
- If there is invalid data upon submission, mark the controls with invalid input with highlighted fields or borders, and require the user to resubmit the form.
- For other errors, such as failed network connection, make sure to display an appropriate error message to the user.
Layout
To facilitate the user experience and ensure that users are able to enter the correct input, consider the following recommendations for designing layouts for forms.
Universal Label Template 60101 Zip Code Free
Labels
Universal Label Template 60101 Zip Code Map
Labels should be left-aligned and placed above the input control. Many controls have a built-in Header property to display the label. For controls that don't have a Header property, or to label groups of controls, you can use a TextBlock instead.
To design for accessibility, label all individual and groups of controls for clarity for both human and screen readers.
For font styles, use the default UWP type ramp. Use TitleTextBlockStyle for page titles, SubtitleTextBlockStyle for group headings, and BodyTextBlockStyle for control labels.
Spacing
To visually separate groups of controls from each other, use alignment, margins, and padding. Individual input controls are 80px in height and should be spaced 24px apart. Groups of input controls should be spaced 48px apart.
Columns
Creating columns can reduce unnecessary white space in forms, especially with larger screen sizes. However, if you would like to create a multi-column form, the number of columns should depend on the number of input controls on the page and the screen size of the app window. Rather than overwhelm the screen with numerous input controls, consider creating multiple pages for your form.
| Do | Don't |
|---|
Responsive layout
Forms should resize as the screen or window size changes, so users don't overlook any input fields. For more information, see responsive design techniques. For example, you might want to keep specific regions of the form always in view, no matter the screen size.
Tab stops
Users can use the keyboard to navigate controls with tab stops. By default, the tab order of controls reflects the order in which they are created in XAML. To override the default behavior, change the IsTabStop or TabIndex properties of the control.
Input controls
Input controls are the UI elements that allow users to enter information into forms. Some common controls that can be added to forms are listed below, as well as information about when to use them.
Text input
| Control | Use | Example |
|---|---|---|
| TextBox | Capture one or multiple lines of text | Names, free form responses or feedback |
| PasswordBox | Collect private data by concealing the characters | Passwords, Social Security Numbers (SSN), PINs, credit card information |
| AutoSuggestBox | Show users a list of suggestions from a corresponding set of data as they type | Database search, mail to: line, previous queries |
| RichEditBox | Edit text files with formatted text, hyperlinks, and images | Upload file, preview, and edit in app |
Selection
| Control | Use | Example |
|---|---|---|
| CheckBox | Select or deselect one or more action items | Agree to terms and conditions, add optional items, select all that apply |
| RadioButton | Select one option from two or more choices | Pick type, shipping method, etc. |
| ToggleSwitch | Choose one of two mutually exclusive options | On/off |
Note: If there are five or more selection items, use a list control.
Lists
| Control | Use | Example |
|---|---|---|
| ComboBox | Start in compact state and expand to show list of selectable items | Select from a long list of items, such as states or countries |
| ListView | Categorize items and assign group headers, drag and drop items, curate content, and reorder items | Rank options |
| GridView | Arrange and browse image-based collections | Pick a photo, color, display theme |
Numeric input
| Control | Use | Example |
|---|---|---|
| Slider | Select a number from a range of contiguous numerical values | Percentages, volume, playback speed |
| Rating | Rate with stars | Customer feedback |
Date and Time
| Control | Use |
|---|---|
| CalendarView | Pick a single date or a range of dates from an always visible calendar |
| CalendarDatePicker | Pick a single date from a contextual calendar |
| DatePicker | Pick a single localized date when contextual info isn't important |
| TimePicker | Pick a single time value |
Additional Controls
For a complete list of UWP controls, see index of controls by function.
For more complex and custom UI controls, look at UWP resources available from companies such as Telerik, SyncFusion, DevExpress,Infragistics, ComponentOne, and ActiPro.
One column form example
This example uses an Acrylic master/detaillist view and NavigationView control.
Two column form example
This example uses the Pivot control, Acrylic background, and CommandBar in addition to input controls.
Customer Orders Database Sample
To learn how to connect form input to an Azure database and see a fully implemented form, see the Customers Orders Database app sample.