Reseam applies community-built patches to Android apps, on-device. The patched app installs alongside the original; nothing about your apps leaves the phone.
These docs cover the three pieces and how they fit together:
- Engine: the Rust patching engine and CLI. Runs on your phone inside Reseam Manager, or on your laptop for authoring and CI.
- API: the metadata server at
api.reseam.app. Servespatches.json,manager.json, announcements, and redirects to the upstream release host. - Patches: the official bundle. How it's built, how to add a patch, and how to publish your own.
Pick a topic from the sidebar, or browse the sections below.
Engine
CLI
- Overview What the Reseam CLI is and what it does.
- Install Download or build the reseam binary.
- Patch Apply a signed bundle to an APK.
- Bundle Generate signing keys, pack bundles, and list their contents.
- Publish Write or update a patches.json release index.
- Inspect Print APK metadata.
- Glossary Terms used by the CLI, bundles, and the patch engine.
- Reseam CLI docs Index of the reseam command-line documentation.
API
- Architecture Where the API sits between the official bundle and clients.
- Overview What the Reseam API is and what it does.
- Install Run the API locally or with Docker.
- Configuration Environment variables the API reads at startup.
- Endpoints The HTTP surface the API exposes.
- Announcements Write operational notices clients can surface.
- Glossary Terms used across the API, bundles, and clients.