> 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/customize.md).

# Customize iOS document viewer

Learn how to customize Apryse for your app with document viewer and annotation interaction options. Enhance user experience with tailored controls and appearances. The Apryse iOS SDK streamlines secur

After you have [added Apryse to your project](/ios/get-started/get-started.md), learn how to customize it for your app.

## Customize a document viewer

Apryse includes two `UIViewControllers` ([`PTDocumentController`](https://sdk.apryse.com/api/ios/Classes/PTDocumentController.html) and [`PTTabbedDocumentViewController`](https://sdk.apryse.com/api/ios/Classes/PTTabbedDocumentViewController.html)) for presenting documents. To customize their appearance and function, including hiding and adding buttons, see [**Customizing a Document Controller**](/ios/ui-customization/viewer-configuration.md).

Apryse also includes a low-level `UIView` ([`PTPDFViewCtrl`](https://sdk.apryse.com/api/ios/Classes/PTPDFViewCtrl.html)) to present documents. If you are using it, please see [**Customizing a PTPDFViewCtrl**](/ios/viewer/customize-pdfviewctrl-i.md).

## Customize how users interact with annotations

To change the way users interact with annotations, including restricting which annotations can be created and edited, see [**Customizing Annotation and PDF Interaction**](/ios/annotation/customization.md).

## Customize individual controls

Apryse includes a rich set of controls. They are used by the [document view controllers](/ios/basic-operations/open/doc-view.md), and can also be used independently. To learn more about them, please see each component's guide/API:

* [**User bookmarks**](/ios/bookmarks/user-bookmarks-i.md)
* [**Annotation list**](/ios/annotation/annotation-list-i.md)
* [**Outline**](/ios/bookmarks/outline.md)
* [**List container**](/ios/ui-customization/navigation-lists.md#customization)
* [**Annotation toolbar**](/ios/annotation/annotation-toolbar-i.md#customization)
* [**Thumbnails browser**](/ios/page-manipulation/thumbnails-view-i.md)
* [**Text search**](/ios/search/text.md)
* [**Page settings**](https://sdk.apryse.com/api/ios/Classes/PTSettingsViewController.html)
* [**Page slider**](/ios/ui-customization/thumbnail-slider-i.md#customization)

## Customize annotation appearances

To change the way an annotation appears, see the [**Custom Annotation Appearance**](/ios/annotation/custom-annot-appearance.md) guide.

## Next step

<a href="/ios/guides.md" class="button primary">Guides</a><a href="https://sdk.apryse.com/api/ios/index.html" class="button primary">API docs</a><a href="/ios/get-started/samples.md" class="button primary">Samples</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/customize.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.