Feb 27 Planning Feature Decisions & User Stories

Users --

• Senior citizens (SC)
• Young "tech savvy" (YTS)
• Potential/future activists & organizers (A&O)

Features --

• Embeddable (websites, emails(?)) (A&O)
• Printable (SC)
• Vision accessibility (SC)
• Screen reader (SC)
• List only (SC)
  • Because zooming and map text resizing can be frustrating
• Available offline (SC)
• Filterable (YTS)
• Shareable (FB, Twitter) (YTS)
  • "I'm supporting this community event"
• Tell a story (health affects by county, general environmental affects) (SC) (YTS)
• (Stretch) Local discounts with "take back" stickers (SC)
• RSVP ability (and RSVP density mapping) (SC)
  • With (optional) texting reminders
  • Promotes idea of community event as opposed to just mapping function
  • Add to calendar option

User Stories --

• I want to see a map
• I want to see locations
• When I click on a location, its location pops up
• I can get/send data to API
• I can see how many people (generally) rsvp'd to a location
  • heat map?
• I can see how affected my community is
  • Different shades (toggled layer)
• I can specify what type of location to visit
  • e.g. Filter out police stations
• I want to see locations near me
  • Filter by travel time
  • Zoom to locations
• I can add an event to my calendar corresponding to my RSVP
• I can print the map
• As a user with bad eyesight, I can read the map
  • Text size
  • Metadata
  • Text-only (list of locations)
• I can share map and API
  • FB and Twitter
• I can embed the map
  • Websites
  • Email (?)

Next Steps --

• How can we project manage all of this? (Meka & Olivia)
• Documentation + Run Script (Chandra & Alex)
• Mock-ups + wireframes (Ritika & Rapi)
• Delegate lead responsibilities