> 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/learn-more/proguard.md). # ProGuard Learn how to optimize your Android code with ProGuard, a tool that removes unused code and resources in your release build. Discover how Apryse uses ProGuard rules for efficient app development. The A The [ProGuard tool](https://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/introduction.html) is used in Android projects to shrink and optimize your code by removing unused code and resources in your release build. You can learn more about how Proguard is used in Android in the [Android guides](https://developer.android.com/studio/build/shrink-code/). Apryse uses `consumerProguardFiles` and these proguard rules will be used by any application project that consumes the AARs if ProGuard is enabled. Therefore there is no need to include additional ProGuard rules in your application for Apryse dependencies. --- # 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/learn-more/proguard.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.