Blog · Getting forms right
User Experience on Web Forms
Labels, placeholders, no-reload submissions, confirmation messages, and the delivery problems that start after someone clicks submit.
Placeholders are not labels
A placeholder disappears as soon as someone starts typing. That makes it a weak place to put information the user may need later, especially on longer forms, mobile screens, or forms with validation errors.
Labels should usually stay visible. Placeholders can still help, but they should act as examples or formatting hints, not as the only explanation of what a field means.
No page reload is not enough
AJAX form submissions can make a form feel faster and calmer, but only when the state changes are obvious. The button should show progress, duplicate submissions should be prevented, errors should land near the field that needs attention, and success should feel final.
A form that silently clears itself after submit is not a good experience. People need confirmation that their message went somewhere.
The form experience continues after submit
The technical work does not end when the browser says the form was submitted. Someone has to receive the email, the CRM record, the notification, or the internal task.
That is where form UX turns into operations: confirmation messages, routing, tracking, spam protection, and email deliverability all shape whether the form actually works.