feat: Use AndroidView overload which re-uses MapView to improve performance in lazy layouts

[philip-segerfast]

This PR uses an AndroidView overload which allows re-using of the underlying view. This improves performance substantially when using GoogleMap in a Lazy layout, like LazyColumn.

This PR also incorporates @bubenheimer's changes from #522.

---

Fixes #285, #492 🦕

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[kikoso]

Hi @philip-segerfast. As far as I read in the documentation, we need to provide a non-null value in the onReset method. This PR does not seem to include it.

[philip-segerfast]

Hi @kikoso, it is enough to make onReset non-null. You can verify by commenting that line out in my PR and you will see that the views are re-created when scrolling.
It still needs some more work though, mainly the GoogleMap state should be reset (for example animations). That's why I made this PR into a draft.
I'll try to make another commit or get back to you regarding this issue during the weekend.

Cheers

[philip-segerfast]

Upon further examination, it appears that executing a reset within onReset may not be necessary since dispositions already clear markers and halt animations, although the underlying GoogleMap's camera position state appears to be untouched.

Some other notes:

• The issue concerning the zoom controls is unrelated to this PR, and appears to stem from a different source. You can reproduce on the main branch by putting a bunch of GoogleMap composables in a LazyColumn.
• Additionally, version 1.6.0-alpha08 of androidx.compose.ui:ui harbors a bug leading to a crash, hence it is advisable to avoid using it.

The PR is quite ready except for the androidx.compose.ui:ui version being in alpha.

[wangela]

We'll wait until this feature moves out of alpha and doesn't cause crashes before we merge.

[philip-segerfast]

Hi, @dkhawk! I made the maps pannable in the demo if you first pan them horizontally so that you still can easily scroll the list. Is this enough for you or would you like the maps to completely intercept the touch events from the LazyColumn like in MapInColumnActivity?

[el-qq]

@dkhawk friendly reminder about this PR (current 6.0.0 :) )

Also, we often use GoogleMap in LazyColumn and have encountered some performance issues (like oom).
Looking forward to these edits in the hope that they will improve performance

[philip-segerfast]

Surely!
I'll also make sure to fix the conflicts soon so that it's ready to be merged again.

[GuillemRoca]

Great job! We will also benefit greatly if this PR gets merged soon so looking forward to it. 👏🏼

[kikoso]

LGTM! This should bring some improvements in terms of performance.

[dkhawk]

@philip-segerfast this is a great change. Thanks so much for your contribution.

[philip-segerfast]

Thanks, you're all welcome!

[googlemaps-bot]

🎉 This issue has been resolved in version 6.1.0 🎉

The release is available on:

• v6.1.0
• GitHub release

Your semantic-release bot 📦🚀

[el-qq]

Local tests show great results!

Thank you very much, @philip-segerfast

[philip-segerfast]

Many thanks to @bubenheimer for reviewing and helping so much too!