# UX requirements

### The importance of UX for campaigns

* **Feature visibility:** claimr's flexibility comes with the ability to customize the look and feel of your campaigns extensively. However, without UX design, certain features may not be displayed correctly or prominently, hindering user engagement and campaign success.
* **User-friendly interface:** Intuitive navigation and clear layouts are essential for a positive user experience. Poor UX design can lead to frustration, causing users to abandon your campaign.
* **Optimized engagement:** By incorporating UX best practices, you can guide users through your campaign seamlessly, encouraging them to complete tasks, earn rewards, and ultimately achieve your campaign goals.
* **Brand consistency:** A well-designed campaign reflects positively on your brand and reinforces your message. UX design helps maintain a cohesive and professional look that strengthens your brand identity.

### Key UX considerations for your campaign

Before diving into building your campaign with ⚡️claimr, take the time to plan and design the user experience. Consider the following:

* **User flow:** Map out the steps you want users to take within your campaign, from initial landing to completing tasks and claiming rewards.
* **Layout and visuals:** Ensure your designs are visually appealing, easy to navigate, and align with your brand identity.
* **Mobile responsiveness:** Test your campaign looks and functions flawlessly across different devices, including desktops, tablets, and smartphones.

Explore the essential UX checklists to guarantee your ⚡️claimr campaign looks and performs its best.

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td align="center"><strong>Campaign</strong>   </td><td><a href="/pages/3HwqdbTj6sub61pRLsDJ">/pages/3HwqdbTj6sub61pRLsDJ</a></td><td><a href="/files/BuIVw4kh3b6hO8Puv1bN">/files/BuIVw4kh3b6hO8Puv1bN</a></td></tr><tr><td align="center">G<strong>roup</strong>       </td><td><a href="/pages/uimvHfyF6AjfMwH6gtFq">/pages/uimvHfyF6AjfMwH6gtFq</a></td><td><a href="/files/L5ufHCdVHahGl1HUxnvO">/files/L5ufHCdVHahGl1HUxnvO</a></td></tr><tr><td align="center"><strong>Quest card</strong>      </td><td><a href="/pages/67pYY80p1HXODrFBkH5o">/pages/67pYY80p1HXODrFBkH5o</a></td><td><a href="/files/TNzI2dSeg7038KGygOBo">/files/TNzI2dSeg7038KGygOBo</a></td></tr><tr><td align="center"><strong>Quest</strong></td><td><a href="/pages/QcpLXVuOMYSudr7ZFmLt">/pages/QcpLXVuOMYSudr7ZFmLt</a></td><td><a href="/files/DchnzhmmDGOMx8H6UQU0">/files/DchnzhmmDGOMx8H6UQU0</a></td></tr><tr><td align="center"><strong>Task</strong></td><td><a href="/pages/vhsSHzO75qMxe7M8dcfG">/pages/vhsSHzO75qMxe7M8dcfG</a></td><td><a href="/files/yNsG5r7h9wxwFFuAe8Ns">/files/yNsG5r7h9wxwFFuAe8Ns</a></td></tr><tr><td align="center"><strong>User progress</strong> </td><td><a href="/pages/LXNOaF9bpiGfxT4raQe4">/pages/LXNOaF9bpiGfxT4raQe4</a></td><td><a href="/files/lbGQRt7lxIM5WJsU7l02">/files/lbGQRt7lxIM5WJsU7l02</a></td></tr><tr><td align="center"><strong>Pop-ups</strong></td><td><a href="/pages/Xk1SQ1vSBptosgvgbVXL">/pages/Xk1SQ1vSBptosgvgbVXL</a></td><td><a href="/files/2UfblnRUW3jH3yNzousi">/files/2UfblnRUW3jH3yNzousi</a></td></tr><tr><td align="center"><strong>Inputs</strong></td><td><a href="/pages/SIUDasG3dekaPKXitiuG">/pages/SIUDasG3dekaPKXitiuG</a></td><td><a href="/files/9gd52ILfkJOektzOodcw">/files/9gd52ILfkJOektzOodcw</a></td></tr></tbody></table>


---

# Agent Instructions: 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://claimr-io.gitbook.io/claimr-help-center/ux-requirements.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.