The Android team is working to enhance the messaging interface. The OKRs we originally established are as follows:
Objective: 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
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
The questions we will also monitor is:
- Do we see a change in time spent/session length
- Are there improvements throughout the funnel and are there differences when compared to Mobile Web
- Have our changes impacted user talk pages vs article talk pages in different ways?
- Share with the Android team the current baseline for the Key Results listed above or establish that the data is too difficult to collect so that modifications to the OKRs can be modified
- Share with the Android team the answer to the following questions
- What do we know about the Android app talk page usage presently? Take into consideration questions on T293114
- What is the # of edits to the talk page namespace comparative to number of editors/general edits in app for native talk pages VS # of edits to talk page namespace on mobile web comparative to the number of editors/general edits on mobile web
- What is the bounce rate/abandonment for talk pages by platform? Specifically, did someone attempt to edit a talk page and failed to / didn't click publish. How does this bounce rate compare to mobile web?
- Any interesting insights about talk pages once the native talk pages were released
- Feel free to be agile, by pulling what information is easier to get (ex. by project) and working on the more complicated parts later and sharing it once you have it
- For the bounce/abandonment rate