google maps compose is unusable with large amount of markers when using custom clustering when

clusterContent

and/or

clusterItemContent

are not null, meaning when I pass custom composable to it. the more I zoom in, the more it lags until app completely freezes when I zoom in enough. having

clusterContent

and and

clusterItemContent

both set to

null

solves the issue, everything works fine. but I want to customise those.

please file a bug

I will

Interesting. I use google maps with AndroidView (in a project before compose maps was a thing) and I have a large amount of cluster items (over 10 thousand). and everything is pretty darn performant. We did put a few things in place to make it performant though because we just followed the general guidelines for the cluster manager algorithm, etc. Have you looked at the readme for google maps because it had a few items worth taking a look at when you have a lot of items.

View version if performant, works great. I've rewritten the View version in Compose, so it uses the same data sets, icons etc. I did everything that I should've done, I'm pretty sure.

I'll try to lookup what I did in the view version. I did we did two things specifically according to the docs.

I'll file a bug and we'll see. I'll scan through docs first but I think I've done everything right.

Yep. Once I'm out of work I will try to get back to you!

thank you very, very much

Looks like the fix for issue 380 was merged

nice, nice. thank you for the information

Looks like there was good comments from a gmaps team member also after I commented: https://github.com/googlemaps/android-maps-utils/issues/1199

interesting. I’ll keep eye on this one. same as you @Colton Idle I want to get rid of

AndroidView

. whole app is in compose and just map is using

AndroidView

with a lot of ugly code that was a nightmare to write and cleanup

Note that Compose wrapper for maps uses

AndroidView

as well, so technically it is no different

I’ve noticed it while digging through the code to try to solve this problem. technically it’s not different but it makes difference in my code 😄 and how I’m writing/using it.

Yeah. I completely understand that it's still AndroidView underneath. But me doing my own crazy thing to try to get my own MapView to recompose because of different clusters and stuff is such a headache. I'd love to be able to have a nice performant example of how to do this stuff.