Re:How We Mapped 1.3M Data Points Using Mapbox
by Brakenshire on Thursday September 13, 2018 @02:11PM
(#17980903)
To be fair, it’s a journalistic exercise not a long running webapp project, if the page loads a second later but development time is significantly reduced, it might be worth the tradeoff. The map works well for me, using mobile on wifi.
Re:How We Mapped 1.3M Data Points Using Mapbox
by reaperducer on Thursday September 13, 2018 @04:02PM
(#17981993)
>it's totally not usable on a mobile network for a ton of people
As noted in the sections:
4. Maps aren’t truly responsive by default (but are annoying on mobile by default)
5. Performance, particularly on mobile, will need all the help it can get
As someone who worked for me used to say: "It's better than good. It's done."
Also, I am loading a ton of data on this page. Interactive maps are nice and I love them but it's totally not usable on a mobile network for a ton of people (ironically given the content of the map). Very curious why they are using React at all, seems like extra page bloat for just one interactive map + chart. Do they test usability on 3G networks? I did not have great load times when off wifi. I think this would be better on a stand-alone page so you can read the article without having your load time impacted by the extra JavaScript.