Menu

Review AI empty-state copy for tone before you merge the component
📰

Review AI empty-state copy for tone before you merge the component

DEV Community: frontend·Sherotree·6 days ago
#5pobF6oz
#devtofrontend#devto#dev#empty#copy
Reading 0:00
15s threshold

Agents will happily ship an empty state that looks right: illustration slot, primary button, secondary link. The string inside is often the bug — “Oopsie! No data found!!” next to a finance table, or “You haven’t created anything yet” when the user lacks permission, not motivation.

I’ve started reviewing empty-state copy for tone as its own checklist item, separate from layout. The component can be perfect and still speak in the wrong register.

What goes wrong in AI empty copy

Patterns that show up constantly:

Blame — “You haven’t…”, “You failed to…”, when the system or permissions are the real cause

Fake cheer — “Awesome!”, “Oopsie!”, emoji piles in a product that otherwise speaks calmly

Jargon — “No entities hydrated”, “Zero rows in projection”

Dead ends — witty line, no next step

Wrong audience — engineer voice in a customer admin, or marketing voice in an internal tool

Lying specificity — “Upload a CSV” when the empty state is actually a filter with zero matches

Layout review won’t catch these.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.