After months of development and some unexpected delays, we’re releasing Androidacy Module Manager Beta 3. If you use root frameworks like Magisk, KerneSU, or APatch, this is the app that helps you discover, install, and manage modules. This version isn’t an update. It’s a complete rebuild that makes it easier than ever to install Magisk modules and manage your rooted Android device.
The Case for Rebuilding Androidacy Module Manager From the Ground Up
The 2.x version served its purpose, but we hit a wall. The architecture relied heavily on webviews, which created performance bottlenecks and security concerns we couldn’t patch away. Technical debt accumulated to the point where adding new features meant working around old problems instead of solving them.
We spent months trying to refactor the existing code before accepting reality: some foundations can’t be fixed, only replaced. The delays frustrated us too, but rebuilding properly beats shipping something half-baked. The new codebase uses modern Kotlin and Jetpack Compose, which gives us better security, performance, and a foundation we can actually build on.
Given the scope of changes and improvements, we’re planning to phase out the 2.x versions. Unless something goes seriously wrong with the beta, we won’t be releasing further updates to the old version. API access for 2.x will be turned off in a couple of months, so we recommend migrating to Beta 3 sooner rather than later.
User Experience Improvements
The webviews are gone. Everything runs natively now, which means the app feels faster and more responsive. We’ve adopted a Material 3 Expressive edge-to-edge design, making the interface cleaner, more intuitive, and more personal without sacrificing functionality.
Performance improvements go beyond the UI. The network stack now uses QUIC and HTTP3, which translates to faster downloads and better handling of unstable connections. The installer now runs as a service, making it more resilient and performant during module installation. Compared to the old webview implementation, you’ll see fewer ads overall. If you download from the Androidacy repository specifically, captchas show up less often and wait times are shorter or eliminated.
The Androidacy Module Manager now supports additional compression formats for modules, meaning previously problematic modules like Shamiko will install without issues. This expands compatibility across the entire ecosystem of available modules. Changelogs are now natively supported, so you can review what changed in each module update before installing.
Search and sorting got smarter. The app now understands context better, so finding specific modules takes less effort when you want to install Magisk modules. We’ve also added a recommendations system that suggests modules based on your setup and usage patterns. If a recommendation misses the mark (or is something you like!), long-press it to give it a thumbs up or thumbs down. Your feedback improves future suggestions.
Module updates now trigger notifications when new versions appear. Premium users will get push notifications for this soon. The installer can optionally display error and debug logs during installation, making troubleshooting easier. These logs stick around for about seven days and you can review them in-app whenever you need to dig into what went wrong.
For users who browse modules in different languages, the app can now translate module content that isn’t in your language through our API. Third-party content gets cached by our CDN, which reduces load on repository servers and protects your privacy by limiting direct connections.
Developer Features and APIs
We built several APIs that let modules interact with users, fetch files, and trigger app installations. These open up possibilities that weren’t feasible before.
Configuration got a major upgrade through two systems. The config.json format comes in simple and advanced flavors. Simple mode looks like {"setting_name":"default_value"} and takes minutes to implement. Advanced mode gives you granular control over how settings work. Either way, the app generates a native settings UI automatically, and persists the config for your module.
The module.prop file now supports several new options. You can specify an app package name or path to a text file for the config field. We don’t validate text files, so you have complete control over the content. If you point to an app, it should eventually support the com.androidacy.modulemanager.MODULE_CONFIG intent action. Right now that’s just a warning, not a requirement, but plan accordingly.
Modules can now include an iconUrl in the module.prop, allowing you to customize the icon shown in the UI for your module instead of using the default placeholder.
Adding repository support is simpler now thanks to new APIs. The app handles most module repositories without custom workarounds, and developers can provide a simple link to open the app to add a source.
For detailed explanations of these features and implementation examples, check the Developer Guides chip in the Androidacy Module Manager app. We’ve included comprehensive documentation to help you take full advantage of the new APIs. We’ll those to our website after the APIs are fully stable.
Premium Benefits and Platform Considerations
Premium subscribers get smarter recommendations, zero ads, and no download limits. Subscriptions work across your entire account but cost more through the Play Store version to cover Google’s fees.
Speaking of the Play Store: that version may limit visibility of certain modules and restrict some features. Google’s policies forced these changes. The website version has no such restrictions but will be released about one to two weeks after the Google Play version during the open beta period. The website version currently lacks an auto-update mechanism.
We’re taking a pragmatic approach with v3 regarding source availability. Rather than maintaining a complex monolithic codebase that saw limited community contributions over the years, we’ll release focused libraries and components as we refine the code. This approach lets us sustain long-term development while contributing tools that benefit the broader Android development community.
Availability and Beta Status
We’re calling this beta because the APIs might evolve based on developer feedback and minor bugs could surface. That said, we consider it stable enough for daily use. We’ve been running it ourselves for weeks without issues.
Download the Androidacy Module Manager from the Google Play Store now. The website version will follow in one to two weeks. Let us know what breaks, what works, and what you’d change. We built this for you, so your feedback shapes where it goes next.
Thanks for sticking with us through the delays. Module management should be straightforward, and we think this version finally delivers on that promise.
