If I'm in a pure compose app (no fragments), what Activity should I be extending and which artifacts...

# compose

[Colton Idle]

If I'm in a pure compose app (no fragments), what Activity should I be extending and which artifacts can I remove from my app?

I could have sworn that Ian said that once I go full compose I can remove appcompat libs entirely? (but my slack search is failing me)

[Halil Ozercan]

Yes you can remove appcompat and extend from ComponentActivity once you depend on androidx.activity:activity-compose

[Colton Idle]

Remove appcompat? Never thought I'd live to see the day. ☠️

[Halil Ozercan]

https://github.com/chrisbanes/tivi/pull/737

[Albert Chang]

https://kotlinlang.slack.com/archives/CJLTWPH7S/p1615496894447000?thread_ts=1615494755.443800&cid=CJLTWPH7S

[Colton Idle]

Nice. I think I'll be safe with ComponentActivity then. I wonder if having to use AndroidView every now and then (for maps and webView) will force me to use appCompat, but I suppose I will find out.

@Halil Ozercan any idea about this PR desc from the link you sent?
"Force exclude AppCompat + MDC dependencies"
How do you force exclude a dep?

[Albert Chang]

You only need AppCompat if you are using AppCompat versions of standard framework views (e.g. AppCompatTextView, AppCompatButton, etc). MapView and WebView are safe.

[yousefa2]

This is where excluding dependencies happen. you can read more about it in gradle docs

[cb]

Please bear in mind that force-excluding dependencies could break libraries, etc. Only do this if you have a good test setup