We build and maintain software for the reading experiences for all the users of the Wikimedia projects on the web and in the Wikipedia mobile apps.
Back to Product and Technology
About us
In a time where fewer people come to Wikipedia via search engines, we want to ensure that when readers do come to Wikipedia, they find it immediately useful, memorable, and enjoyable. We want readers to remember Wikipedia from the first time they visit, so that they return to find opportunities to go deeper – actively participating and engaging in their learning experience, and growing into the daily readers, donors, and contributors of the future. This is the focus of the Reader teams.
We are a group of three teams. Reader Experience focuses on enhancing ways of learning and engagement for active readers, while Reader Growth focuses on ways of learning and engagement for new and casual readers. The reader-focused work of the Wikimedia Apps teams, who focus on the most active and enthusiastic readers, also falls under the scope of the Readers teams.
This approach is designed to ensure that our work advances very stage of being a reader, from brand new to experienced, and builds on both foundational and transformative user experiences, addressing the evolving needs of our projects and their diverse audiences. We work across platforms (mobile, desktop, apps), and are part of the Core Experiences group.
The work of all three teams – Apps, Reader Experience, and Reader Growth – is jointly overseen by Olga Vasileva, Nat Baca, and Carolyn Li-Madeo.
Check out our repository and learn more about:
All reader-focused work on the mobile and desktop websites was previously housed under one umbrella as Reading Web (archived), which was split in July 2025 to seed the Reader Growth and Reader Experience teams.
Prior to its iteration as the Web team, the team was known as Reading Web or Readers Web, and before that (until 2015-ish) Mobile Web. You may still find these names used in the documentation.
Projects
Our work constitutes most of the objective Wiki Experiences 3: Consumer Experiences (WE3; owner: Olga).
Our objective is that readers from multiple generations engage, and stay engaged, with Wikipedia, leading to measurable increases in retention and donation activity.
This objective will focus on retaining new readers through innovative content formats, core audiences through strengthening familiar reading experiences, and ensuring long-term sustainability by deepening reader connections and diversifying donations. It will include a continuation of our work into making content easier to discover through new and more experimental features such as AI summaries or personalized rabbit holes. It will also include work on retaining and improving the quality of the reading experience deeper in the reading funnel and on exploring reading curation through reading lists and other non-editing participation. For donors, this work will continue focusing on diversifying revenue sources from within the platform.
The code in the brackets (ie, "WE3") is used in the annual plans, and helps identify and report the projects (key results) and smaller pieces of work for each key result (hypotheses).
Each page below corresponds with one of our projects dedicated to this objective (key results) and details its associated work.
People
Group leads
Reader Growth
Reader Experience
Apps
People we work with
Why do we focus on readers?
The Wikimedia Foundation's Product and Tech department's strategic vision is a multigenerational project that supports evolving ways of creating and engaging with free knowledge. Even as the internet becomes cluttered with low-quality information, Wikipedia remains a critical trustworthy source of neutral human-curated knowledge.
Yet we are facing an existential challenge: our pageviews have flattened or declined, even as global internet use continues to grow. The percentage of people worldwide who know and use Wikipedia is shrinking, and accordingly, so is the percentage of users who might become inspired to contribute to Wikipedia in the future, as editors or donors.
This decline is driven by new generations learning through new platforms and technologies. The way people learn online has shifted drastically in recent years. Specifically new generations learn from and use the internet in ways different from how they have traditionally used Wikipedia. New generations of internet users are less reliant on search engines for information seeking, and more prone to experiences within specific apps that are heavily personalized and encourage a lean-back approach — different from the specific fact seeking which drives most of our current pageviews.
This rapidly changing internet is also full of new, and sometimes more useful, ways to access knowledge and learn. Global internet users are more diverse, not only in age and geography, but also in what they need from learning and being online - there's visual learners and audio learners, people who prefer depth over breadth and vice versa, people who want a fact in 10 seconds, and those willing to spend hours in a rabbit hole.
In the past, we could take for granted that most people using the internet would encounter Wikipedia often. Today, we need to recognize that every visit is a crucial opportunity to spark a lifelong affinity to Wikipedia. In order to introduce a new generation to Wikipedia, we need to ensure that when they do land on the site, it is immediately useful and memorable enough to make them curious and encourage them to return the next time they see a link to Wikipedia. For those millions of people who visit Wikipedia often, we need to solidify their long-term connection to Wikipedia so that they grow into the editors and communities of the future.
Questions for communities
Tell us about someone you know who reads, but does not edit Wikipedia:
- Why do they read Wikipedia?
- What's one thing that would help them better learn from Wikipedia?
Reporting an issue
- Use the Phabricator Bug Report template
- Tag the task with
#reader-experience-teamor#reader-growth-teamor#wikipedia-ios-app-backlogor#wikipedia-android-app-backlog(Check the Developers/Maintainers page to check who is responsible for what.) - Add any relevant component tags (e.g.
#vector-2022,#minervaNeue)
If you are comfortable with Phabricator and doing some work first, please search first: before creating a bug, check Phabricator search to see if the issue's already been reported.
Requesting a feature
Before submitting a feature request, understand that the Wikimedia Foundation undergoes a rigorous Annual Planning Process to determine which features to pursue in any given year. Your feature request is most likely to be accepted if it falls within an existing annual plan initiative.
First, consider adding your feature request to the Community Wishlist to have it more formally integrated into our planning process.
Alternatively, you may submit a task to request a feature as well:
- Use the Phabricator Feature Request template
- Tag the task with an appropriate team tag (see above)
- Add any relevant component tags (e.g.
#vector-2022,#minervaNeue)
If you don't have access to Phabricator, see phabricator/Help#Creating your account for detailed instructions on how to create one.