Design thinking for developers, forms design is more beautiful
Programmers are usually people who do not have good sense of design. Therefore, Techtalk will introduce some perspectives and knowledge about this field to help us improve the ability to apply design concepts into products! Let's see it.
Common designers and remedies
From signup flow, a multi-view stepper, to monotonous data entry interface, the form is one of the most important components of digital product design. This article focuses on the principles that should and should not be in the form design. Remember, these are just common ground and there are always exceptions to every rule.
The form should only have 1 line
Label above
Group labels with their input
Avoid complete capitalization
Show all options if only under 6
Avoid using placeholder text as labels
Avoid using placeholder text as labels
Put checkboxes (and radios) from top to bottom for easy scanning
CTA (Call to action) is clear
Displays internal errors
Use only inline validation after the user has finished typing (unless that information is useful in the input process)
Don't hide the basic help text
Distinguish clear main actions and extra actions
Express data entry requirements right in the input field
Uncheck the * and specify fields that are not required
Group of similar information
Asking for what?
Discard non-mandatory fields and find other ways to collect data. Test types are also a good way with high response rates to replace questions. Moreover, automatic analysis data and social channels, conversion UI, SMS, email, voice, ORN, location, fingerprints, etc. are gradually becoming the statistical channel of modern times.
Make it fun
Life is short. Nobody wants to sit down and fill a long, long form. Be so close, funny, strong in contact. Do something no one expected. The role of a designer is to show the company's brand in a way that elicits emotional reactions from users. If done properly, you will be able to increase the completion rate (should still follow the rules above).