Forms are where product quality leaks

A form is not the first screenshot. It is the pause, the mistake, the retry, and the half-success after the request leaves the browser.

The layout can look finished while the workflow is brittle. Real users navigate with keyboards, lose focus, return to stale drafts, submit twice, hit a permission change, or wait through a request that succeeded even though the page timed out.

The implementation needs distinct ownership for those states. Local validation can catch obvious field errors. The server should own uniqueness, permission, and current-state checks. Pending state should show that the request is active and prevent duplicate intent. Partial success should say what saved and what did not.

Error copy is part of the interface contract. “Something went wrong” does not tell the user which field or action failed, why, or what to try next. A retry also needs idempotency: if the browser sends the same intent twice, the server should recognize it.

Long forms need draft recovery. Accessible forms need labels, focus movement, and an error summary that can be reached without a mouse. Those are not polish items. They decide whether the workflow survives ordinary use.

The boring states are where the product tells the truth.