Best practice is probably to avoid referencing AAC...

# compose

[jim]

Best practice is probably to avoid referencing AAC ViewModels in your composable functions.  They are not platform-agnostic and almost always imply a strong coupling between your composable function and the rest of your application.

Instead, create an interface and only refer to the interface from your composable (this allows you to easily create an alternative implementation of the widget data that does not use AAC ViewModels), or read from the view model up at the top of your application and split it off into only the non-ViewModel data that your individual composables need.

When your composable does not behave well in Preview, that is almost always an indication your composable is not sufficiently isolated from the rest of the platform/application code.