v2 wireframes

[alanjosephwilliams]

These wireframes:

• Default to the map view!
• Reckon with the incorporation of multiple, diverse datasets.
• Allude to but don't flesh out too much detail around future content associated with locations (taken from Yelp, Factual, et al).
• Allude to "hot food" locations, which I know we are not settled on including yet. This could also be "HSA offices" or "Food Pantries". We can also reduce to two options for the time being.

I'd love feedback before I start building. @fureigh @mollymcleod @lippytak

1. Default Screen (after allowing the app to use your location)

1. Map marker tapped/ store selected

Note there are no longer any infowindows--the map marker changes colors, and content is fixed to the top. With this one tap, the user can call the location. One day, we should allow tapping the address to open their default map app and route them to that location (perhaps).

1. Detail view for the selected store

4 . List view for active dataset

[lippytak]

This looks really great to me. Here are a few questions/thoughts to consider:

• I'm a little confused what 'clear' does. If it just brings back the initial header seems pretty low value because it wouldn't save real estate anyway.
• The right arrow (for details) vs. back button (for remove details) seem a bit inconsistent. Maybe a 'i' for more info and a left arrow for back? I think those are more common for the mobile sites I use but could be wrong, and maybe being more explicit for our user makes sense.
• Unclear to me how to toggle between map/list view.

Also keep address search in the back of your mind: https://github.com/fureigh/ebt-near-me/issues/32