> For the complete documentation index, see [llms.txt](https://docs.jigx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jigx.com/examples/readme/preview.md).

# Preview (iOS feature)

{% hint style="danger" %}
**Known Issue:** We recommend using alternatives while we improve the long-press experience.
{% endhint %}

{% columns %}
{% column %}
Add a preview for the following [Components](/examples/readme/components.md):

* [widgets](/examples/readme/widgets.md)
* [list-item](/examples/readme/components/list/list-item.md)
* [event](/examples/readme/components/event.md) The preview is triggered by *long-pressing* the widget or item. The *long-press* action can be used on:

1. Widgets
2. List-items on widget
3. onPress action on list-item or event.
   {% endcolumn %}

{% column %}

<figure><img src="https://1414514342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHcPzbms3kZejTmFd500V%2Fuploads%2FrrWVVFkU7aN7986FcsLP%2Fcc-preview-intro.png?alt=media&amp;token=541a6c18-423a-414f-9a96-53c179a8640f" alt="Preview" width="175"><figcaption><p>Preview</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
**Content preview**

***Applies to:** iOS devices only.*

On **iOS**, you can access a **content preview** by long-pressing a control.\
Long-pressing a control (for example, a web-view or entity-field) opens a lightweight preview window, allowing you to quickly view detailed content without navigating away. Pressing deeper expands the preview, revealing the full context.
{% endhint %}

## Configuration options

<table><thead><tr><th width="130.8828125">Core structure</th><th></th></tr></thead><tbody><tr><td><code>actions</code></td><td><p>These can be added to the preview:</p><ul><li><a href="/examples/readme/actions/action-list.md">action-list</a> </li><li><a href="/examples/readme/actions/execute-entities.md">execute-entities</a> </li><li><a href="https://docs.jigx.com/examples/readme/actions/execute-entity">execute-entity</a> </li><li><a href="/examples/readme/actions/go-to.md">go-to</a> </li><li><a href="/examples/readme/actions/open-url.md">open-url</a> </li><li><a href="/examples/readme/actions/state-actions/reset-state.md">reset-state</a></li><li> <a href="/examples/readme/actions/state-actions/set-state.md">set-state</a></li><li> <a href="/examples/readme/actions/sync-actions/sync-entities.md">sync-entities</a> </li><li><a href="/examples/readme/actions/confirm.md">confirm</a></li></ul></td></tr><tr><td><code>children</code></td><td>Two components available to use in a preview mode:</td></tr><tr><td><code>header</code></td><td>The is can be part of the displayed preview.</td></tr><tr><td><code>isCompact</code></td><td>When set to <code>true</code> the size of the preview will be adjusted to its content.</td></tr></tbody></table>

{% hint style="warning" %}

1. Currently issues could be experienced when displaying the header's `title` and `subtitle` in the preview.
2. Using the `action.go-to` within an action [action-list](/examples/readme/actions/action-list.md) does not trigger the preview popup.
   {% 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://docs.jigx.com/examples/readme/preview.md?ask=<question>&goal=<user_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.