- The Android team wants to begin client work by 19 October. We would prefer the API to be functional before then, but it ought to be in at least an advanced state of development, and delivered no later than 1 November.
- The API is time-sensitive because the feature it will enable us to build is part of our Q2 OKRs.
- The purpose of Android Suggested edits image suggestions is to allow users to quickly and easily add lead images to an article in one language, based on the lead images from articles in another language.
- This is part of Android's Q2 OKRs, to increase usage of the Suggested edits feature.
- Initially, the users of Suggested edits on the Android app. We will pilot the feature so that other teams coming after can refine their presentation.
- In Q4, the Growth team will introduce similar functionality on the web, meaning an expansion of the potential audience.
- In order to expand the number of editors on the Android app, and the quality and relevance of articles, an easy and straightforward way to suggest Commons images to be added to articles is required.
- The fact that 3 teams within the Foundation want to do similar work this year should make it apparent that there is a widely perceived user need.
- This is extensively documented in the parent ticket T256081
- The tl;dr version is that an Android user will see a call-to-action when reading an article without an image, asking if they would like to add one. They tap on the CTA and are presented with a suggested image from a similar article. They choose whether to add the image to the article or not. We need an API that will return suggested images, as outlined in the parent ticket.
- As mentioned, this is aligned with team, department, and overall Foundation goals to increase editing and welcome newcomers.