> 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/activity-loader.md).

# Activity Loader

<figure><img src="/files/e1JIWwEXrb4qBBZusnfv" alt=""><figcaption></figcaption></figure>

## Overview

A good loading strategy is essential to design a seamless experience for users. The activity loader is one of the components to achieve that goal.

With a simple message that appears on the screen, the activity loader informs users that Mirakl is performing an action under the hood.

The component has a title and a progress bar (mandatory), and one or several subtitles (optional).

## Guidelines

{% hint style="info" %}
Do not overuse the activity loader, as it can create uncertainty.
{% endhint %}

### When to use <a href="#da7c" id="da7c"></a>

Loaders should be used:

* when users are waiting for Mirakl to process a task.

### When not to use <a href="#id-24a3" id="id-24a3"></a>

Loaders should not be used:

* when the task is known to take some time, importing large amounts of data, for example, as it can bring uncertainty.
* when the task is known to take very little time. Avoid the strobe effect.

{% hint style="info" %}
[Learn more about loading patterns](/design/patterns/loading.md)
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://design.mirakl.com/design/components/feedback/activity-loader.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.