Just updated accompanist and Jetpack versions in m...

# compose-android

[Rihards]

Just updated accompanist and Jetpack versions in my project - how do You use WebView now since it’s deprecated?😄 Google search just shows me examples where it’s not deprecated…

[sindrenm]

There is a post over at https://medium.com/androiddevelopers/an-update-on-jetpack-compose-accompanist-libraries-august-2023-ac4cbbf059f1 talking about this. For WebView, it is recommended to fork their implementation or create your own.

[Stylianos Gakis]

I wonder if now the least time consuming approach + least maintenance in the future is just doing interop with the View WebView instead.
Forking the entire library sounds like a recipe for future maintenance burdens, but I hope I am wrong since I’ve never looked at the internals of it.

[sindrenm]

I always just assumed that it was using the View WebView internally, to be honest. But I've also never looked at the internals.

[Rihards]

Thanks! It seems that I will go back to View WebView solution since the forking doesn’t seem reasonable for me in this case.

[Ben Trengrove [G]]

It is just a wrapper of the view WebView

[sindrenm]

An ~800 LoC wrapper. 😅

[Zach Klippenstein (he/him) [MOD]]

If you’re wrapping it for your specific use cases, you probably don’t need to support as much of the api surface as a generic google-owned wrapper of it would.

[Mark Murphy]

FWIW, https://medium.com/@zmj10170812/elevating-ui-unlocking-the-potential-of-webview-in-jetpack-compose-e0569e77f40c points to https://github.com/KevinnZou/compose-webview as a maintained fork.