Overview

Overview

Summary

This project redesigns empty state communication across the Mercado Libre ecosystem to make it clearer, more accessible, and more actionable. Through ecosystem-wide mapping, we identified inconsistencies and introduced a more contextual and cohesive UI system.


Target

Mercado Libre users across internal and external platforms.


Goals

  1. Provide clear guidance on next steps or the absence of actions.

  2. Replace generic messages with contextual, situation-specific copy.

  3. Improve accessibility and visual consistency using the design system.



KPIs

  1. Fewer errors or repeated actions caused by unclear empty states.

  2. Higher task completion after encountering an empty state.

  3. Better accessibility compliance (contrast, clarity, text support).

Deliverables:

Research

Research

Cursor

Cursor

Figma

Figma

Website Design

Website Design

Framer Development

Framer Development

UI/UX Design

UI/UX Design

Year

/

2023

Client

/

Mercado Libre

Insights

Insights

Starting Point.

Starting Point.

01

Lack of guidance

Empty states often describe the situation but don’t clearly tell users what to do next.

Messages lack context

Generic copy fails to explain why the empty state happens, increasing confusion.

02

Inconsistent and inaccessible UI

Visual inconsistencies and low contrast reduce clarity and trust across the ecosystem.

03

01

Lack of guidance

Empty states often describe the situation but don’t clearly tell users what to do next.

Messages lack context

Generic copy fails to explain why the empty state happens, increasing confusion.

02

Inconsistent and inaccessible UI

Visual inconsistencies and low contrast reduce clarity and trust across the ecosystem.

03

UX Research &

UX Research &

Mapping.

Mapping.

UX Writer

UX Writer

Design process.

Design process.

The component was created by first mapping existing empty states across the ecosystem to identify common patterns and issues. Based on these findings, a standardized component was designed following the Andes design system, focusing on clarity, consistency, and accessibility. Communication principles prioritized clear guidance, contextual messaging, and action-oriented language.

The component was created by first mapping existing empty states across the ecosystem to identify common patterns and issues. Based on these findings, a standardized component was designed following the Andes design system, focusing on clarity, consistency, and accessibility. Communication principles prioritized clear guidance, contextual messaging, and action-oriented language.

Design & Content

Design & Content

Guidelines.

Guidelines.



First-use empty states

They appear when a user accesses a section for the first time and no data is available yet.
They are divided into:


  1. Guidance-driven: when the next action depends on the user.

  2. Informational: when the action depends on a third party or an external process.





Structure:

Title: Not yet + [past action] + [noun]
Example: “You haven’t uploaded products yet”

  • Description: When + [action in present/subjunctive sense] + [value proposition]
    Example: “Once you upload them, you’ll be able to manage them and track their performance.”

  • CTA: Infinitive verb
    Example: “Upload products”





No-results empty states

No-results empty states appear when a user performs a search or applies filters and the system returns no matches.

Unlike first-use empty states, in this case there was a prior user action, but no content is available as a result of that action.



Structure:

Title: Not yet + [past action] + [noun]
Example: “You haven’t uploaded products yet”

  • Description: When + [action in present/subjunctive sense] + [value proposition]
    Example: “Once you upload them, you’ll be able to manage them and track their performance.”

  • CTA: Infinitive verb
    Example: “Upload products”




Structure:

Base structure:
No + verb (find, show, list, etc.) + [noun] + [context]
Example: “We couldn’t find products with these filters.”

  • Verb: should express what the system attempted to do and couldn’t (e.g. find, show, return, list).

  • Noun: the type of expected content (e.g. products, results, orders, listings).

  • Context (optional): can be added, such as “with this search,” “based on the applied filters,” or “in this period.”

Description

  • Briefly explains what the user can do to change the state and get results.

  • Recommends clear, actionable steps (e.g. adjust filters, change search criteria, check terms).

  • Avoids generic phrases like “Try again” without context.

Action (CTA)
A button or link that helps recover the flow or adjust the search.
Uses explicit infinitive verbs (e.g. Clear filters, Search again, Back to list).

Example

  • Title: No results found for this search

  • Description: Try different terms or remove filters to see more options.

  • CTA: Clear filters






Structure:

Base structure:
No + verb (find, show, list, etc.) + [noun] + [context]
Example: “We couldn’t find products with these filters.”

  • Verb: should express what the system attempted to do and couldn’t (e.g. find, show, return, list).

  • Noun: the type of expected content (e.g. products, results, orders, listings).

  • Context (optional): can be added, such as “with this search,” “based on the applied filters,” or “in this period.”

Description

  • Briefly explains what the user can do to change the state and get results.

  • Recommends clear, actionable steps (e.g. adjust filters, change search criteria, check terms).

  • Avoids generic phrases like “Try again” without context.

Action (CTA)
A button or link that helps recover the flow or adjust the search.
Uses explicit infinitive verbs (e.g. Clear filters, Search again, Back to list).

Example

  • Title: No results found for this search

  • Description: Try different terms or remove filters to see more options.

  • CTA: Clear filters





No-results empty states

No-results empty states appear when a user performs a search or applies filters and the system returns no matches.

Unlike first-use empty states, in this case there was a prior user action, but no content is available as a result of that action.



Takeaways

What i Learned.

01

Guidance over information

Empty states should clearly guide the next action, not just describe the absence of content.

Context creates clarity

Contextual, specific messages help users understand why they’re seeing an empty state and how to move forward.

02

Consistency builds trust

A standardized, accessible empty state system improves usability and confidence across the ecosystem.

03

01

Guidance over information

Empty states should clearly guide the next action, not just describe the absence of content.

Context creates clarity

Contextual, specific messages help users understand why they’re seeing an empty state and how to move forward.

02

Consistency builds trust

A standardized, accessible empty state system improves usability and confidence across the ecosystem.

03

Browse other projects

Ready to work together? Let's talk about freelance projects, collaborations, and full-time roles.

Copy Email

Copied

nat gómezg

Create a free website with Framer, the website builder loved by startups, designers and agencies.