> 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/getting-started/introduction.md).

# How Luciq works

How Luciq works: the SDK captures what happens in your app, the Inbox ranks it, and you act from the dashboard, an AI client, the CLI, or your tools.

Luciq helps you find, fix, and prevent issues in your mobile app. The SDK captures what happens in your app. Luciq groups that signal into issues and opportunities and ranks them. You act on them from the dashboard, your AI client, the CLI, or the tools your team already uses.

{% stepper %}
{% step %}

#### Capture

The Luciq SDK runs in your iOS, Android, React Native, Flutter, or KMP app. It captures crashes, app hangs, performance data (APM), bug reports, session replays, and survey responses. Store integrations bring in your app store reviews.

Start with your platform: [iOS](/ios/setup-luciq-for-ios.md), [Android](/android/set-up-luciq-for-android.md), [React Native](/react-native/setup-luciq-for-react-native.md), [Flutter](/flutter/setup-luciq-for-flutter.md), or [KMP](/kmp/setup-luciq-for-kmp.md).
{% endstep %}

{% step %}

#### Prioritize

The [**Inbox**](/product-guides-and-integrations/product-guides/inbox.md) brings everything that deserves your attention into one place, grouped and ranked:

* [**Issues**](/product-guides-and-integrations/product-guides/inbox/issues-list.md): what is broken. Crashes, performance issues, AI-detected issues, and bugs, ranked by impact.
* [**Opportunities**](/product-guides-and-integrations/product-guides/inbox/opportunities.md) (beta): what to build next. Themes that AI finds across bug reports, app store reviews, and survey responses.

The [App Health Dashboard](/product-guides-and-integrations/product-guides/getting-started-with-luciq/app-health-dashboard.md) gives you the overall picture: frustration-free and crash-free sessions, app insights, and how your latest releases compare.
{% endstep %}

{% step %}

#### Investigate

Open any issue to see its details, occurrences, and session replay. You can also ask your AI client, such as Claude or Cursor, about your production data in plain language through the [Luciq MCP Server](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server.md).
{% endstep %}

{% step %}

#### Act

Forward issues to Jira, Linear, and other [integrations](/product-guides-and-integrations/integrations.md), get notified with [Alerts & Rules](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules.md), and script the same work with the [Luciq CLI](/product-guides-and-integrations/product-guides/luciq-cli.md) or the [Luciq API](/references/api-access.md).
{% endstep %}
{% endstepper %}

## Ways to use Luciq

Every surface works with the same data. Pick the one that fits the task.

| Surface                      | Best for                                                                                                                                                                                                                                      |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dashboard**                | Triage, team views, and configuring rules. See the [Product Guides](/product-guides-and-integrations/product-guides.md).                                                                                                                      |
| **AI client (MCP)**          | Asking questions about your production data in plain language from Claude, Cursor, or your IDE. See the [Luciq MCP Server](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server.md).                                  |
| **CLI**                      | Scripts, CI pipelines, and symbol file uploads. See the [Luciq CLI](/product-guides-and-integrations/product-guides/luciq-cli.md).                                                                                                            |
| **API**                      | Pulling your data into your own scripts, dashboards, data pipelines, and CI checks. See [API Access](/references/api-access.md).                                                                                                              |
| **Agent skills**             | Guided multi-step jobs in your AI client, such as SDK setup, debugging, and alert tuning. See [Agent Skills](/product-guides-and-integrations/product-guides/ai-features/agent-skills.md).                                                    |
| **Integrations and exports** | Connecting Jira, Slack, PagerDuty, and other tools, and exporting app health metrics. See [Export APIs](/product-guides-and-integrations/product-guides/export-apis.md) and [Integrations](/product-guides-and-integrations/integrations.md). |

## Try it

Explore the [demo dashboard](https://demo-dashboard.luciq.ai/applications/ios-demo-app/production/app-health) to see Luciq with sample data. Every SDK API is documented in the [API Reference](https://docs.luciq.ai/references).


---

# 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.luciq.ai/getting-started/introduction.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.
