IssueTracker

Using Compose within Fragments require setting a different ViewCompositionStrategy (DisposeOnViewTreeLifecycleDestroyed) so that the composition follows the fragment's view lifecycle. While we do document this behavior in https://developer.android.com/jetpack/compose/interop/interop-apis#composition-strategy it is still a common 'gotcha' that developers frequently run into as per feedback we've received from partners (b/229427938).

To prevent developers from making this mistake, we can improve the DevEx by either:

• providing a lint warning when using ComposeView in a fragment (preferred - works for existing implementations)
• create a subclass ComposeFragment (less preferred - requires awareness of this new component, also can be confused with fragment-in-compose use case)