For specific Windows Forms Application rules, go to Rules to Better Windows Forms Applications.
There are different ways to align your form labels and each has its own pros and cons.
Labels are essential for guiding users on what information to enter in a form field. To improve readability and consistency, keep labels clean and concise. Avoid unnecessary words and don’t end them with a colon (:), which is a common but outdated practice.
Consistency is a key factor of software development, designing applications that minimise the learning curve through consistent use of componentry and functionality. If buttons with similar functionality are named inconsistently across a web application, it can cause a confusing experience for its users. For example, the buttons used to close a form should be named consistently across your application.
Additionally, buttons should have clear names so the user knows what to expect. For example, it is unclear if a button named Close will save (or not save) when closing, so Cancel would be clearer. A Save button alone is not explicit about the following action for the form (It could close or remain open).
While "OK" buttons were the standard convention with operating systems of the past, web applications should use a more user-friendly approach to dialog boxes. Instead of "OK" buttons to confirm an action the users want, it’s more efficient and effective to give them button that is labeled with that specific action.
The words we choose can significantly impact user experience. One such area of careful consideration is the language surrounding user authentication.
Usually there are problems fitting buttons next to datagrids or listboxes when trying to imply that those buttons add functionality to the datagrid or listbox.
When there are too many choices always Default to the most common ones. Then add a checkbox to allow the advanced users to turn off the common choices.
If the form controls are different entities, they usually have different data and different validation, thus they should not be combined. Having the controls separated also make the form easier to read.
For any case of 'Add New', choose to open a new window (popup) for entering data.
- Do you know how to align form labels?
- Do you avoid clutter in labels?
- Do you know how to label web-based form buttons consistently?
- Do you replace ‘OK’ buttons with clear action labels?
- Do you use right terms for user authentication?
- Do you have a label tag for the fields associated with your input?
- Do you align your Add/Edit/Delete buttons horizontal and bottom right?
- Do you avoid "Data Junk" (data not manually entered by yourself)?
- Do you avoid combining different entities?
- Do you avoid doing an embedded 'Add'?
- Do you avoid using menus for ComboBox maintenance?
- Do you avoid using one form for data entry?
- Do you avoid using plain textboxes for notes?
- Do you create a popup form for editing details?
- Do you follow the control size and spacing standards?
- Do you group related fields by using FieldSet?
- Do you use HTML "maxlength" attribute to limit number of characters on input fields?
- Do you have consistent way to store a same field?
- Validation - Do you avoid capturing incorrect data?
- Do you know the correct way to develop web-based data entry forms?
- Do you format date selectors to include the weekday?
- Do you make text boxes show the whole query?
- Do you provide hints for filling non-common fields?
- Authentication - Do you have a 'Forgot your password' link?
- Do you provide red errors next to the field?
- Do you trim starting and trailing whitespaces in input fields?
- Do you provide the user Drill-Downs and Drill-Arounds?
- Do you save the last user's selections?
- Do you use the concept of drafts?