I can definitely understand that rationale for breaking up RxAndroid. The issue I've encountered is that when the question is wrap it myself or use a library for an individual feature, like a location wrapper, I almost always just wrap it myself to avoid bringing in another library. But that ends up being a non trivial amount of time wrapping individual components. Of course, that's ultimately on me and I could just adjust my mindset and be more liberal about including libraries. Still, I do see value in a broader library focused on rx-ifying common android flows.