[well_ackshually]

>You don’t have to cluster anymore. You can just be.

Try to get Google Maps or Apple Maps running on a phone with more than 200 Markers/Annotations, then come back to me with that. Their performance is fucking dreadful. Google Maps released a new renderer that just OOMs if you're rendering a Polyline with 5k segments. Decimate it or face consequences.

As far as I know, MapBox is about the only one that has tolerable performance. Anyone else doing heavy work and using the gmaps SDK is figuring out tricks: overlay rendering (drawing on a canvas above the map, which requires expensive RPC calls to get visible bounds / map projection which makes performance shit if you're not careful and always lags a frame behind), intense caching of marker descriptors, careful management of markers (dropping 200 Markers from scrolling the map + adding 200? Enjoy your main thread work that freezes the map), etc, etc.

First party map tools are absolute dog shit.

[mjmsmith]

My iOS app using MapKit is smooth with ~4k annotations on an iPhone 14. My experience is that it doesn't really start to choke until you get closer to ~10k.

[swiftcoder]

> Try to get Google Maps or Apple Maps running on a phone with more than 200 Markers/Annotations

That the big tech version of this is pretty shit, should come as a surprise to no one. The OP's visualisation runs fine on my phone, presumably Google/Apple could do this too, if they were willing to spend a big of engineering time on it