I'm trying to find a long-term client-side architecture for my Compose/Web application. Currently I'...

# compose-web

[Norbi]

I'm trying to find a long-term client-side architecture for my Compose/Web application.
Currently I'm looking at:
1. https://arkivanov.github.io/Decompose/
2. https://github.com/badoo/RIBs/blob/master/documentation/about/evolution-of-ribs.md
Can someone please explain the main difference between them from an architectural viewpoint?
(I see that RIBs is not multiplatform, so I'm just curious about the differences.)
Besides, does anybody have experience with Decompose in a real application?

[Arkadii Ivanov]

Maybe @spierce7 can share some experience?

[spierce7]

@Norbi I highly recommend using decompose. Decompose is inspired by ribs (if I’m not mistaken). It can be a bit of a shock to the system if you are used to programming on Android / ios.

I ended up giving up dependency injection during the switch to decompose as well. It’s a big change, but I also think that it’s for the better. There is no magic. There is no question about where a dependency comes from, and there is a bit more code. It also takes about 3 days of working with it non-stop to fully understand all the moving pieces, but the end result is that when you write code, if it compiles, it also probably works.

[spierce7]

I highly recommend the investment of time in moving to decompose. My team and I have really enjoyed it.