Page MenuHomePhabricator

Explore Feed Revamp 2025-2026
Open, MediumPublic

Description

Background

The Explore feed is the first thing readers see when they open the Wikipedia app and for years, it hasn't been doing its job.

Engagement is low, the card layout feels static compared to modern feeds, and many readers don't realize it can be personalized. Meanwhile, Wikipedia's depth and breadth — its greatest strengths — can feel overwhelming without clearer structure and relevance signals.

We're redesigning the Explore feed: a two-tab experience where 'Community' surfaces Wikipedia's best editorial content in a familiar, scannable format, and For You delivers a full-screen, immersive experience personalized to your interests, reading history, and location.

This is not a social feed and everything surfaces from Wikipedia's own articles and community.

Strategic Alignment

This work directly supports the Consumer Strategy goal of reaching new audiences and addresses our biggest retention gap: the step from new reader to someone who comes back regularly. It maps to the annual plan KR to perform at least one experiment per platform showing a practically significant improvement in logged-out casual reader retention or an indicator metric.

What we learned before building

Before designing, we ran two studies to understand what readers actually need from the feed.

In-app survey · December 2025 · 1,184 respondents
Current app users universally want more personalization and more interactive content — games, quizzes, and content tied to their interests and reading history. A significant share weren't aware the feed could be customized at all, despite it being the first tab they see on every app open. Games was the least-used feature in the feed and simultaneously one of the most requested improvements, signaling a major discoverability gap.

Qualitative interviews · December 2025 · New and non-app users
Participants brought strong expectations from other feed-based apps. When the Explore feed lacked familiar relevance cues — recency, popularity, personal connection — it felt hard to evaluate and easy to leave. Low-effort, remixed content performed best: features like On This Day resonated because they feel approachable and finite. Participants wanted personalization without algorithmic entrapment.

Prototype testing · Early 2026 · 14 participants
We tested two feed directions with new and casual readers: Focus (full-screen immersive) and Streams (scrollable card feed). The split was exactly 50/50 on preference — but for complementary reasons. Focus felt modern and conducive for daily use; Streams felt organized and credible. That finding directly shaped the final design: the Community tab uses the Streams approach, and the For You tab uses the Focus approach.

"It gives you that swiping gesture which is really addicting... this is a good way to do it because people are so used to this swiping gesture." — Participant, prototype study
"I would probably open it again just because I like to read something in the mornings before going into social media... just a little bit more substantial or meaningful." — Participant, prototype study

The Experience

Two Tabs, Two Experiences

The redesigned feed has two tabs accessible from the top of the Explore screen:

Community

A scrollable feed of content that exposes curation and information about the broader community and movement: In the News, Featured Article, On This Day, Top Read, Picture of the Day, and more. Familiar, structured, and updated daily.

For You

A full-screen, swipeable experience built around you. Each module is a vertical stop in your feed; within each module, you swipe horizontally through a stack of cards. Modules include:

  • Article Recommendations based on your interests
  • Because You Read — articles related to what you last read
  • Continue Reading — your most recent article and your reading list
  • Places of Interest — Wikipedia articles about places near you
  • Discover Recommendations — the latest recommendations based on your reading list
  • Random Article — one surprising article, shake to shuffle
  • Games — a teaser question from today's game with a path to play more

At the end of the feed, users see a "That's it for today" card with the option to add interests, visit the Community tab, or loop back to the top. In the future this screen could serve as a screen of the daily digest or a quiz of what was in the feed that day.

Onboarding

On first meaningful use, readers are invited to select topics they care about. The flow reuses elements of the Android reading list onboarding pattern — clear visual tiles, and search by topic or article. It's lightweight and skippable. Readers also choose their default landing tab (Community or For You), so they arrive at the content most relevant to them from the first session.

Personalization

Personalization in the For You feed is transparent and user-directed. Every card tells you why you're seeing it: "Because you follow Arts", "Based on your reading history", "Places of interest". Readers can dismiss content, save it, hide modules, and update their interests at any time from Settings → Explore Feed → What's driving your feed. No black-box profiling. No algorithmic entrapment.

Design Priniciples

  • Retention before depth — reasons to come back matter more than any single deep read
  • Discovery through remixing — snippets and previews lead into articles, never replace them
  • Transparent personalization — "Because you follow..." not a black box
  • Calm, trustworthy browsing — productive and credible

Core Requirements

