# UX/UI Designer

<mark style="color:blue;">**Here are ways Liquid and Grit can help to...**</mark>

## Workshop & Plan User Flows&#x20;

* [x] Design user interfaces that are intuitive and easy to use.
* [x] Create benchmarks for your product development.

Liquid and Grit's [Database tool](/information-by-product/impact-portal/database-tool.md) holds over 34K screenshot and gameplay video libraries of every new release of the top-grossing mobile games, helping UX/UI designers stay up to date when planning their own player experiences.&#x20;

Our [mechanic summaries](/information-by-product/impact-portal/insights-tool.md#mechanic-summaries) also serve as a comprehensive guide to the design components of particular mechanics.

<figure><img src="/files/28fIU07VQCtrTRM34a54" alt=""><figcaption></figcaption></figure>

## Create your Designs

* [x] Create engaging and interactive experiences for players, such as a first-time user experience.
* [x] Develop accessible interfaces.
* [x] Develop effective in-game advertisements and microtransaction systems.

Liquid and Grit's [Deep Dive Toolkits](/information-by-product/product-design-toolkits.md) offer comprehensive analysis and insights into specific, important genre-wide topics, allowing game designers to develop systems that are balanced, engaging, and effective.&#x20;

For example, our [FTUE](https://my.liquidandgrit.com/wiki/ftue-report) deep dive toolkit helps designers create engaging new-user experiences that are effective at teaching players key mechanics and progressions. An analysis of the FTUEs of 26 apps across the casual, core, and casino markets, with retention data sheets, is also included.


---

# 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://product.liquidandgrit.com/information-by-role/ux-ui-designer.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.