A modern programming language that makes developers happier.

kotlinlang

<https://medium.com/androiddevelopers/an-update-on-jetpack-compose-accompanist-libraries-august-2023-ac4cbbf059f1>

Only weird one to kill off in my opinion is WebView. Compose should have this as a foundational component IMO

Accompanist Webview was a bit buggy. I experienced a couple of flashes sometimes. Had to copy and paste and tweak on my own.

Adding support to use a WebView from Compose is a little bit trickier than to implement your own PagerIndicator, so I don’t understand this decision either. It would be nice to have a ready made solution to add a WebView instead of everyone implementing their own solutions for manipulating states to navigate between pages or listen to events.

It is almost the same as using GoogleMaps from Compose

&gt; Compose makes implementing your own versions of these widgets easy.
While it is the best part of compose, I still think the pager indicator, placeholder should not be deprecated, the compose-material/compose-material3 should be the best place for it, it should be a material design standard and we can have a consistent design for the apps, otherwise every app has its own implementation and every app looks so different, what a mess.

i could see pager indicator being part of compose. placeholder... i think was added by a 3rd party contributor to accompanist and they already forked it to keep it maintained (if memory serves correctly)

Will mostly miss systemuicontroller, as no real replacements. Not using it for edge to edge thing mentioned.

WebView being abandoned is astonishing. There's no reason why the community should take over, it _must_ be a first-party solution.

We'll soon have multiple forks each doing their own thing, which creates a lot of fragmentation in terms of features, performance, and bugs.

More importantly I'm concerned about possible security issues when there are multiple unofficial WebView implementations...