Progress was being made over the past year, just as rovo89 documented in a few of his public updates on the issue until finally both the Xposed Framework itself and the Xposed Installer are ready for release. A project as complex as Xposed requires time to work and then test-time that he didn't often have due to his other obligations. It's simply a hobby, one that he's done for the benefit of the community for 5 years. Xposed is not his full, or even part-time, job. Thus, the best thing we could do was to give rovo89 time to work on his pet project. (This exact thing happened anyways with the abforce implementation, and the resulting mess of various installation methods justified rovo89's hesitation.) Plus, if rovo89 continuously updated his source, he was worried that someone would take the unfinished code to build a semi-functioning Xposed Framework without the universal Xposed Installer to accompany it. It's his brainchild, and he's the best at understanding it and modifying it, so adding more manpower onto the project at such a late stage could simply delay the project further. That's why calls for open sourcing his modifications made to Xposed since the last public release of Xposed have been denied. What we mean by this is that not only should modules work without issue for users, but the way that modules are set up should be consistent among users so developers will know whether or not a Xposed Module is to blame for an app crash. While abforce did a great job in getting his unofficial Xposed working on Android 7.1 Nougat, his implementation went against rovo89's vision for Xposed-that it should be a stable solution providing a reliable and easy to use contract for users and developers alike.

Furthermore, this unofficial implementation was incomplete, leading to inconsistent or buggy behavior with certain Xposed Modules. We saw a glimpse of renewed excitement in the project when developer abforce released an ART submodule for AOSP 7.1.2, but as our very own GermainZ points out you were better off waiting for the official Xposed Framework release as abforce's implementation required the framework to be integrated into custom ROMs.

But many others have moved on to a life without Xposed on their devices. For some, the wait has been tolerable mostly due to the sheer number of additional functionality that the Xposed Framework offers in Android Marshmallow.

Throughout the past year, XDA Senior Recognized Developer rovo89, the lead developer of the Xposed Framework, has provided several updates on the progress of Xposed Framework for Android Nougat.

Xposed bluestacks 2