Extending the above point, Flutter has a lot of state management "choices" and there was not really a recommended way to manage state until last Google IO where speakers recommended something called

Provider

(https://pub.dev/packages/provider) pattern. Would you guys prefer/recommend any specific state management technique for Compose when it gets released?

This looks roughly equivalent to Compose's Ambient and React's Context. When working with Android Views we've used the same sort of pattern using View tags as the lookup source; the arch components navigation library does this, for example