Skip to Content

How do I design empty states to make the user feel humanity... not loneliness?

20 January 2026 by
ايكو ميديا للتسويق الرقمي, Khaled Taleb
| No comments yet

Introduction


‫‬

Don't make the user stare at a blank screen.

‫‬

Empty states in applications are not just empty spaces or screens saying 'no data'.

They are sensitive psychological moments, silent UX touchpoints with a deep impact, where the user appears hesitant, confused, or waiting without guidance.

‫‬

There is no error.

There is no loading.

Just... nothing.

‫‬

And in this silence, many products unintentionally tell the user:

"You are not in the right place yet."

‫‬

And here lies the opportunity:

You either lose them or gain their trust.

‫‬

I learned the hard way that empty states are not placeholders.

They are moments of dialogue.

‫‬

In this article, I share how I design empty states to feel human, understandable, and intentional — not mechanical or forgotten.

‫‬

Why are empty states more important than you think?

‫‬

Empty states appear in critical situations, such as:

‫‬

  • The first use of the application

  • After data deletion

  • When filters are applied that hide all results

  • When a 'silent' error occurs without a clear message

‫‬

These are not interface gaps... but emotional gaps.

‫‬

A smart designer does not leave the user alone there, but meets them with a calm, clear, and encouraging language.

Ignoring it = hesitation.

Designing it well = a sense of guidance.

‫‬

The golden rule: empty states are emotional moments.

‫‬

The user does not think:

‫‬

"This is an empty state."

‫‬

But thinks:

‫‬

  • Did I make a mistake?

  • What do I do now?

  • Is this application even useful?

‫‬

Your good design should answer these questions immediately.

‫‬

1. Start with reassurance… not commands.

‫‬

The worst thing you can do is jump straight to instructions.

‫‬

❌ "No data available"

✅ "It seems you haven't added anything yet — let's get started together"

‫‬

Reassurance removes blame and anxiety.

It makes the user feel like they are in a conversation, not an interrogation.

‫‬

2. Speak as a human… not as a system.

‫‬

System language is cold.

Human language builds trust.

‫‬

The difference is not cosmetic, but psychological.

Words design the feeling before the interface.

‫‬

3. Always answer the question: "What now?"

‫‬

An empty state without guidance = dead end.

‫‬

Every empty state should contain:

‫‬

  • One clear step

  • Only one action

  • Without confusion

‫‬

For example:

‫‬

  • Create your first project

  • Add a new item

  • Adjust the filters

‫‬

Just one… is enough.

‫‬

4. Match the tone with the context.

‫‬

Not all empty states are happy.

‫‬

An empty state after the first use ≠ an empty state after an error.

Tone is more important than colours.

The message is more important than the illustration.

‫‬

5. Use visual elements sparingly.

‫‬

Illustrations are optional.

Clarity is mandatory.

‫‬

And if you use images:

‫‬

  • Keep them simple.

  • Avoid repetitive stock illustrations.

  • Make them supportive, not distracting.

‫‬

A smart icon > a loud illustration.

‫‬

Read also:UX/UI design trends in 2026: when the product becomes the "hero".


6. Design it as if it is a disguised onboarding.

‫‬

The first empty state is the first usage lesson.

‫‬

It should clarify:

‫‬

  • What is the purpose of this section?

  • What is its value?

  • How do I get started?

‫‬

Here you are setting expectations.

‫‬

7. Don't hide the emptiness behind skeletons forever.

‫‬

Skeleton loaders are great... but sometimes nothing is coming.

‫‬

Quickly show the empty state when:

‫‬

  • There is actually no data.

  • The user is the one who should take action.

  • Waiting will not solve the problem.

‫‬

Clarity is better than false hope.

‫‬

8. Accessibility does not disappear with emptiness.

‫‬

Emptiness does not mean neglect.

‫‬

Make sure to:

‫‬

  • Readable contrast.

  • Clear focus order.

  • Understandable text (not just icons).

  • Support for screen readers.

‫‬

An inaccessible empty state = a flawed experience.

‫‬

A quick checklist before launch.

‫‬

Ask yourself:

‫‬

  • Does this message reassure the user?

  • Does it explain what is missing?

  • Does it suggest one clear step?

  • Does it feel truly human?

  • Would I feel comfortable seeing it?

‫‬

If in doubt... rewrite it.

‫‬

What I personally avoid.

‫‬

“No data available.”

‫‬

  • Messages that make the user feel guilty.

  • Too many meaningless buttons.

  • Overly elaborate graphics.

  • Silence.

‫‬

Empty states deserve genuine intent.

‫‬

In summary.

‫‬

Empty states are mini-conversations.

Treat it as a space to build trust, not as a void to be filled.

‫‬

When you design with empathy,

“nothing” transforms into the beginning of a relationship.

‫‬

With Echo Media

‫‬

If you are a UX/UI designer or a digital product owner,

review the empty states in your app now.

‫‬

Does it reassure the user?

Or does it leave them alone in front of a silent screen?

‫‬

At Echo Media | Echo Media for Digital Marketing, we help you to:

‫‬

  • rewrite UX copy in a human language

‫‬

  • improve empty states to increase engagement

‫‬

  • turn drop-off points into trust points

‫‬

‫📩 Contact us now and let every screen — even the empty ones — work in your favour.

‫‬

Sign in to leave a comment