Slow Composition and Unnecessary Recompositing of Google Maps with Custom Clusters
I've used Google Maps on XML (Views) with Cluster Manger with my customization. I decided to migrate to Compose Maps and Custom Clusters, I'm still using View-based Cluster Manager, but that doesn't affect my issue.
The issue is, that the map loads slowly on Composable Screen, one of the Bottom navigation screens. Every navigation from another screen and coming back to the same map screen reloads the map, but the markers are loaded on time. I've already handled it. The map looks like a mesh grid some of the time, clustering markers take a couple of seconds and lag for second as well, and after that, it works smoothly. Unlike Views, it's not caching the map and the markers well, is there any workaround?
If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@binayshaw7777 Thank you for opening this issue. 🙏 Please check out these other resources that might help you get to a resolution in the meantime:
- Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
- Open a support case - Get 1:1 support in Cloud Console.
- Discord - chat with other developers
- StackOverflow - use the
google-mapstag
This is an automated message, feel free to ignore.
I would also love to get insight about this as well. I request repo owner to give their feedback on this as soon as possible.
Any update on this? I am also having the same problem
Not yet and we moved on with the way it is. Still waiting for an update on this one.
On Sat, 20 Jan 2024, 12:07 am Yasin Tanriverdi, @.***> wrote:
Any update on this? I am also having the same problem
— Reply to this email directly, view it on GitHub https://github.com/googlemaps/android-maps-compose/issues/449#issuecomment-1900960596, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMPHB76MDCFUVMI4O5N6LOTYPK76ZAVCNFSM6AAAAAA6S7BSLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBQHE3DANJZGY . You are receiving this because you commented.Message ID: @.***>
I don't know why it's happening but when I created a release build, the app got a lot smoother and less laggy. I'm not sure about recomposition count as Layout Inspector won't work on Release favour.
Maybe it's just in Debug mode, but still unlike XML based views which is still smoother in both favours, I was expecting Compose to be more or less the same.
I have the same issue. Tapping the tab in the bottom bar causes the map to recompose.