ReVanced Manager is an Android application that applies custom patches to Android APKs using the ReVanced Patcher engine. It provides a user interface for downloading patch bundles, selecting and configuring patches, patching applications (including a background patcher service), signing the resulting APKs, and installing them. The app is built with modern Android technologies: Jetpack Compose for UI, Room for local persistence, Koin for dependency injection, Ktor for networking, and WorkManager for background tasks. It follows an MVVM architecture with a repository pattern and supports root-based installation via Magisk modules. The application manages a complex state of patch selections, downloaded apps, installed apps, and options through a Room database with schema migrations. It includes a downloader plugin system for acquiring APK files from various sources, automatic update checks for the manager itself, patches, and downloaders, and extensive localization support via Crowdin.

This repository is a template for creating ReVanced patches. It provides a Gradle multi-module project structure with a patches module and an extensions module, along with example code for a bytecode patch and an Android extension. The template includes CI/CD workflows for building, testing, and releasing patches using semantic release, as well as issue templates and contribution guidelines. The actual patch logic is not implemented (the example patch contains a TODO), making this a scaffolding repository intended to be forked and customized. The codebase is minimal and well-organized, but lacks any non-trivial logic or reusable components beyond the template structure itself.

The ReVanced Documentation repository serves as a central hub for documentation related to the ReVanced suite of tools (Manager, CLI, and Patcher). It does not contain application code but instead aggregates Markdown documentation and uses Git submodules to link to the respective tool repositories. The repository features a GitHub Actions workflow that automates the process of updating these submodules and committing the changes, ensuring the documentation stays in sync with the source code. Architecturally, the repository is straightforward: it consists of documentation files organized by topic, configuration files for submodules, and a workflow for maintenance. The key entry point is the GitHub Actions workflow triggered by repository_dispatch events, which updates a specified submodule and records the change. This design allows for efficient maintenance of the documentation without manual intervention. While the repository lacks complex application logic, it demonstrates good practices in documentation management and automation. The update workflow is a reusable component that could be adapted to other projects using submodules. The documentation itself is well-organized and accessible, providing users with clear guidance on using and contributing to the ReVanced ecosystem.