During showcase #2 it became really clear that users of near by *only* use list view when the map view doesn't update. Our current filters don't make much sense given the fact that the user has already filtered by location
Version: unspecified
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T40648 Wiki Loves Monuments 2012 (tracking) | |||
| Resolved | None | T39577 Tracking bug for 1.0beta1 release of WLM app | |||
| Declined | None | T40347 Remove nearby list view |
philinje wrote:
My proposed approach to this is to remove the distance filter in the list view, and update the list based on updates in the map view. I think the name and address filters are pretty useful, and the list view will be more efficient when people are in the field.
I disagree with all of this. Sometimes maps in apps are just slow (on say a bad connection) and I might just want to discover things near me. Once I find a close interesting monument I will want to click on the location and use my native google map app which has tile caching to get directions and walk there. I think we should throw this away with caution.
Lets open a bug when this is more actionable. This seems like more of a concern. The map and list views now play nicer with each other (always reflecting the content of each other). We might find users find it better.