# Aliucord Manager, a Compose installer that replaces the old modding bootstrapper > Aliucord Manager is the Kotlin and Jetpack Compose application that installs Aliucord, the Discord client modding framework, replacing a legacy installer that is now deprecated and broken. It is aimed at people who want to install mods on their own Android device, and its README is candid about the storage, network and permission steps the install requires. **Aliucord/Manager** — The new way to install Aliucord – in a user-friendly way - Repository: https://github.com/Aliucord/Manager - Stars: 720 · Forks: 77 - Language: Kotlin - License: OSL-3.0 - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/aliucord-manager ## An installer for one modding framework, not a general app store Aliucord Manager describes itself as the new method to install Aliucord, in a user-friendly way, and the project description says the same: the new way to install Aliucord, in a user-friendly way. That is the whole scope. Aliucord itself is the Discord client modding framework, and the manager is the front end for putting it on a device. The README's final installation step is to install plugins by following the separate plugin installation instructions, which live in the aliucord repository rather than here. So the manager handles one thing well, the framework install, and everything after that happens through the installed app. The implementation is Kotlin with Jetpack Compose, and the repository layout matches a standard single-module Android project: an app/ directory, build.gradle.kts, settings.gradle.kts, gradle.properties, the Gradle wrapper with gradlew and gradlew.bat, and a gradle/ directory. There is also an INFO.md, a TODO.md and a crowdin.yml at the root. The client itself is Discord, so this is a client modification tool, and the audience is users who want to add plugins to their own Discord installation on their own device. Nothing in the documentation suggests a use beyond that. ## Android 7 to 16 QPR1, across four architectures The prerequisites section is specific about device support. Supported Android versions run from Android 7 at SDK 24 up to Android 16 QPR1 at SDK 36, and the supported architectures are arm64, armeabi-v7, x86_64 and x86. Listing all four architectures is the kind of detail that matters more than it looks. A manager that only shipped arm64 binaries would fail on the many emulators and older low-end devices that run 32-bit ARM or x86, and the armeabi-v7 and x86 entries in this list are what make the tool usable on those. There is also a migration path from the previous generation. The README says that if you have already installed Aliucord via the old installer app, you can uninstall the legacy installer, and it is explicit about why: the legacy installer is deprecated and does not work anymore. So the manager is not an optional alternative for existing users, it is the only working path, which reframes the decision from a choice between two installers to a single option. The Discord sign-in step is part of the install flow, not an optional extra, which is a reasonable hint that Aliucord's plugins interact with an authenticated account. ## Ten install steps, including the failure modes listed in advance The installation section is a numbered sequence that runs from downloading the latest release APK through to installing plugins. You download the APK from the GitHub releases page, open and install it, granting the unknown sources permission in system settings if your browser has not enabled it, then open the manager and grant the permission requests the app asks for. Then the actual work happens. You click New Install, or Update if Aliucord is already present, and you can change how the Aliucord app icon will look once it is installed. You click Install and wait, with an explicit instruction not to exit the app while it is running. Afterwards you click Launch or start the installed app directly, grant its permission requests, sign in to Discord, and move on to plugin installation. The most useful part of the section is the failure list, which names the causes before you hit them: a poor internet connection, internet censorship or blocks, in which case the README suggests a VPN or a different DNS server, and insufficient free storage, with at least 500MB recommended. If you are stuck, the README points at the support channel on the project's Discord. The unknown sources step and the wait-without-exiting instruction are the two places where a hurried user is most likely to break the install, and the README calls out both. ## Building the APK yourself with the Gradle wrapper The build section is short and complete. You need Git and JDK 21 or newer, then you clone the repository and build it. The clone is a single command: ```bash git clone https://github.com/Aliucord/Manager && cd Manager ``` On Linux and macOS the build is: ```bash chmod +x gradlew && ./gradlew :app:packageStaging --stacktrace ``` And on Windows the wrapper runs as a batch script: ```bash .\gradlew.bat :app:packageStaging --stacktrace ``` The task name is :app:packageStaging, and the built APK lands at ./app/build/outputs/apk/staging/app-staging.apk. Two observations. The build produces a staging variant rather than a release one, which is consistent with a project that distributes release APKs through GitHub releases while keeping the source build simple. And the --stacktrace flag is not decoration: this is a Gradle Android build on a specific JDK, and when it fails the stack trace is the difference between a fixable error and a guess. The repository also publishes a nightly build link for the app in the build status badge, which is a separate distribution channel from the tagged releases. ## Crowdin translations, a licence to read first, and a moving target Localisation is handled through Crowdin, with the README asking anyone fluent in the listed languages to contribute translations, and the crowdin.yml file at the root holds the configuration. That is the right shape for an app with a broad user base and a maintainer team that is not going to translate everything by hand. The licence is OSL-3.0, the Open Software License, which is a strong copyleft licence with a patent grant. The practical consequence for a consumer application is different from a library: the manager is distributed as an app, and the OSL-3.0 obligations attach to modified versions of the software being distributed. Anyone who plans to fork the manager and ship a modified APK needs to read the licence carefully, because the obligations bite on the modified work rather than on private use. The release record shows steady work with a gap: v1.2.0 on 2026-01-31, v1.2.1 on 2026-02-03 and v1.3.0 on 2026-05-15, with the last push to the main branch on 2026-09-19. So the tree has seen work after the last tagged release, and the version numbering is a simple semver line. What you should not expect is a long support window per version. This is a client modding installer for a platform that changes underneath it, so a version that works today may be the version you need after the next Android or Discord update. ## Conclusion Adopt Aliucord Manager if you want to install Aliucord and its plugins on an Android device and the legacy installer has stopped working on your Android version, since the manager covers Android 7 through Android 16 QPR1 across four architectures. Do not adopt it as a general purpose app installer or as a distribution mechanism for your own plugins, since it exists to install one specific modding framework and points plugin authors at a separate instructions page. Before you install, check the 500MB free storage recommendation and the unknown sources permission, read the troubleshooting list of failure causes in the README, and note the licensing position, where the repository is licensed under OSL-3.0 and the latest release is v1.3.0 from 2026-05-15 with the last push on 2026-09-19. ## FAQ ### What are the system requirements for Aliucord Manager? The README lists supported Android versions from Android 7 at SDK 24 up to Android 16 QPR1 at SDK 36, and the supported architectures are arm64, armeabi-v7, x86_64 and x86. The install also needs permission to install from unknown sources and at least 500MB of free storage. ### Can I still use the old Aliucord installer app? No. The README states that the legacy installer is deprecated and does not work anymore, and that if you already installed Aliucord with it you can uninstall it. Aliucord Manager is the supported path. ### How do I build Aliucord Manager from source? Install Git and JDK 21 or newer, clone the repository, then run chmod +x gradlew && ./gradlew :app:packageStaging --stacktrace on Linux or macOS, or .\gradlew.bat :app:packageStaging --stacktrace on Windows. The APK is written to ./app/build/outputs/apk/staging/app-staging.apk. ### What should I do if the Aliucord Manager install fails? The README lists the likely causes: a poor internet connection, internet censorship or blocks where a VPN or a different DNS server helps, and insufficient free storage with at least 500MB recommended. If you are still stuck, the project asks for help in the support channel of its Discord. ### How is Aliucord Manager translated and licensed? Translations are crowd-sourced through Crowdin, with the project configuration in crowdin.yml at the repository root. The licence is OSL-3.0, so anyone shipping a modified build should read the LICENSE file before doing so. ## Sources - [Aliucord/Manager on GitHub](https://github.com/Aliucord/Manager) - [Issues](https://github.com/Aliucord/Manager/issues) - [License: OSL-3.0](https://github.com/Aliucord/Manager/blob/main/LICENSE) - [README](https://github.com/Aliucord/Manager/blob/main/README.md) - [Releases](https://github.com/Aliucord/Manager/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/aliucord-manager