#### Background
The Android team was responsible for the[[ https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Add_an_image_MVP | Image Recommendations MVP ]]In May 2021 the Android team built an MVP for Image recommendations. Our roadmap included learning from the [[ https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Structured_tasks/Add_an_image | Growth team's V1 ]] implementation of image recommendationsThe goal of the MVP was to determine if it would be a good* task for newcomers, especially on mobile. Now that V1 is complete andThe results were generally positive resulting in the Growth team is exploring section images,introducing the feature on Web (Desktop and Mobile). the Android team is interested in bringing the Image Recommendations task into the appIt has had mostly positive results and the community is acquainted with the feature giving us the confidence to bring the feature back to the app with the ability to actually post photos.
#### How will we know we were successful
**Validation**
KR 1.1: Conversion and Retention rates of growth target users are the same as Structured Tasks users with similar demographic profiles 1: 2000 articles have images in a 30 day period
KR 1.2: 10% of editors whose first edit is through image recommendations task that successfully tries a different suggested edit task, or wikitext edit provides a quality editAverage at least 8 edits per session per unique user
KR 1.3: 15% of Suggested Editors try image recommendations task and 70% of those users complete the task again on a separate day in a 15 day period
Guardrail: Rejection rate below 40% and acceptance rate andKR 1.4: At least a 35% task completion rate isn't below suggested edits averagete
Guardrail: Two new communities do not request to turn the feature offKR 1.5: DAU of Suggested Edits increase overall
**Guardrail: Revert rats**
KR 1.1: Feature does not exceed Mobile Web equivalent
####Must Havesworsen gender or geographic bias*
[ ] Ability for community to turn off feature for their wikiKR 1.2: Less than 5% of users report NSFW or offensive content
[ ] Allow filtering for topicsKR 1.3: Users spend at least 10s evaluating a task before publishing it
[ ] Quality Gates to limit the number of image recommendations in a day and messages if they spend too little time on the taskKR 1.4: Bounce rate does not exceed 50%
KR 1.5: Reject and Accept rate does not deviate from Mobile Web or MVP by more than 10%
KR 1.6: Revert rate does not exceed 15%
**Curiosities**
KR 1.1: Do these numbers differ by language or user tenure
KR 1.2: If this is a user’s first suggested edit, do they go on to try others?
[ ] Distinction it is an edit from the Android app suggesKR 1.3: Feature perception by geographically underrepresented edits for purpose of tracking revertsgroups on large language wikis
####Potentially out of scope####Must Haves for V1
- Entry point should reside in Suggested Edits screen and within an article
- Image Recommendations task should exist immediately below Article Descriptions
- There should be an indicator it is a new task to users that have completed at least one suggested edit and the new indicator should go away the second time the visit the screen
- Users should have an option to add a caption on the screen but it should not be prompted
- There must be a way for users to report issues with the feature, it should take them to the support email
- Users should have an entry point in the task to the FAQ page
- There should be some sort of way to ensure users aren’t continuously hitting yes in a short (less than 5s) span of time to guard against bad faith edits
- There must be onboarding to the feature
- Users should be able to access full article and image metadata
- Do not allow users to skip without providing some feedback (Yes, No, Not Sure)
[] - Allow users to zoom/pinch on image
- Considerations for images running out or task not being available in certain languages
**Nice to Haves**
- Users able to filter by topics
- Subtle positive reinforcement (display in darkmode)
**Potentially out of scope**
- Section Images
####Things to consider
[] How to improve captions from the Growth team's iteration
[ ] If there should be additional requirements for who can do the task
#### User Stories
- As a Wikipedia Android app user with a small screen and inconsistent internet, I would like to evaluate images and determine if they should go into an article, to contribute to Wikipedia articles that are in need of more content.
- When I am using the Android app, I want to be able to add images with one hand to many articles on my mobile device, so that I can be productive while riding the bus in Bogotà, and listening to music.
- When I am reading an article about Chun Shui Tang Bubble Tea in Taiwan, I want to learn that I can add an image to the Chinese language article, so that I enhance articles that I find interesting.
- When I try to add an image to an article and fail, I want to learn how to do this task, so that I can build my confidence before going on to adding image that I want as my intended edit.
- BONUS: When I am recommended an image for an article in Bengali and I don’t believe the image is a good fit and I am physically next to the subject of the article, I want to be made aware there is a Commons app, so I can upload the appropriate image using the Commons App
#### Target Quant Regions and Languages
- Spanish Wikipedia
- Portuguese Wikipedia
- Chinese Wikipedia (or Persian Wikipedia if the API isn't changed)
Regions:TBD
Primary Languages: TBD - Hindi Wikipedia (or Bengali Wikipedia if the API isn't changed)
#### Target Qualitative Audience
TBD
- Spanish and Portuguese speakers in LATAM and Caribbean countries
- Hindi speakers in India
- Chinese speakers in Taiwan
- No more than 40% of our testers should identify as male