Learn

/

Feedback

Feedback

4 patterns

Loading states, empty states, error screens, and confirmation dialogs that keep users informed. You'll hit this when users stare at a blank screen during data loading or accidentally delete something with no warning.

Avoid

Recent Orders


Prefer

Recent Orders

Why avoid

A blank screen during loading provides no feedback at all. Users cannot tell whether the page is broken, still loading, or empty. This uncertainty leads to impatient clicks, page refreshes, and a perception that the application is slow or unreliable.

Why prefer

Skeleton screens show the shape of upcoming content while data loads, giving users a sense of progress and structure. They feel faster than blank screens because the user can see that something is happening and can anticipate where content will appear.

Nielsen Norman Group: Skeleton screens
Avoid

No results found.


Prefer

No results found

Try adjusting your filters or search with different keywords.

Clear filters

Why avoid

A bare empty state (just "No items" or a blank area) leaves users stranded. They do not know if the feature is broken, if they need to do something first, or where to go next. Every empty state is a chance to guide the user, and a blank screen wastes that opportunity.

Why prefer

A helpful empty state explains why there is no content and offers a clear next step (such as a "Create your first project" button). It turns a dead end into an onboarding opportunity and reduces confusion for new users who do not know what to do.

Nielsen Norman Group: Empty state design
Avoid

Error 500: ECONNREFUSED localhost:5432
at TCPConnectWrap.afterConnect


Prefer

Something went wrong

We could not load your data. Please try again in a few moments.

Try again

Why avoid

Technical error messages with stack traces, error codes, or developer jargon are meaningless to most users. They feel alarming and unprofessional. Users do not know what a "500 Internal Server Error" means or what they should do about it, so they leave.

Why prefer

Friendly error screens use plain language, explain what happened, and offer recovery options (retry, go home, contact support). They reassure the user that the problem is temporary and provide a clear path forward instead of a dead end.

Nielsen Norman Group: Error message guidelines
Avoid

Account

Manage your account settings and preferences.

Delete account


Prefer

Delete account?

This will permanently remove all your data. This action cannot be undone.

Cancel

Delete

Why avoid

Performing destructive actions immediately with no confirmation is dangerous. A single misclick can delete data permanently, and the user has no way to prevent it. Even with an undo feature, a confirmation step for high-impact actions provides essential peace of mind.

Why prefer

A confirmation dialog for destructive actions (delete, remove, cancel subscription) gives users a chance to reconsider. The dialog should clearly state what will happen and use specific language like "Delete 3 files" instead of a generic "Are you sure?" prompt.

Nielsen Norman Group: Confirmation dialogs