Open rendecano opened 6 years ago
IMO Jetpack and the architecture components supersede any purpose that RIBs might serve and do it in a much smarter way. If your app really has any substantial number of screens and "flow" to it, RIBs is a poor framework to build on. I feel like Uber touches on this a little in their articles about RIBs but their use case is pretty special so I would be careful when deciding to implement such an opinionated framework. It's going to be a long, painful journey for my company to get off of this (and that sets aside the total lack of support since it took them 2 years for an update).
Although at this point I doubt anyone reading this is looking to implement this framework, a warning seems prudent.
@tyvsmith @jbarr21 Any insights?
Hey guys, I'm sure most of you have already watched the Google IO 2018 videos particularly the newly introduced Android Jetpack..
They've introduced this Navigation Architecture component: https://developer.android.com/topic/libraries/architecture/navigation/navigation-implementing#kotlin
This sounds like a RIB concept but with one RootActivity but instead of using plain Views objects, Fragments will be used. Any insights on this? (especially Uber developers) :slightly_smiling_face:
Thanks!