[toss1]

Yes definitely seems like the wrong lesson but right changes

Just a large list of reports only MAY give me a faster access to the info I want. If the trail I'd like to go to today is not at the top of the list / on the first page, it would likely take objectively longer to check the conditions for the place that I want to see.

What would be best would be a map that not only provides locations of the listed trails, but also a coarse indicator of conditions — just Excellent/OK/Marginal/Closed, and maybe a number of trails/km/miles open. Click to that, and NOW the list of reports by recency will give me the detail I wanted. This would be all WAY faster (presuming a properly responsive app) than scrolling through multiple reports that aren't relevant.

So, it seems we have different ideas about what counts as "complexity". I see a map as simpler than a list with the order that I don't want; the author apparently sees it as more complex (perhaps because coding the map and the selected lists is more complex than just the one big list?).

In any case, it is an improvement.