Background

The current Explore Feed settings entry point (Profile > Settings > Explore Feed) leads users into a combined module list and language configuration flow that conflates feed customization with app-level language settings on iOS. On Android and iOS users have the ability to hide all cards and essentially turn off the explore feed. As part of the new For You feed redesign, the Explore Feed settings screen is being restructured to reflect the two-tab feed (For You / From the Community) and to introduce a new 'What's driving your feed' entry point. Additionally, users will have the ability to hide modules but not shut off the feed completely.

The top-level Explore Feed settings screen will present 2 main options

1. Community— leads to separate module management screen for community.
2. For you — leads to separate module management screen for For you
3. What's driving your feed — leads to a screen explaining and managing personalization signals in For You

The existing screens (the Customize Explore Feed module list and the language toggle list on iOS) are replaced by the new flows defined in this task and its siblings. The entry point from Settings remains unchanged, just a naming update: Settings → Home Feed.

[iOS Specific] Additionally, language settings are being unified. There will no longer be a separate language configuration for the app and for the Explore feed. The Wikipedia Languages screen (accessible via the What's driving your feed flow) serves as the single source of truth for language preferences.

User Story

As a Wikipedia reader, I want the Home Feed settings screen to clearly reflect the two-tab feed structure and give me an easy way to manage both my modules and what's personalizing my feed, so that I can quickly find the right control without wading through a combined list of unrelated options.

Requirements

• The Home Feed settings screen is accessed from Settings → Home feed
• The top-level screen displays two sections: FOR YOU and COMMUNITY.
• Under FOR YOU: a 'Modules' row (subtitle: 'Turn on or off "For you" feed modules') and a 'What's driving your feed' row (subtitle: 'Topics and articles shaping your content').
• Under COMMUNITY: a 'Modules' row (subtitle: 'Turn on or off "Community" feed modules').
• Each row indicates it is tappable and leads to a sub-screen.
• Tapping 'For You – Modules' navigates to the For You Modules screen with each module listed with a radio button for it to turn off or on (built on separate task)
• Tapping 'What's driving your feed' navigates to the What's Driving Your Feed screen (built on separate task)
• Tapping 'Community – Modules' navigates to the Community Modules screen (built on separate task)
• The existing Customize Explore Feed screen is retired and replaced by the new sub-screens.
• There is no longer a separate Explore feed language setting; language is managed exclusively through the Wikipedia Languages screen accessed via What's driving your feed.
• Remove ability to turn off Explore tab. For anyone who has this setting currently enabled, they will now default to seeing the Home Feed.

Design

Figma file (this screen) →
Figma file (complete flow for reference) →

Android task for reference: https://phabricator.wikimedia.org/T419761

Toni Handoff Notes

Based on progress at PR https://github.com/wikimedia/wikipedia-ios/pull/5995

Most of this task is complete but we should double-check these two requirements:

There is no longer a separate Explore feed language setting; language is managed exclusively through the Wikipedia Languages screen accessed via What's driving your feed.

Unclear to me if the Explore language picker is a separate choice from the primary app language. Our current progress saves it as if it is separate. Currently a user could choose Spanish Explore language and Explore shows Spanish content, but primary app language remains in English.

Remove ability to turn off Explore tab. For anyone who has this setting currently enabled, they will now default to seeing the Home Feed.

I guess this is done? Since we rewrote the home settings view, we didn't add the disable toggle. We should add a cleanup task to remove the disable toggle code once the A/B test is complete and we are out at 100%.