React Server Actions Need UX States

React Actions and Server Actions can make form submission and server mutations cleaner, but they do not remove the need for product states. Users still need to know what happened.

011. Pending Is an Interface State

When a user submits a form, the interface should show that the request is in progress. Disable unsafe duplicate actions, preserve entered data, and make the waiting state visible without blocking unrelated work.

A silent form submission feels broken even when the backend is working correctly.

Server-side mutations still need client-visible states.

022. Validation Should Be Specific

Validation errors should point to the field or business rule that failed. Generic failure messages force users to guess and repeat work.

The server may own the rule, but the interface owns the explanation.

033. Optimism Needs Reversibility

Optimistic UI can make applications feel fast, but it should be reserved for actions that can be reversed or corrected cleanly if the server rejects the change.

For high-risk actions, show progress and confirmation rather than pretending the operation already succeeded.

044. Recovery Is Part of the Flow

Network errors, permission failures, and validation conflicts should give users a way to retry, edit, or contact support without losing context.

A clean architecture becomes a good product only when the user experience handles the full request lifecycle.