> 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/android/get-started/customize-a.md).

# Customizing Android document viewer

Learn how to customize a document viewer with Apryse for your app. Customize appearance, functions, controls, and annotation interactions. Apryse offers open-source tools for easy modifications. The A

After you have [added Apryse to your project](/android/get-started/get-started.md) and [added a document viewer](/android/get-started/viewdoc.md), learn how to customize it for your app.

## Customize a document viewer

Apryse includes [DocumentActivity](/android/open-save-document/open.md) and [PdfViewCtrlTabHostFragment2](/android/open-save-document/open.md) for showing documents. To customize their appearance and function, see [**Customizing a document viewer**](/android/viewer/fragment-config.md).

Apryse also includes a low-level `ViewGroup` ([PDFViewCtrl](/android/open-save-document/open/view.md)) to show documents. If you are using it, please see [**Customizing a PDFViewCtrl**](/android/viewer/customize-pdfviewctrl.md).

## Customize individual components

Apryse includes a rich set of controls. They are used by the [DocumentActivity](/android/open-save-document/open.md) and [PdfViewCtrlTabHostFragment2](/android/open-save-document/open.md), and can also be used independently. To learn more about them, please see a detailed [list of each component](/android/ui-customization/components-overview.md).

## Customize how users interact with annotations

Annotation and PDF interaction is implemented within the open-source [tools package](/android/annotation/tools.md). This includes annotation creation & selection, text selection, form filling, link following, etc.

* [Disable (or re-enable) the ability to create or edit annotations](/android/annotation/disable-annot-create-edit.md)
* [Customize annotation handling](/android/annotation/intercept-annotation-handling.md)
* [Customize quick menu](/android/ui-customization/customize-quick-menu.md)
* [Customize annotation style editor](/android/annotation/customize-color-picker.md)
* [Custom annotation creation and handling](/android/ui-customization/custom-tool.md)

## Customize annotation appearances

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

## Customize by modifying the source code

Apryse's tools and [demo package](/android/samples/package-samples/run-sample.md) are completely open source. Any and all changes are possible by editing the source code directly. All source code can be found in `/lib/src`.

You can also integrate with source code directly in your application for easy code modification as described here: [How to integrate the Apryse libraries from source](/android/get-started/faq/run-tools-source.md).

## Next step

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