The feed must
  • Be immediately useful on app open
  • Surface a mix of fresh content (what's new), familiar content (topics the reader cares about), and community content (Main Page)
  • Clearly signal freshness — timestamps, "trending", "new this week" language where appropriate
  • Allow readers to save, share, dismiss, and hide content — all actions reversible
  • Support the full range of Wikipedia's languages as configured by the reader
The feed must not
  • Summarize content using LLMs — all content comes from Wikipedia articles
  • Function as a social feed with likes, comments, or follower counts
  • Require account creation
  • Feel unstructured or like a catch-all for unrelated feature
Onboarding must
  • Offer popular and trending topic suggestions
  • Allow search by topic or seed article
  • Be lightweight and skippable — no forced setup
  • Let readers set their default landing tab

How we'll know its working

Key Result

By the end of Q4, perform at least one experiment per platform (web and apps) that shows a practically significant improvement in logged-out casual reader retention or another indicator metric over control (with casual reader retention defined as 21-day cumulative retention for web, and 14-day cumulative retention for apps)

Target Reader

Someone who installs or opens the Wikipedia app with intent to read a specific article but has no established habit of returning — a new reader building their first relationship with Wikipedia.

Primary Hypothesis

If we redesign the mobile apps Explore Feed, we'll see a 10% practically significant increase in Explore Feed engagement over multiple days per unique logged-out reader within 14 days of release.

Metrics
  • 1.1 Key Metric: 10% practically significant higher multi-day unique logged-out retained users for "Home" feed within upgraded app compared to Explore feed within holdout
  • 1.2 Indicator: 15% more unique users engage with Home in upgraded app compared to Explore in holdout
  • 1.3 Indicator: Practically significant improvement in reader progression (new-> casual->active)
Guardrails
  • [Phase 2 only] 2.1 Majority of survey respondents report feeling neutral or satisfied with redesigned feed
  • 2.2 No significant decrease in Explore/Home feature retention
  • 2.3 No more than 3% of users turn off all modules and leave them off over course of experiment
Curiosities
  • [Phase 2 only] 3.1 Did this feature have an impact on DAU (check at 90 days)
  • 3.2 How may users personalize their feed (onboarding interest selection counts)
  • 3.3 Do we see a difference in scroll depth from users who configured interests vs those that skipped
  • 3.4 Do we see an increase in click throughs originating from Explore
  • 3.5 Do we see a difference in customization numbers
  • [Phase 2 only] 3.6 Does satisfaction differ based on if a feed is personalized or not and reader type (new vs casual vs active)
  • 3.7 Which modules drive the most engagement

Follow along at:

https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Explore_Feed_Refresh

Quality

TestingOwnerCadence
ExploratoryQSPer Release Candidate
Per Ticket (Feature)EngineeringDuring development
*Smoke TestingQSPer release candidate
*Upgrade TestingQSPer release candidate
Analytics ValidationData AnalyticsWhen Analytics is completed
Internal TestingQSWhen MVP is completed
* Automation Candidate
Environment
TestConditions
PerformanceTest against devices that are older, smaller, on a poor-performance network, with full memory (w/ simulators)
LanguagesDevice language settings: LTR, RTL, Compounding (long words), Latin, Cyrillic, Brahmic, Logographic, Numbers, Special characters
Account required?Accounts/logins: New account, Regular, 2FA, Hcaptcha, Email Code, Other
AccessibilityAccessibility Settings: Voice control, System text size, System contrast, Hearing enhancements, Motion
Error statesNetwork offline, feature offline, crashes
Test overview
OnboardingNew and existing installs onboarding and toasts
Community feedCards, swiping, tapping, overflow
For You feedCards, swiping, tapping, overflow
SettingsCommunity and For You
Happy pathUser journey and navigation
Unhappy pathError states, unexpected user behavior, test while downloading saved articles

Testplan


Release

We are aiming to have an holdout test released by May 25, 2026
On release day,
We will release the app version (XXX), to 50% of users who have automatic upgrades on. For users on the app version, all of them will have access to the new "Home" feed.

  • Holdout group (Control): 100% of users on this version have access to current/older "Explore" Feed experience
  • Release group (Variant): 100% of users on this version have access to updatd/new "Home" Feed experience.

Related Objects

StatusSubtypeAssignedTask
OpenNone
ResolvedTLessa-WMF
ResolvedABorbaWMF
DeclinedSNowick_WMF
DeclinedNone
ResolvedTLessa-WMF
ResolvedFeatureDbrant
Resolvedcooltey
ResolvedWRai-WMF
OpenNone
ResolvedWRai-WMF
Resolvedcooltey
Resolvedcooltey
ResolvedWRai-WMF
Resolvedcooltey
Resolvedcooltey
DuplicateNone
Resolvedcooltey
ResolvedDbrant
OpenNone
ResolvedDbrant
OpenNone
ResolvedNone
Resolvedcooltey
OpenNone
ResolvedDbrant
ResolvedDbrant
OpenDbrant
ResolvedDbrant
ResolvedDbrant
ResolvedDbrant
Resolvedcooltey
ResolvedDbrant
ResolvedWRai-WMF
ResolvedWRai-WMF
OpenNone
OpenWRai-WMF
ResolvedDbrant
ResolvedDbrant
DuplicateSChekfa-WMF
ResolvedWRai-WMF
ResolvedWRai-WMF
ResolvedWRai-WMF
ResolvedWRai-WMF
ResolvedWRai-WMF
ResolvedWRai-WMF
ResolvedWRai-WMF
OpenFeatureNone
Resolvedcooltey
ResolvedWRai-WMF
ResolvedHNordeenWMF
Resolvedcooltey
OpenSChekfa-WMF
ResolvedDbrant
Resolvedcooltey
Resolvedcooltey
ResolvedSNowick_WMF
InvalidNone
InvalidNone
InvalidSNowick_WMF
ResolvedSNowick_WMF
ResolvedSNowick_WMF
OpenSChekfa-WMF
ResolvedWRai-WMF
OpenNone
ResolvedSNowick_WMF
ResolvedDbrant
OpenNone
OpenSChekfa-WMF
ResolvedSNowick_WMF
ResolvedSChekfa-WMF
ResolvedWRai-WMF
ResolvedWRai-WMF
ResolvedSNowick_WMF

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes