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

# Select an integration or framework to get your iOS application started

Enhance your iOS app with Apryse SDK for efficient document processing. Supports Android, iOS, and Windows apps from one codebase. Get started now! The Apryse iOS SDK streamlines secure document proce

Start adding accurate, reliable, and fast document processing capabilities to your iOS application.

<a href="/ios/get-started/integration.md" class="button primary">Swift Package Manager</a><a href="/ios/get-started/integration.md" class="button primary">CocoaPods</a><a href="/ios/get-started/integration.md" class="button primary">Manual integration</a>

## Frameworks

Apryse SDK Supports a number of mobile frameworks for delivering Android, iOS, and Windows apps from a single codebase.

<a href="/xamarin/get-started/get-started.md" class="button primary">Xamarin</a><a href="/ios/get-started/frameworks/react-native/react-native.md" class="button primary">React Native</a><a href="/ios/get-started/frameworks/flutter/flutter.md" class="button primary">Flutter</a>


---

# 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.apryse.com/ios/get-started/get-started.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.