Forms & inputs
A field that just says 'Your phone' leaves users guessing at the format you'll accept
Vague fields make users guess the format and trip validation. Show the expected format inline — a sample value, a prefix, a picker — so they get it right first.
A form field labelled only “Your phone” with a hint to “add your country code” pushes the work onto the user: should there be dashes, spaces, a plus sign, a leading zero? The same guesswork repeats on a company size that might be a number or a range, and a website field that may or may not want https. Every guess that misses ends in a validation error and a correction loop — friction the form created by staying vague.
The fix is to show the expected format at the field itself. A phone input with a country-code selector and a sample like “+1 (555) 356-7832,” a company-size dropdown of ranges, and a website field with a fixed “http://” prefix tell the user exactly what a valid answer looks like — and often make an invalid one impossible to type. A concrete example communicates faster than any written rule.
Lean on structure wherever you can, then pair it with the right keyboard for each field type so typing the format is effortless on mobile. Be careful using placeholders as the example — they vanish the moment the user starts typing, so keep a persistent label or move the sample into helper text. For anything that still slips through, the error message should echo the same valid example.
Because an unformatted field makes the user guess your rules, and a wrong guess ends in a validation error and a re-do. Should the phone number include the country code, dashes, spaces? Is company size a single number or a range? Does the URL need https? Showing the expected format inline answers all of that before they type, so they get it right the first time and complete the form faster.
Prefer structure over instructions. A masked phone field with a country-code selector, a dropdown of size ranges, or a fixed 'http://' prefix guides input by design so a wrong format is hard to enter at all. Where you can't structure it, use a realistic sample value — '+1 (555) 356-7832' — as a hint. A concrete example communicates faster than a written rule like 'include your country code.'
Be careful with placeholders — they disappear the moment the user starts typing, taking the format guidance with them right when it's needed. If the field has a persistent label above it, a placeholder example works. Otherwise put the sample in helper text below the field, or build the format into the input with a mask or prefix so the guidance can't vanish.
Yes. Inputs that carry their own structure — country-code pickers, dropdown ranges, prefixes, and masks — make many invalid entries impossible rather than just discouraged. That cuts the number of errors users hit and the number of correction loops they have to run, which is the whole point: fewer failed submits and more completed forms.
