Reading/Quarterly planning/FY2016-2017/Q2

Brainstorming Guidelines

 * Ideas for Q2 FY 2016-2017 (October 2016 - December 2016) should align with each platform's focus areas, as identified in Reading's strategy (see also full WMF FY 2016-20127 annual plan).
 * Some previous brainstorms: Q1 & Q2 FY 2015-2016 brainstorms, Q3 FY 2015-2016, Q4 FY 2015-2016 planning, Q1 FY 2016-2017 planning.

Web

 * Lazy load images in Vector
 * Wikigrok game (standalone not mediawiki)
 * Make Minerva available as a desktop skin in desktop preferences/via opt in panel on mobile site (solve tech debt on the way)
 * Push web service back end for allowing users to subscribe and unsubscribe from push services (infrastructure will be useful for web and app) Jdlrobson (talk) 15:58, 15 August 2016 (UTC)
 * Wikidata descriptions translate tool with mobile web call to action for users of multiple languages
 * Expose links such as Featured content and Current events that are available in the navigation area of Vector in Minerva. Bmansurov (WMF) (talk) 11:51, 12 August 2016 (UTC)
 * Better user experience for non JavaScript browsers: Bmansurov (WMF) (talk) 11:51, 12 August 2016 (UTC)
 * Add article title in languages in Special:MobileLanguages similar to how the language overlay works; Bmansurov (WMF) (talk) 11:51, 12 August 2016 (UTC)
 * Make Special:MobileMenu contents available without leaving the page; Bmansurov (WMF) (talk) 11:51, 12 August 2016 (UTC)
 * Allow users to login and logout; Bmansurov (WMF) (talk) 11:51, 12 August 2016 (UTC)


 * Verify that basic functionality works and look and feel are ok for browsers that are important for new readers (UC mini, Opera mini, more?). Setup a test strategy and verify that things works on those browsers. PHedenskog (WMF) (talk) 07:26, 16 August 2016 (UTC)
 * Images in portrait mode on mobile: Make sure images are centered on small devices in portrait mode for a more pleasant experience. PHedenskog (WMF) (talk) 07:26, 16 August 2016 (UTC)
 * There is a related, albeit opposite, task in phabricator: https://phabricator.wikimedia.org/T142627
 * Tablet experience - Work on MobileFrontend for screens wider than phones. tablets + desktops Npangarkar (WMF) (talk) 05:04, 17 August 2016 (UTC)
 * Expose article stats on web - expose metadata about artilcles and inform readers about the liveliness and quality of articles  Npangarkar (WMF) (talk) 05:04, 17 August 2016 (UTC)
 * Hovercards (pending results of research) Jkatz (WMF) (talk) 21:41, 17 August 2016 (UTC)
 * Image improvements (specifically those around lead image selection, which impact search results, VE, hovercards and both apps) https://phabricator.wikimedia.org/T132605 Jkatz (WMF) (talk) 21:41, 17 August 2016 (UTC)
 * Overall article presentation, tying together
 * what is above in terms of browser work
 * uncollapsing sections + adding TOC
 * moving lead paragraph up
 * splash page (per google PWA) Jkatz (WMF) (talk) 21:41, 17 August 2016 (UTC)

Android

 * Personalized metrics for readers/editors. "You have read three pieces about sports and edited two design pieces this week." See Slide 10 and related article. Melodykramer (talk) 21:57, 10 August 2016 (UTC)
 * Experimenting with various push designs. "Perhaps a push notification sounds or feels different if I’m in a car versus. on foot vs. seated. How might a push change if I haven’t picked up my phone in an hour versus if I’m clearly on the phone? Could the message be different based on the temperature of the phone?" See related article. Melodykramer (talk) 21:57, 10 August 2016 (UTC)
 * Considering we don't do push notifications at all yet, maybe we could do something simpler as a first foray into it. T95396 strikes me as a good candidate. MHolloway (WMF) (talk) 07:53, 17 August 2016 (UTC)
 * Reading lists V2 - Improve on a feature that is already in production. do usability research and learn from analytics. - Npangarkar (WMF) (talk) 05:04, 17 August 2016 (UTC)
 * +1. Reading lists are mostly working well but have some issues that we need to address (T139230 and T135273, for example).  MHolloway (WMF) (talk) 08:05, 17 August 2016 (UTC)
 * Improve the editing experience. I would like to see us devote some resources to this one of these quarters, even if it's just coming up with a concrete plan for how we will implement the various features required for a full-fledged editing experience.  However, I don't see any provision for work on editing features in the Reading strategy document.  Is this officially outside our purview? MHolloway (WMF) (talk) 08:05, 17 August 2016 (UTC)
 * For reference, here are notes from a discussion on this topic at this year's Wikimania: https://etherpad.wikimedia.org/p/Wikimania2016-discussion3c MHolloway (WMF) (talk) 08:09, 17 August 2016 (UTC)
 * Related but potentially standalone task: Correctly handle editing restrictions/page protection (T132834, T85528). MHolloway (WMF) (talk) 14:33, 17 August 2016 (UTC)
 * Tablet experience. MHolloway (WMF) (talk) 08:13, 17 August 2016 (UTC)
 * Feed 2.0 - a smorgasbord of enhancements to the Feed experience including new cards, new features, and improvements. We have about 40 Phabricator tickets related to this effort already, about half have been tagged for a 2.0 MVP. As in 1.0, this effort would require work across the Android app and Content Service. Changes in the latter can be used by all platforms, especially iOS.
 * Per strategy and annual plan, a moderation tool specifically for the app. Ideally one that can be used by casual users.  Brainstormed ideas and community consutlation underway here: Reading/Readers contributions Jkatz (WMF) (talk) 21:41, 17 August 2016 (UTC)

Reading Infrastructure

 * Multi-Content Revisions - the implementation of the lookup interface would probably fall to reading
 * Article meta date/ "key value pairs"