> 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/print.md). # Print - [Printing Library for Android](https://docs.apryse.com/android/print/print.md): Discover how to print in Python using the Print To show a system print dialog. Learn how to get started with printing in Python effortlessly. The Apryse Android SDK streamlines secure document process - [Printing a PDF in Android](https://docs.apryse.com/android/print/printing.md): Discover how to easily implement printing functionality in your app using Apryse SDK. Learn how Print.startPrintJob can simplify the process for you. The Apryse Android SDK streamlines secure document - [Code samples for printing PDFs in Android](https://docs.apryse.com/android/print/samples.md): Learn how to combine multiple pages in PDF format with PDF imposition using PDFNet. Explore the Android showcase sample app for a demo on page arrangement and printing features. The Apryse Android SDK - [APIs for PDF printing in Android](https://docs.apryse.com/android/print/apis.md): Discover utility classes for printing PDF documents in Android using com.pdftron.pdf.Print. Enhance your app's functionality with Java/Kotlin integration. The Apryse Android SDK streamlines secure doc --- # 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/print.md?ask=&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.