IssueTracker

Component used: Activity Compose

Version used: 1.8.0

For apps that are built fully using Compose, there's a significant amount of Android specific knowledge needed to actually get that UI to be displayed:

1. You have to know what an activity is in the first place.
2. You have to know what activity superclass you should be using (e.g., ComponentActivity) since you can't use android.app.Activity for Compose UI
3. You have to understand what boilerplate you need in your activity (overriding onCreate(), calling setContent, etc.)
4. You have to make sure to add that activity to your manifest and understand the correct intent filters necessary.

It would be nice if there was a way to generate all of that for you. It could be as simple as adding another annotation to a specific @Composable method.

This would be dependent on being able to generate the correct activity class and APIs to add that activity class to the AndroidManifest.xml for you.