https://kotlinlang.org logo
#android
Title
# android
a

alexsullivan114

11/29/2018, 9:13 PM
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.
l

louiscad

11/29/2018, 10:59 PM
In many cases, it's a lot less code with #coroutines (usually a single extension method to write once and reuse everywhere), which can interoperate with RxJava2. For example, if you use fused location listener from Play Services, you can use this integration: https://github.com/Kotlin/kotlinx.coroutines/tree/master/integration/kotlinx-coroutines-play-services and if you want to interop with RxJava2 world, you can use this integration: https://github.com/Kotlin/kotlinx.coroutines/blob/master/reactive/kotlinx-coroutines-rx2/README.md What do you think about this?
a

alexsullivan114

11/30/2018, 4:58 PM
Oh that's an interesting idea.
2 Views