Is it possible to reopen <https://github.com/google/accompanist/issues/729>? I think this should be ...

# compose

[Felix Schütz]

Is it possible to reopen https://github.com/google/accompanist/issues/729? I think this should be adressed.

[Ian Lake]

Do you have an example of an AnimatedContent transition resting the same transition with something outside of the AnimatedContent even in the non-Navigation world? I don't think that's possible, which makes this infeasible

[Ian Lake]

I think the possibilities open up considerably when shared elements exist, which fits your use case of shared UI (i.e., Scaffold items) that are part of each screen's UI much better

[Felix Schütz]

Sorry for replying so late. I don't think I quite understand what you mean. But I think the idea laid out in the issue should be possible.

[Felix Schütz]

Is there an article or something like that about shared elements?

[Ian Lake]

Shared elements don't exist yet in Compose - they're one of the elements on the roadmap: https://developer.android.com/jetpack/androidx/compose-roadmap

[Ian Lake]

It'll have big implications on a lot of Compose, Navigation particularly, that will heavily influence how'd you'd approach an element that is shared across multiple (but not all) screens. It absolutely won't involve multiple NavHosts though 🙂