Change Details

**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

**Primary target audiences** **Quant:** KR: 2% decrease in editor abandonment KR: Engagement with full page editing is comparable to Android KR: Increase in unique user edit rate Guardrail: Passes review from accessibility users **Qual**: No reports of reasonably fixable bugs with the native editor through the app store or our support email in a 30 day period post release **Measurement Plan ** AB test if we see a higher rate of edits per person that engage with the new editor

**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.Primary target audiences** **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)Quant:** Are more users attemptingKR: 2% decrease in edits? How does this change with discoverability interventions? Native Editor full page editingor abandonment Suggested Edits prominenceKR: Engagement with full page editing is comparable to Android Are we seeing a differencKR: Increase in affordances engaged with for native editor?unique user edit rate 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 AmericaGuardrail: Passes review from accessibility users **Target Qualitative Audience** Low Bandwidth Readers Blind and Low Vision Users / Accessibility ExpertsQual**: No reports of reasonably fixable bugs with the native editor through the app store or our support email in a 30 day period post release **Measurement Plan Moderators** AB test if we see a higher rate of edits per person that engage with the new editor