Forms & inputs tips

9 tips curated around Forms & inputs best practices.

Ctrl K

UX tip graphic titled 'Explain why you need required fields.' Both panels show a mobile lead form ending in a 'Schedule a demo' button. The left panel marked with a red X asks for Full name, Email address, Phone number, and Company name with no explanation of why any of it is needed. The right panel marked with a green checkmark shows the phone number field with a short reassurance line beneath it — 'Only used for delivery issues' next to a small info icon — so the user understands why the sensitive field is required before filling it in. BRIX Templates branding at the bottom.

Forms & inputs

Jul 6, 2026

A one-line reason beside a sensitive field turns reluctance into a filled-in answer

Users hesitate to share a phone number without a reason. Add a short line explaining why each sensitive field is needed to build trust and completion.

Forms & inputs

Jul 2, 2026

When users can see what's required, they fill the form in instead of second-guessing it

Unmarked form fields make every input feel mandatory. Mark required fields with an asterisk and tag the rest 'Optional' so users complete forms faster.

UX tip graphic titled 'Make verification codes easy to enter.' The left panel marked with a red X shows a mobile screen headed 'Verify with code' with a single cramped text field containing a hard-to-read string '12QvrZ345', a faint 'Didn't receive a code?' link, and a 'Continue' button. The right panel marked with a green checkmark shows a screen headed 'Verification Code' with the subline 'Enter the 6-digit code sent to your phone ending in 6543', six individual digit boxes (showing 8, 4, 1 and three empty), a 'Resend code' link, and a 'Verify code 00:53' button with a countdown. BRIX Templates branding at the bottom.

Forms & inputs

Jun 13, 2026

The code step is where a logged-in user can still become a lost one

A clumsy code field stalls users at the last step. Split digits into boxes, trigger the number pad, and confirm where the code was sent to keep them moving.

UX tip graphic with the title 'Use language anyone can understand.' Two contact form cards side by side. The left card marked with a red X shows the formal heading 'Inquiry submission form' with the subtext 'Please complete the information so an advisor can process your request', a 'Full name' field with placeholder 'Indicate your full name', a 'Description of inquiry' field with placeholder 'Provide a detailed description', and a muted 'Submit request' button. The right card marked with a green checkmark shows the friendly heading 'How can we help?' with the subtext 'We reply within 24 hours', a 'Your name' field with the example email 'mattbricks@email.com', a 'Your message' field with placeholder 'Tell us what's going on…', and a prominent purple 'Get in touch' button. BRIX Templates branding at the bottom.

Forms & inputs

May 23, 2026

Form copy that sounds like a contract makes users hesitate before they fill it in

Bureaucratic form copy slows users down and breaks trust. Replace formal language with conversational labels so users complete forms faster and with less doubt.

UX tip graphic with the title 'Match input fields with the appropriate keyboard type.' Two mobile form views side by side showing Phone and Email fields: the left view marked with a red X shows a QWERTY text keyboard for a phone number field, the right view marked with a green checkmark shows a numeric keypad for the same phone number field. BRIX Templates branding at the bottom.

Forms & inputs

Apr 8, 2026

The right keyboard for each field is the kind of detail users notice when it's wrong

Showing a text keyboard for number fields forces users to switch modes. Set the right input type so the correct keyboard appears automatically.

UX tip graphic with the title 'Use real-time validation to guide users and reduce errors.' Two form cards side by side showing a 'Join our community' form: the left card marked with a red X shows a generic 'Please verify all inputs and try again' error after submission with a red 'Try again' button, the right card marked with a green checkmark shows an inline 'Invalid email address' error directly below the email field with a red border highlight. BRIX Templates branding at the bottom.

Forms & inputs

Apr 2, 2026

Catch errors as they happen, not after the user thinks they're done

Generic post-submit errors leave users guessing what went wrong. Inline validation checks each field on blur and shows specific fixes instantly.

Forms & inputs

Mar 18, 2026

Users finish more forms when each step looks like it only takes a moment

A single long form overwhelms users before they start. Split it into multi-step sections with a progress bar to reduce perceived effort.

Side-by-side comparison of two 'Contact our team' form cards: the left card uses only placeholder text as labels which disappear when a user types, while the right card shows persistent labels above each input field that remain visible throughout the interaction.

Forms & inputs

Mar 9, 2026

Labels that disappear when users type leave them guessing in the middle of a form

Placeholder-only fields lose their label the moment a user types. Persistent labels above each input keep context visible throughout.

Side-by-side comparison of two forms: the left shows a long form with six fields — Name, Email address, Phone number, Address, Company, and Job position — with no visible submit button, while the right shows a shorter form with four fields and a purple 'Get in touch' button.

Forms & inputs

Mar 9, 2026

Every field you ask for is a hurdle between the user and the submit button

Every field you add to a form is a reason to stop. Remove non-essential fields and more users will complete it.