Reading/Quarterly Planning/Q3

Brainstorming Guidelines

 * Stay aligned with Q3 goals mentioned in with the Roadmap
 * Nothing (within the constraints of the Roadmap goals!) is too off the wall or crazy during brainstorming!
 * Earlier brainstormings are found here

Have Parsing needs?
Enter them in T119088 by December 4.

Web

 * 1) Speed/Architecture mobile web beta (including W0 compatibility)
 * 2) Read More to stable
 * 3) Gather/Collections support for Android
 * 4) Language button / fixed footer menu mobile web, Simplified Vector desktop sidebar (w/ A/B test for Reading strategy)
 * 5) QuickSurveys automation (no constant deployments)
 * 6) QuickSurveys UI - possibly leveraging CentralNotice infrastructure
 * 7) QuickSurveys event trigger mechanism (likely dependency: Fundraising Tech)
 * 8) QuickSurveys Wikipedia Zero survey tagging
 * 9) Revisit EL schemas
 * 10) OpenGraph
 * 11) Hovercards to stable
 * 12) iOS universal links support
 * 13) Image performance in MobileFrontend
 * 14) Special:UserProfile transition
 * 15) Researchers surveys

iOS
Origianl Brainstorm List
 * 1) Maps based nearby interface
 * 2) IOS Notifications
 * 3) Finish deployment of deep "Universal" links
 * 4) iPad design and tablet specific user stories
 * 5) CoreData migration (update app data layer for stability and speed)
 * 6) Feed, feed, feed (potential dependency on apps content service if desiring to centralize logic)
 * 7) Improve read more. A/B test variations of image size + text extract, amount of related articles, and location of read more within the page.
 * 8) Adopt content services

iOS Goals (not all committed)
It should be noted that the iOS team is in the midst of finalizing and pushing to Beta a major revision of the app. All the items below are subject to being dropped if the user feedback from that roll-out requires significant iterations or investment prior to moving on to any new goals. I'm not sure this should be a stated goal, since its basically "finish the goal from last quarter if we haven't by Jan 1", but can add it if it is helpful for understanding the relative priorities of the team.

Android
Outcome: #4 is likely part of Gather epic, everything else added to the holding tank of awesome ideas!)
 * 1) Gather (likely dependency on Reading Web for API enhancements)
 * 2) Wikipedia Zero exit interstitial (potential dependency on Reading Web, although is simple extension change potentially doable by Android engineer)
 * 3) Better custom APK channel persistence (i.e., don't lose channel if custom APK preload gets upgraded before first launch)
 * 4) Do more with notifications?
 * 5) Picture of the day?
 * 6) Tablet layout
 * 7) Continue work on Wikipedia Lite
 * 8) Improve discovery of saving a page and accessing list of saved pages
 * 9) Surface more main page content
 * 10) Any of which would also work nicely on Google Now if they actually open up the API
 * 11) Improve share a fact and show which text has been shared

Infrastructure
Infrastructure Goals (not all committed)
 * 1) ..and even more ideas here

Strategy/Product

 * 1) 0.1% unauthenticated desktop to mobile A/B test for Reading strategy