Reading/Quarterly planning/FY2016-2017/Q1

Brainstorming Guidelines

Ideas for Q1 (From July to September) should align with each platform's focus areas, as identified in our strategy: Reading/Strategy/2016-2017 plan, specifically:
- iOS = Improve the Encyclopedia Experience
- Web = New Readers (focus on developing countries), or, in light of ongoing research for New Readers and a lot of 'debt', Improve the Encyclopedia Experience.
- Android = Community of Readers (new experiences)
This said, it's brainstorming - be creative!
Some previous brainstorms: Q1 & Q2 FY 2015-2016 brainstorms, Q3 FY 2015-2016, Q4 planning.

Ideas from User Interaction Consultation

Android

Fill out experience. Ability to read talk pages and browse categories (That’s what some unhappy users say in their reviews at google play store.) Bmansurov (WMF) (talk) 18:29, 17 May 2016 (UTC)[reply]
Finish feed. Work started on feed might not be finished by end of this quarter. Jkatz (WMF) (talk) 18:36, 17 May 2016 (UTC)[reply]
Navigational overhaul. App spring cleaning and navigational re-thinking around feed and tabs. Jkatz (WMF) (talk) 18:25, 17 May 2016 (UTC)[reply]
Lead image centering. Allow users to select and/or center lead image and store in image/article metadata. Requires moderation...somewhere. Jkatz (WMF) (talk) 18:36, 17 May 2016 (UTC)[reply]
Wikidata description editing. Allow users to edit wikidata descriptions. Need feedback loop, but moderation takes place in wikidata. Jkatz (WMF) (talk) 18:36, 17 May 2016 (UTC)[reply]
Quickfacts - surface structued data - Npangarkar (WMF) (talk) 16:12, 18 May 2016 (UTC)[reply]
Select page extract. Allows users to highlight the key sentence that we'll use as the text extract for the page (microcontribution) Phuedx (WMF) (talk) 16:28, 18 May 2016 (UTC)[reply]

Web

Banners. I'm not convinced about this but if Android is working on lead image centering this would be a good opportunity to collaborate. Jdlrobson (talk) 15:49, 18 May 2016 (UTC)[reply]
PDF download article (for mobile web users that want to keep content for offline) JHernandez (WMF) (talk) 17:35, 17 May 2016 (UTC)[reply]
- +1 a "Take offline" button. Starting with something simple we can gauge what the interest for such a feature is compared to say language switching. Jdlrobson (talk) 15:49, 18 May 2016 (UTC)[reply]
Mobile accessiblity. Go over the list of most widely used templates and make sure they look good on mobile devices. Submit improvements where necessary. Bmansurov (WMF) (talk) 18:29, 17 May 2016 (UTC)[reply]
- Roll out TemplateStyles extension and work as community advocates to clean up commonly used templates and identify blockers for doing so. benefits - editors who are more considerable of mobile and pages that are more mobile friendly. Potentially strategic reducing future friction and unblocking longstanding RFCs such as thumbnail default size. Jdlrobson (talk) 15:49, 18 May 2016 (UTC)[reply]
Hovercard roll-out. Updates to hovercards for broader rollout, which include some important image improvements and logged-out reading preferences. Jkatz (WMF) (talk) 18:36, 17 May 2016 (UTC)[reply]
Sessions. Work with analytics to generate session metrics using event logging Jkatz (WMF) (talk) 18:36, 17 May 2016 (UTC)[reply]
Targeted Quicksurvey. The Global Reach team would like to use the quicksurvey in a targeted way. These are the 2 ways of target we would like to see: 1) Per Wikipedia Zero partner; 2) Per country. This information will be valuable to learn more about the emerging communities’ WP readers, and also to measure the impact of the Wikipedia Zero program. DFoy (WMF) (talk)
Allow Quicksurvey to support multiple questions. This feature is important to allow Wikipedia Zero users to be surveyed without cost to them. Using other external survey methods would be expensive for Zero users. DFoy (WMF) (talk)
Push notification messaging service provide infrastructure that allows users to register for services and for services to send push notifications to any subscribers. (no web ui changes). Benefits of this are that we'll enable community to experiment with notifications amongst small groups and we'll be able to explore services such as pushipedia. Jdlrobson (talk) 15:49, 18 May 2016 (UTC)[reply]
Reading suggestion. Based on the user's reading history, suggest an article to read next. Bmansurov (WMF) (talk) 15:54, 18 May 2016 (UTC)[reply]
- As in related pages? :) --Melamrawy (WMF) (talk) 16:24, 18 May 2016 (UTC)[reply]
- (Toby:) Use navigation vectors instead of reading history? Regards, Tbayer (WMF) (talk) 16:32, 18 May 2016 (UTC)[reply]
Better multimedia experience on mobile. Allow mobile users to see video clips and listen to audio clips without leaving the page, i.e. in an overlay. Also improve the media player controls (longer seek bar, etc.) Also, allow downloading audio and video files. Bmansurov (WMF) (talk) 15:59, 18 May 2016 (UTC)[reply]
Paragraph summarization. Create an AI that highlights the most important sentence in a paragraph. Since this is language specific, start with English. Bmansurov (WMF) (talk) 16:02, 18 May 2016 (UTC)[reply]
- Is this more like the Highlights suggestions, or more of a share-a-fact?--Melamrawy (WMF) (talk) 16:24, 18 May 2016 (UTC)[reply]
Analytics -- TNegrin (WMF) (talk) 16:41, 18 May 2016 (UTC)[reply]
- Retention
- Engagment (session depth)
Sharing snippets of text. Allow sharing a block of highlighted text via a unique URL (appended hash maybe?). Bmansurov (WMF) (talk) 16:09, 18 May 2016 (UTC)[reply]
Tablet + Desktop experience - Make a better reading experience out of the tools we have - Npangarkar (WMF) (talk) 16:10, 18 May 2016 (UTC)[reply]

iOS

Quickfacts - surface structued data - Npangarkar (WMF) (talk) 16:12, 18 May 2016 (UTC)[reply]

Content service

Basic trending articles. Look at two previous days of pageview ranks, then calculate the delta. Generate top movers (if not on the list day-2, consider movement from position 1001 to position x). --ABaso (WMF) (talk) 16:05, 18 May 2016 (UTC)[reply]
Search backend Integration --TNegrin (WMF) (talk) 16:41, 18 May 2016 (UTC)[reply]

Reading Infrastructure

Key-value store (authenticated write + read; public read). Add support for a key-value store that supports both authenticated write and read, plus allows for the ability of public readable key-values. --ABaso (WMF) (talk) 16:02, 18 May 2016 (UTC)[reply]
Template styles - was planned but Coren (a volunteer) picked it up, not sure if there is anything to do here. --Tgr (WMF) (talk) 16:17, 18 May 2016 (UTC)[reply]
AuthManager support. AuthManager is planned to be finished by mid-June, various related activities will remain - support, fixing of old bugs which have now become easy to fix, supporting Security with 2FA etc. --Tgr (WMF) (talk) 16:11, 18 May 2016 (UTC)[reply]
Improve OAuth usability. OAuth is a major enabler of innovation by connecting external installations (Labs, third parties) with Wikimedia user identities, but usability sucks (especially on mobile). T91825 T98880 T103587 --Tgr (WMF) (talk) 16:17, 18 May 2016 (UTC)[reply]
Process API metrics. We have the API usage data in Hadoop now, but some more work is needed to get insights out of it (dashboards etc). --Tgr (WMF) (talk) 16:21, 18 May 2016 (UTC)[reply]
more ideas: https://etherpad.wikimedia.org/p/reading-infra-2016-17-q1