@jim I was looking at the recommendations here:
https://developer.android.com/jetpack/compose/state#viewmodel-state
So we have a composable called Screen that is basically a MVVM binder, in which case I think it makes sense to pass a A-VM. The content composable on the other hand follows the logic you're talking about. i.e. passed as properties, and not a stateful object like an AVM with flows/LD.
Actually, what I probably should've done in my case is add a preview for the Content composable instead, and then just pass mocked data for my preview.
Thanks for the input!
Thanks