Andrey Kovalev

@amal I think it's already in place https://github.com/bumble-tech/appyx/pull/32

@saket `NavModel` at any given level of the tree coordinates [navigation of the subtree](https://bumble-tech.github.io/appyx/apps/structure/#composable-navigation). It allows us to keep our codebase organised in a tree structure, and use to use...

Hi @saket you can already retain your presenter per Node level. Please check `com.bumble.appyx.sandbox.client.mvicoreexample.MviCoreExampleBuilder` where we retain feature. To make it work per node level you simply need to provide...

Hi @LittleTasteOfHeaven, the ViewModel support is not integrated into the library yet, however, we have support for retaining objects. Similar functionality can be achieved using the `RetainedInstance` API. Please check...

Hi @dandc87 thanks for reporting it! We'll look into it

@ganfra sorry for the late response. Atm there's no mechanism implemented to guarantee the lifecycle order. Children are moved to`DESTROYED` state when the parent's lifecycle scope is cancelled. To support...

@zsoltk can be closed?

> IMHO it should be implemented in the same way as in `Fragment` – each `Node` should be `ViewModelStoreOwner` with own `ViewModelStore`. Then throw everything into single `FragmentManagerViewModel`-like `ViewModel` that...

> The standard lifecycle viewModel functions for compose delegate to the composition local LocalViewModelStoreOwner. Wouldn't it just be a matter of coming up with a proper implementation of this which...

Hi @ganfra `ParentNode` starts managing children when `onBuilt()` is called. Can you possibly defer calling it to the point when you have dependencies ready?