> 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
A component that indicates to users that we're processing their data or that a page is loading.
## 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
Loaders should be used:
* when users are waiting for Mirakl to process a task.
### When not to use
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 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/activity-loader.md?ask=&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.
