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

# UI customization for Android viewer

Discover how to create customizable UI with UI components. Learn about tool hierarchy, custom tools, quick menu, thumbnail slider, and more. Start building your custom views today! The Apryse Android

Apryse SDK is highly configurable and comes with a rich set of APIs which allow developers to customize and manipulate documents in many ways. The following guides will show you the best ways to make your customizations.

## Get started

[UI components](/android/ui-customization/components-overview.md) An introduction to components that can be used to make customizable UI.

[Tool hierarchy](/android/ui-customization/tool-subclasses.md) An introduction to various tools and there interdependencies.

[Set tool mode](/android/ui-customization/set-tool-to-toolmanager.md) To change which tool is selected.

[Custom tools](/android/ui-customization/custom-tool.md) To inherit a tool class to extend and create a custom tool.

[Custom view](/android/ui-customization/custom-relative-layout.md) To add a custom view to a page which is displayed above it.

[Quick menu](/android/ui-customization/quick-menu.md) To use quick menu to conveniently access tools through a drop down style selector.

[Custom quick menu](/android/ui-customization/customize-quick-menu.md) To customize the quick menu by adding or removing tools, changing the display order, or style and theme.

[Thumbnail slider](/android/ui-customization/thumbnail-slider-a.md) To display pages with a small preview enabling quick page to page navigation.

[List container](/android/ui-customization/list-container.md) To display lists across multiple tabs such as annotation list, document outline, and user-defined bookmarks list.


---

# 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/ui-customization/ui-customization.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.
