Niek Haarman

I've played around with this as well, and ditched the entire `AcornAppCompatActivity` and implemented the view mechanism manually. I still use ViewControllers, but a modified version that can provide `@Composable`...

Hi @VincentJian, I was unable to reproduce this. Is this still an issue?

This can be done by either - Having a different Activity with its own Navigator handle the Intent in a completely separate task; - Wrapping the 'main' Navigator in another...

Could you give an example of what you mean by an unidirectional/mvi architecture? I'm unfamiliar with it.

You can have a look at the experimental [ConcurrentPairNavigator](https://nhaarman.github.io/acorn/wiki/experimental/concurrentpairnavigator/), which allows a second Scene to be pushed on top of the initial Scene, and have both Scenes active at the...

I'm still not really sure I fully grasp your use case, but here are some thoughts. Acorn's perspective on app navigation is to have navigational state completely decoupled from the...

You could also completely disregard the 'draggable view' from your main navigation flow and let the default Acorn implementations do the main navigation for you. Then inflate a custom layout...

> I don't want to remove the current UI, I want both in the same container Sure, implement a custom `SceneTransition` that leaves the shared view intact.

@NickvanDyke What kind of dialog do you need?

Interesting approach! I'd have to look into this a bit more, for example to properly deal with configuration changes and such.