How are you guys

[melbaldove]

I know Uber people are busy. But are there any plans to make further improvements to RIBs? Its getting pretty inactive nowadays

[sbarow]

Hey @MelbyBaldove the repo might seem inactive but its because there aren't much updates needed other than ensuring RIBs compile with the latest SDK's.

What kind of improvements would you like to see?

[dangthaison91]

How about Plugin @sbarow ?

[sbarow]

How about Plugin @sbarow ?

Plugins aren't tied directly to RIBs so I am not sure it makes sense include them as an improvement in this repo.

[xzeror]

@sbarow so what about https://github.com/uber/RIBs/issues/312?

[sbarow]

@sbarow so what about #312?

Yeah this is something we can do.

[chenjunpu]

@sbarow When to migrating the TicTacToe RIBs sample to use Needle？

[melbaldove]

@sbarow #291 #304 and #308 I guess

[ermik]

@chenjunpu this is probably a question for @neakor because he was planning to think about it. Certainly, with some guidance from folks @uber, community can do these things as well.

[neakor]

For the original question:

Internally we haven't made any major changes since inception back in 2016. We've mostly been busy working on https://github.com/uber/needle and https://github.com/uber/motif

We are just kicking off an effort to simplify RIBs and reduce boilerplate code now. We'll likely have something new in Q3.

@chenjunpu I don't believe we will migrate the TicTacToe example in this RIBs repo. RIBs is an architectural pattern and Needle is a DI system. The two can be used independently. In fact they have been as you can see that Uber started using RIBs with a different DI system. We just recently migrated all of our codebase to Needle.

[keithcml]

Hi team, Any plan to have more integration example about using RIBs? Like how to work well with new Android Jetpack Navigation Components?

Thanks

[neakor]

@Leland-Takamine can help answer the Android specific question.

[dron247]

@keithcml I do not really think that jetpack navigation and RIBs are compatible matters, you can, for example have a RIB root in one of those fragments and provide necessities to every root with dagger, but I'm afraid you can not really mix them, because RIBs is one of the ways of NOT USING fragments at all.

[dangthaison91]

@neakor Could you please share progress on this?

We are just kicking off an effort to simplify RIBs and reduce boilerplate code now. We'll likely have something new in Q3.

[GrahamBorland]

One year on, any more status updates?

Any plans to incorporate changes from Badoo's fork?

[tyvsmith]

Hey folks, When this repo was created, it was primarily a snapshot to inform the community conversation. However, We recently started a reinvestment project into RIbs on Android to modernize it. We have migrated to using this repo primarily as the source of truth as opposed to an internal copy. We have many projects planned like conversion to Kotlin, jetpack Compose Support, Coroutines support, and long term evaluation of jetpack library integrations, kmp, and additional Rib based libraries. For iOS, we're still figuring out staffing to bring more investment, but it's on the radar.

We expect quite an uptick in investment and support in this repo, including evaluation of forks, and our roadmap will be open.

Thanks!

[ermik]

@tyvsmith we haven't taken it as far as it needed to go, but some ideas for KMP are here: https://github.com/makegoodstuff/RIBs/commits/tmp-multiplatform-structure