# Activity Loader

<figure><img src="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2FDebmnUpOAvoPPYsygWh5%2FActivity%20Loader%20Hero.png?alt=media&#x26;token=3e1d69ea-5492-4d5b-a070-494273a1a2fb" 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](https://design.mirakl.com/design/patterns/loading)
{% endhint %}