Hi I would love to know if the following dependenc...

# compose

[why]

Hi I would love to know if the following dependencies are necessary for a pure Jetpack Compose project :

implementation 'androidx.core:core-ktx:1.3.2'
 implementation 'androidx.appcompat:appcompat:1.2.0'
 implementation 'com.google.android.material:material:1.3.0'
 implementation 'androidx.lifecycle:lifecycle-runtime-ktx:2.3.0'

[Timo Drick]

no they are not necessary.
You just need: "androidx.activityactivity compose1.3.0-alpha03"
And than just the libs from compose you are using.

[why]

Thanks for your input 👍

[Timo Drick]

Than you have to use this code for Activity because the AppCompatActivity is not available:

class MainActivity: ComponentActivity()

[why]

yes I got it thanks again 🙂

[Timo Drick]

It saves apk size when you not using the appcompat stuff. In my app i am able to get an Apk size < 2mb.
In the beginning of compose it was < 1mb but compose and also my app increased in size.

[Louis Pullen-Freilich [G]]

This is most likely because Compose currently has a dependency on appcompat and fragments - in the next release this will be removed so it should be a lot smaller

[Adam Powell]

yeah those transitive dependencies were added for the alphas not because compose actually needs them, but because if you are using them elsewhere in your app, they need to be at least a particular version or newer for compose to not run into problems.

[Adam Powell]

last I checked when these are stripped out, small apps post-r8 shrinking still have classes.dex files < 1MB. There's a lot in appcompat that r8 can't prove it can remove safely.

[Colton Idle]

OOh. So in a pure compose app we can remove appcompat dependency completely?

[Adam Powell]

@cb did a blog post on it: https://medium.com/androiddevelopers/jetpack-compose-before-and-after-8b43ba0b7d4f