Reading/Reading Lists

Why

 * new readers offline focus
 * apps synced bookmarking and offline features
 * Doc James community wishlist item
 * gather is dead
 * book creator is dying

What

 * multiple features built for specific populations of users (or potential users) across all three platforms (web, Android and iOS)
 * shared backend requirements and development
 * shared product glossary
 * shared design language

How

 * Meetings!
 * Identify and specialize personas from New Readers and previous Design Research work, who have needs relating to downloading, bookmarking, sharing and reading collections of articles
 * Generate a list of {use-cases|features|stories}
 * Create a matrix of each persona X each story
 * Assign priority that persona would give that story
 * Wikif-y the chart!
 * Extract shared requirements for backend needs
 * Begin design process for initial features for initial platform (Android)
 * ...tbd...
 * PHAB TICKETS?

Background

 * Rita's slide deck
 * Link to copied versions of etherpad notes
 * book creator?
 * ...what else??

Not Watchlist

 * Not building on watchlist
 * Watchlist serves a specialized purpose (change notification) for editors
 * Goal is to coordinate across reading audience for lists related to consumption, not a mega solution for all lists of articles
 * Watchlist has a complex technical and usage history and would significantly increase scope of these efforts