Feature job story for Q2
As a Wikipedia editor with an Android device, I want to efficiently respond to actionable notifications and effectively communicate with other users so that I can improve wikipedia projects with confidence and in a productive and equitable way.
Target users have a more intuitive and enhanced communication interface to reduce barriers for productively collaborating with other Wikipedians to increase confidence while improving wikiprojects.
We currently support article and user talk pages in the Android app. However, there are user workflows we have not deliberately thought about. This quarter we want to enhance our existing talk page experience and explore new feature ideas to fill gaps that exist in user workflows as it relates to unlocking collaboration between users. It is a priority that our discussion experience feels at home on the Android platform but doesn’t disrupt the workflows of users using other platforms.
While we will try to accommodate logged out users, our priority is logged in users. We will build on our preliminary communications work and notifications work from last quarter.
By the end of this fiscal year, we hope to improve collaboration workflows that encourage productive edits and engagement. Additionally, we hope to sufficiently address the concerns raised on village pump and Phabricator, that are within our ability to address.
Q1 Product Requirements
How will we know we were successful?
- Key results (Overall increase in Talkpage edits): Talk Namespace edits made through Android app and not reverted within 48 hours increases by 10% 30 days after release of interventions
- Key results( Penetration Increase amongst active editors): Of the people who publish an edit to a wiki, across namespaces, in a month, we see an 10% increase in the percentage of people who publish an edit to a talk page that is not reverted within 48 hours.
- Key Result: 2% Decrease in abandonment rate amongst target users on talk pages
Other Research Questions
What impact did our changes have on session length of talk pages
What impact did our changes make on the EditAttempt Step funnel (Visits to talk pages, hitting edit, attempting to publish, and successfully hitting publish). How does this compare to mobile web?
Was there an increase in overall talk page edits amongst target users and do we notice more talk page activity amongst our existing editors?
Are there differences in the data for user talk pages vs. article talk pages
More information will be available on our project page