Ribs: [Question] How to divide Hierachy Scope

[dangthaison91]

We are trying to adopt RIB by subdividing app into deep hierachy scope like your blog post. But sometimes, our feature has many steps, each step attached based on some conditions and may create another condition. So if we divide scope for each state, we will be leading to create a scope tree with so many levels and some RIBs (often be viewless RIB) act as a router.

We don't have any rules or guideline. We don't know if this can be merged, that must be split into parent-child RIB if we want to decrease level of scope tree but still keep it encapsulate.

This is what we doing. Do you have any ideas or advise. Will really appreciate

[dev4jam]

hey @dangthaison91 I don’t see any major issues in your diagram. What’s the problem? Regarding your diagram I’d remove SignOut (unless it’s a particular screen) and moved back to LoggedOut rib. You also may want to try to scope your app based on screens first (rather then screen states). And later if some RIB became very complex split it into smaller RIBs.