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
Placeholder text disappears as soon as someone starts typing. That makes it a poor place for anything they may need later, especially on long forms, on phones, or on forms that show validation errors.
Labels should usually stay visible. Placeholders can still help as an example or a format hint, but they shouldn't be the only explanation of what a field is for.
Submitting without a page reload
AJAX submissions, which send the form without reloading the page, can make it feel faster and calmer, but only when every change of state is obvious. The button should show progress. Duplicate submissions should be blocked. Errors should appear next to the field that needs fixing, and success should look final.
If your form quietly clears itself after submit, people are left wondering whether it worked. They need confirmation that their message went somewhere.
The form experience continues after submit
The job isn't done when the browser says the form was submitted. Someone still has to receive the email, the CRM record, the notification, or the internal task.
This is where form design becomes an operations question. Confirmation messages, routing, tracking, spam protection, and email deliverability all decide whether the form actually works.