Reading/Quarterly planning/Q4

Brainstorming Guidelines

 * Align with the roadmap
 * This said, it's brainstorming - be creative!
 * Some previous brainstorms: Q1 & Q2 FY 2015-2016 brainstorms, Q3 FY 2015-2016

Android

 * The Feed. (replace the current "Today" screen (Main Page) with an infinitely-scrollable feed of relevant articles based on the user's activity). DBrant (WMF) (talk) 18:10, 4 February 2016 (UTC)
 * Model off the iOS team's implementation (card views).
 * Sort of dependent on the success of the feature in the iOS app, but very likely better than the current Main Page. Featured articles on the Main Page are disproportionately Cricket-related. That's enough with the cricket!
 * Integrate with trending articles API, when it's ready?
 * And then trending and recommendations can tie in nicely with google now also KHammerstein (WMF) (talk) 00:00, 10 February 2016 (UTC)
 * Wiktionary. DBrant (WMF) (talk) 18:42, 4 February 2016 (UTC)
 * Expand current Wiktionary integration to more languages (currently restricted to en). Will require more server-side work to massage non-en pages.
 * Split off into its own app, and replace the current (outdated, Phonegap-based) Wiktionary app.
 * Comment splitting Wiktionary into its own app might be a step in the wrong direction. It seems to me that a single integrated app might be preferable. Is there a rationale for wanting to split off Wiktionary? --Pine ✉ 18:14, 7 February 2016 (UTC)
 * I think an argument can be made for both cases. But the reality is that we currently have a Wiktionary app published on Google Play that is severely out of date (but still has ~75k users). If it's simple enough to split off our new integrated Wiktionary dialog into its own app, and replace the current one, it might be worth pursuing. We should, of course, also weigh the option of sunsetting the current Wiktionary app entirely. DBrant (WMF) (talk) 15:00, 8 February 2016 (UTC)
 * Some integration with the Wikipedia app would definitely be nice, but I find Wiktionary very useful on it's own and would appreciate direct access to it via it's own app. (the old wiktionary app was nice to have, for what it was) Also would be awesome if it could support using the content offline (e.g. when someone is travelling). Probably integration of structured data in wiktionary would help towards making such an app more easily possible and able to do more. Aude (talk) 19:33, 8 February 2016 (UTC)


 * Moar Wikidata. DBrant (WMF) (talk) 18:42, 4 February 2016 (UTC)
 * Native info windows populated from Wikidata.
 * This needs careful thought. We already have the infoboxes in Wikipedia and I wouldn't want to replace them with something automatically generated from Wikidata. With the infoboxes, users can control what fields are there, etc.  There are plans or ideas for improving infoboxes and make them fully machine readable, etc. T114251 Aude (talk) 19:33, 8 February 2016 (UTC)
 * Inline with link previews, search results?
 * Move away from hamburger menu. DBrant (WMF) (talk) 18:50, 4 February 2016 (UTC)
 * Surface more clearly the features we want users to see.
 * Force ourselves to trim away features that are unnecessary.
 * This sounds really cool, but we could prototype first! KHammerstein (WMF) (talk) 23:59, 9 February 2016 (UTC)
 * New directions in microcontributions. DBrant (WMF) (talk) 18:42, 4 February 2016 (UTC)
 * Engage with community of editors/admins to generate ideas for apps to handle low-hanging, repetitive administrative tasks.
 * Make app aware of metered connections BSitzmann (WMF) (talk) 23:47, 8 February 2016 (UTC)
 * When on a metered connection (e.g. on a cellular data plan):
 * Lazy load images (only load shortly before we scroll to it)
 * Turn off image widening
 * Focus on more sessions and longer sessions for existing users KHammerstein (WMF) (talk)
 * Google now integration to encourage coming back to the app
 * Trending, recommendations, nearby, ...?
 * Improve read more to encourage longer sessions
 * Test different amounts, locations, designs

iOS

 * Idea

Infrastructure, APIs, and Services

 * Idea

UX Standardization

 * Idea

Web

 * Mobile web stable channel speed/architecture ABaso (WMF) (talk) 05:12, 29 January 2016 (UTC)
 * Private multiple watchlists --ABaso (WMF) (talk) 18:02, 3 February 2016 (UTC)
 * Integrable as general collections (reading lists) in Apps. DBrant (WMF) (talk) 17:33, 4 February 2016 (UTC)
 * Recent discussion on (Expiring watch list entries) has included various ideas of expanding watchlist entries to include tags that could be used to expose multiple lists. There are also  (Multiple watchlists) and  (Public and private watchlists, shared watchlists) and I'm sure many other related requests for improving watchlists. This seems like an area where a suite of improvements could be designed and implemented possibly in collaboration with WMDE and other interested parties. --BDavis (WMF) (talk) 22:36, 6 February 2016 (UTC)
 * This proposal does not seem to be related to the roadmap. Perhaps you want to propose a change in the roadmap? Nemo 16:44, 7 February 2016 (UTC)
 * The roadmap says "global south", so let's fix known, self-contained bugs that reduce the quality of the websites for all unregistered users with limited networking or resources:    Nemo 16:43, 7 February 2016 (UTC)
 * As a stretch, let's do the same for casual users and light editors who would otherwise be forced to use the desktop site for simple activities:  Nemo 16:43, 7 February 2016 (UTC)
 * Can we get Wiktionary integration on mobile web? --Pine ✉ 18:15, 7 February 2016 (UTC)
 * Would be interested in splitting of Special:Nearby out of MobileFrontend and adding maps, like we did in the Android app :) Aude (talk) 19:34, 8 February 2016 (UTC)