Hi everyone,
I’m currently building a responsive, mobile-friendly web dashboard to help organize our team’s regional Mapillary capture sequences and track missing coverage areas. The map uses custom web layers and pulls a lot of live coordinate data, but I’ve hit a really annoying performance bottleneck specifically when loading it on mobile browsers.
Whenever our field mappers try to scroll or zoom into highly dense areas with thousands of sequence points, the browser completely stutters. The mobile UI thread blocks, causing the entire web viewer to freeze for up to five seconds while it struggles to parse and render the heavy map datasets.
To isolate whether this is a rendering limitation or a background data-handling issue, I’ve been experimenting with different mobile scripting and lightweight thread-execution frameworks. While looking into how other mobile-focused software platforms handle complex, high-frequency scripts in the background without locking up the user interface, I’ve been studying some of the architectural setups over. I actually downloaded a delta executor app build to use as a local testbed so I could analyze how their background threading manages to execute intense automation scripts without causing these kinds of UI lags on Android devices.
My issue is that even when I try to offload the coordinate parsing to a background web worker in the mobile browser, the main DOM thread still drops a massive number of frames when drawing the sequence clusters. Has anyone else managed to optimize high-density interactive map vectors for mobile web viewers? Are there specific tricks for preventing main UI thread blocking during heavy map-data updates that you’d recommend?
I’d really appreciate any insights or advice on how to keep the mobile browser view fluid!