> 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/xamarin/annotation/namespaces.md).

# Library namespaces

Discover how Apryse SDK's Xamarin.Android and Xamarin.iOS libraries empower you to interact with documents using UI components and programmatically. Learn more about the tools and namespaces available

Apryse SDK contains tools libraries for Xamarin.Android and Xamarin.iOS that allow you to interact with the documents with UI components as well as programatically.

{% tabs %}
{% tab title="Android" %}

## Xamarin.Android library namespaces

Tools library in Xamarin.Android is identical to [tools library in Android](/android/annotation/tools.md).

The package to namespace mapping is:

* `com.pdftron.pdf.tools` to `pdftron.PDF.Tools`
* `com.pdftron.pdf.controls` to `pdftron.PDF.Controls`
* `com.pdftron.pdf.utils` to `pdftron.PDF.Tools.Utils`
* `com.pdftron.pdf.widget` to `pdftron.PDF.Widget`
* `com.pdftron.pdf.dialog` to `pdftron.PDF.Dialog`
* `com.pdftron.pdf.model` to `pdftron.PDF.Model`
* `com.pdftron.pdf.config` to `pdftron.PDF.Config`
  {% endtab %}

{% tab title="iOS" %}

## Xamarin.iOS library namespaces

Tools library in Xamarin.iOS is identical to [tools library in iOS](/xamarin/annotation/tools-overview.md#ios).

* All tools such as `PTPanTool`, `PTFreeHandCreate` etc. are in `pdftron.PDF.Tools` namespace.
* All controls such as `PTAnnotationToolbar`, `PTThumbnailSliderViewController` etc. are in `pdftron.pdf.Controls` namespace.
  {% endtab %}
  {% endtabs %}


---

# 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/xamarin/annotation/namespaces.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.