The Mapillary web app has gained dangerously too much bloat lately. Sure, it has become a complex app over the last years and most of the data is cached once it has been loaded but asking 50.05 MB just to get things rolling is imho a bit much. Please keep in mind that more and more (if not most) people access the internet on mobile devices over metered connections, not over unlimited stable high speed wired connections. I do not know to what extent Mapillary collects such stats but I am pretty sure that especially Facebook should have some quite exact stats in this regard. Anyway, I can only urge you to optimize for bandwidth by setting yourself an ambitious hard target, like no more than 10 MB (which sounds realistic for the Mapillary web app). Without a specific hard target one is very quickly tempted to say “nah, it is good enough”.
At first glance, the largest size contributor seems to be the latest addition of NeRFs. For example, note that the page loads many quite heavy NeRF PNGs. In this specific case there are a few very easy and simple things you can do:
- load heavy images only when needed
- rigorously use JPEG for natural content images
- crank up the JPEG compression ratio for thumbnails to 0.75, or maybe even 0.5 (usually it is around 0.9)
- if you have to use PNGs then consider using 8 bit palette mode
- set yourself an ambitious hard target and check it on every update
Anyway, you have a lot of smart people on board and they will surely know what to do. 
Just please keep an 
on bandwidth for all those people who pay for every megabyte directly out of their 
pocket.
6 posts - 2 participants