# Recommended UX

Recommendations for a typical banking application to optimize cost and efficiency:

1. Use a [List request](/basic-concepts/list-request.md) (type `restrictive`)  to fill the initial list of transactions using the cleaned up name and logo, and optionally also include categorisation and category icon in this view.
2. When a user wants more information about a transaction then they can press/click on it. At this point a individual call (see [Quick Start](/implementation-guides/quick-start.md)) of type `extended` is made and the user will navigate to the Detail View.

See also [Restrictive vs Extended](/basic-concepts/restrictive-vs-extended.md).

See also [Additional UX Considerations](/implementation-guides/additional-ux-considerations.md).

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


---

# 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://devs.snowdropsolutions.co.uk/implementation-guides/recommended-ux.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.