> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/ios/setup-luciq-for-ios/setup-feature-requests/showing-feature-requests-list.md).

# Showing feature requests list

The following method can be used to display the Feature Requests page to your users. Once you display the page, your users can submit new feature requests, add comments, and up-vote other feature requests.

{% tabs %}
{% tab title="Swift" %}
{% code overflow="wrap" %}

```swift
FeatureRequests.show()
```

{% endcode %}
{% endtab %}

{% tab title="Objective-C" %}
{% code overflow="wrap" %}

```objectivec
[LCQFeatureRequests show];
```

{% endcode %}
{% endtab %}
{% endtabs %}

<figure><img src="/files/OjvFDkc1qbD9f0NmErC7" alt=""><figcaption><p><em>This is what the list of in-app feature requests looks like.</em></p></figcaption></figure>

{% hint style="info" %}

### When to Show Feature Requests

In order to get the feature requests page to show reliably, the above API should be linked with an action inside your application, such as the press of a button.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.luciq.ai/ios/setup-luciq-for-ios/setup-feature-requests/showing-feature-requests-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.