Wikimedia Apps/Team/Android/Android Annual Plan 2024-2025
 | This page is for Fiscal Year 2024-2025, and is no longer being updated. See the team's page for ongoing work: Wikimedia Apps/Team/Android. |
The Android team's work was guided by the Wikimedia Foundation Annual Plan, and specifically the Product & Technology department's Objectives and Key Results. The Annual Plan relates to the Wikimedia Foundation's fiscal year, which starts on July 1 and ends on June 30 of the following year.
The Android team typically expects that about half of our time will be devoted to annual planning priorities in the coming year, while the other half will be spent on technical maintenance and other essential work to support our actively and passively maintained projects.
Essential work
[edit]- Maintained Projects: We continued to support anti-vandalism tools while trying to integrate with Community Config and various suggested edits. There are other features in the app like Places, as well as the overall Android app platform that we continued to maintain, and fix bugs raised by users.
- Temporary Accounts: The Android team supported updates and features required to accommodate the release of Temporary Accounts.
Completed Annual Planning Priorities
[edit]Wiki Experiences 3.1
[edit]There is a new generation of readers looking to build a lasting connection with Wikipedia. As a result we plan to explore opportunities for readers to more easily discover and learn from content they are interested in. The Android app team will release a series of experiments and determine in partnership with the community, which intervention best contributes to reader retention.
Wiki Experiences 3.2
[edit]Our goal is to provide a diversity of revenue sources while recognizing our existing donors. Based on feedback and data, our focus is on increasing the number of donations beyond the methods the Foundation has relied upon in the past, specifically the annual banner appeals. We want to show that by investing in more integrated donor experiences, we can sustain our work and expand our impact by providing an alternative to donors and potential donors that are unresponsive to banner appeals. 50% is an initial estimate based on the decreased visibility of the donate button on Web as a result of Vector 2022, and the increase in the number of donations from FY 2023-2024's pilot project on the Wikipedia apps to enhance donor experiences (50.1% increase in donations). Evaluating this metric by platform will help us understand trends in platforms and if different tactics should be deployed in the future based on a difference in behavior based on platform audience.
| Key Result | Android team hypothesis | Project details | Timeline |
|---|---|---|---|
| Wiki Experiences, Key Result 3.1
Release two curated, accessible, and community-driven browsing and learning experiences to representative wikis, with the goal of increasing the logged-out reader retention of experience users by 5% |
If we put an ideal version of a WikiPodcasting feature and a scrappy Wiki Text-to-speech feature on Android in front of users, they will convey they’d repeatedly use the WikiPodcasting feature, but would not use the scrappy Text-to-Speech version outside of accessibility needs. | https://phabricator.wikimedia.org/T386942 | In progress - carrying over to 2025 - 2026 |
| Wiki Experiences, Key Result 3.2
50% increase in the number of donations via touch points outside of the annual banner and email appeals per platform. |
If we update the contributions page for logged-in users in the app to include an active badge for someone that is an app donor and display an inactive state with a prompt to donate for someone that decided not to donate in app, we will learn if this recognition is of value to current donors and encourages behavior of donating for prospective donors, informing if it is worth expanding on the concept of donor badges or abandoning it. | Wikimedia Apps/Team/Android/Private Donor Recognition Experiment | Completed January 2025 |
| Wiki Experiences, Key Result 3.1
Release two curated, accessible, and community-driven browsing and learning experiences to representative wikis, with the goal of increasing the logged-out reader retention of experience users by 5% |
If we introduce a personalized rabbit hole feature in the Android app to recommend condensed versions of articles based on the types of topics and sections a user is interested in, pulled from different articles, we will learn if the feature is sticky enough to result in multi-day usage by 10% of users over a 30-day period, and a higher pageview rate than users not exposed to the feature.
& If we introduce personalized reading lists in the Android app and recommend articles based on articles users are interested in, we will see a 5% increase in reading list feature retention. |
Rabbit Holes | Completed May 2025 |
| Wiki Experiences, Key Result 3.1
Release two curated, accessible, and community-driven browsing and learning experiences to representative wikis, with the goal of increasing the logged-out reader retention of experience users by 5% |
If we create a daily-use Wikipedia-based trivia game in the Android app, logged-out readers who engage with this feature will open the app on multiple days within a 20-day period at a rate at least 5% higher than those who do not engage with the feature.
& If we scale a daily-use Wikipedia-based trivia game in the Android app, logged-out readers who complete the game will open the app on multiple days at a rate 5% higher than those who do not receive a promotion for the game, and thus do not play it. |
Wikimedia_Apps/Team/Android/TriviaGame | Completed May 2025 |
| Wiki Experiences, Key Result 3.1
Release two curated, accessible, and community-driven browsing and learning experiences to representative wikis, with the goal of increasing the logged-out reader retention of experience users by 5%. |
If we enhance the search field in the Android app to recommend personalized content based on a user's interest and display better results, we will learn if this improves user engagement by observing whether it increases the impression and click-through rate (CTR) of search results by 5% in the experimental group compared to the control group over a 30-day A/B test. This improvement could potentially lead to a 1% increase in the retention of logged out users. | Wikimedia Apps/Team/Android/Recommended Content in Search | Completed September 2024. |
| Product and Engineering Support (PES), Key Result 1.3
Run and conclude two experiments from existing exploratory products/features that provides us with data/insights into how we grow Wikipedia as a knowledge destination for our current consumer and volunteer audiences in Q1 and Q2. Complete and share learnings and recommendations for potential adoption for future OKR work in the Wiki Experiences bucket by the end of Q3 |
If we create a Wikipedia-based game for daily use that highlights the connections across vast areas of knowledge, it will encourage consumers to visit Wikipedia regularly and facilitate active learning, leading to longer increased interaction with content on Wikipedia. Success will be measured by completing an experimental project that provides at least one recommendation about gamification of learning as an opportunity to increase onwiki engagement. | New Engagement Experiments/PES 1.3.2: Wikipedia games | Completed September 2024 |
| Wiki Experiences, Key Result 3.1.9 | If we create a daily-use Wikipedia-based trivia game in the Android app, logged-out readers who engage will open the app on multiple days within a 20-day period at a rate at least 5% higher than those who do not. | Wikipedia Trivia Game | Completed July 2025 |
| Wiki Experiences, Key Result 3.1.14 | If we scale a daily-use Wikipedia-based trivia game in the Android app, logged-out readers who complete the game will open the app on multiple days at a rate 5% higher than those who do not play it. | Wikipedia Trivia Game | Completed July 2025 |
Community discussion
[edit]Any project the Android team pursues will include community consultations with impacted user groups.