#### Background
During the 2023-2024 FY the Product & Technology organization has a set of objectives to enhance Wiki experiences. One of the metrics the iOS team is aiming to move is a 10% increase in mobile contributions that are not reverted.
**Our Hypothesis is:**
If we improve editing through the iOS app we will be able to keep experienced editors we've reengaged through the introduction of Watchlist. Our goal is to introduce Suggested edits to the app. We will explore an alt-text micro task and if that does not yield the results we are hoping for, we will introduce Image Recommendations or Machine Assisted Article Descriptions as the Initial suggested edit for the iOS app. Prior to release of the new Suggested Edits task we will make much needed improvements to our wikitext editor that that it is native and has better performance.
###How will we know we are successful?
The new features and improvements must prove how it contributes to the KR 1.1 of the Annual Plan:
Increase unreverted mobile contributions in the main article namespace on Wikipedias by 10%, averaged across a representative set of wikis.
Additionally, we estimate we can increase the average monthly edit count per editor from 4.9 to at least 5.5, bringing it closer to Android's 6.7 monthly average, and significantly higher than mobile web's monthly average edit rate of 4.2 edits per editor.
**Validation**
- Increase the average monthly edit count per unique editor from 4.9 to at least 5.5
- 10% Increase in unreverted mobile contributions in the main namespace
- 2000 articles enhanced using Suggested Edits
**Guardrails**
- Revert rate does not increase
- Geographic bias is not worsened
- Less than 5% of users report NSFW or offensive content
**Curiosities (nice to have) **
- Are more users attempting edits?
- How does this change with discoverability interventions?
- Native Editor full page editing
- Suggested Edits prominence
- Are we seeing a difference in affordances engaged with for native editor?
- Do we see a decrease in abandonment for folks using our native editor?
- Do we see an increase in time spent with the native editor?
- What impact does Geography have on the suggested edit interventions?
- What impact does emphasizing captions and alt-text have on task completion and user satisfaction with feature?
###Target Quant Regions and Languages
- Spanish, French and Portuguese speakers in the Americas (North, South and Central) and Caribbean
- Chinese speakers in North America
###Target Qualitative Audience
- Low Bandwidth Readers
- Blind and Low Vision Users / Accessibility Experts
- Moderators
####User Stories
**Native Editor**
- When I make a typo on a talk page, I want to be able to edit a full talk page in my iOS app, so that I can delete the typo
- As a user that just completed a Suggested Edit and noticed a typo in the article, I want the cursor to stay in place and not jump around when editing the full article, so I can make precise edits without frustration.
- As an avid user of the iOS app, I want the UI to be consistent throughout the app, so that I can cut down on context switching
**Suggested Edits**
- As a Dominican user of the Wikipedia iOS app on NYC Metro, I would like to evaluate images for Spanish Wikipedia and determine if they should go into an article, so that I can contribute to Wikipedia articles that are in need of more content.
- As a Chinese Canadian editor of the Wikipedia iOS app, I would like to be aware of opportunities to expand content on Chinese variant Wikipedia articles while receiving guidance and positive reinforcement so that I can grow my confidence as an editor
- As a user with limited data, I want to read alt-text, so even if images are not loaded, I am aware of what is in the image
- As a user navigating articles with a screen reader, I want quality alt-text to be available , so that I have the same additional context about an article as users that are not using screen readers