> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/components/feedback/snackbar.md).

# Snackbar

A discreet but efficient way to convey feedback on the outcome of an action.

## Overview <a href="#id-101ca4" id="id-101ca4"></a>

<figure><img src="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2FBY1NmNl6qsD8nPCzSupS%2FSnackbar%20Hero.png?alt=media&amp;token=44ecca59-0915-4e5f-9152-f3d92abb46bb" alt=""><figcaption></figcaption></figure>

Snackbars inform users when a backend action is done.\
They pop up briefly at the bottom of the screen, explaining the outcome without being too intrusive.

### When to use ?

Use snackbars to quickly share results, whether good or bad. \
*For example: 'Item added' or 'Item deleted'*

Snackbar should not be used to display critical information; use [alerts](/design/components/feedback/alerts.md) instead.\
*For example: 'You cannot perform this action because your profile has not been verified'*

## Design guidelines

Snackbars can only have one [button](/design/components/actions/buttons.md).

{% hint style="info" %}
**Prototyping a Snackbar on Figma for designers**<br>

* Trigger : onClick **OR** onDelay - 50ms
* Animation type : Custom Spring
* Duration: 300ms
  {% endhint %}

## Content <a href="#id-0969f1" id="id-0969f1"></a>

<figure><img src="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2FVfwEcQ2L5uVm3vyzO7ng%2FSnackbar%20Example%201.png?alt=media&amp;token=2b67fba7-6df6-4c3a-9d43-7248008b8fa3" alt="" width="563"><figcaption></figcaption></figure>

**Keep it short**

Snackbars are visible for 5 seconds, users won’t have time to read a long sentence. If you need more than one sentence consider using another component.

**Use simple words**

Use everyday language and generic terms as much as possible, it’ll be easier to reuse.

**Capitalize the first word, no period**

{% hint style="info" %}
**Template**: Object + verb+ED
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://design.mirakl.com/design/components/feedback/snackbar.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.