Page MenuHomePhabricator

Create new tab experience that has empty state on first launch (Group C)
Closed, ResolvedPublic3 Estimated Story Points

Description

Background

After the release of Tabs V1, we are testing improvements to the New tab experience with V2 (More dynamic tabs)

Requirements
  • User clicks tabs icon in top right and is brought to tab overview
  • If user does not have active tabs they should see
    • Empty state with text and illustration
    • Module at the bottom of the tabs overview that shows Did You Know content (to be built in T404795)
    • Overflow menu in the top right that allows users to close recommendations or close all tabs (to be built in T398883)
  • State logic (tab count)
    • Define tab count as number of open article tabs excluding the Main Page tab.
      • If tab count < 2 → show “Did You Know” (DYK) module.
      • If tab count ≥ 2 → show “Because you read …” module.
  • When user clicks + sign to open a new tab they should be brought to the Main page with an inactive search
  • Upon clicking an article recommendation, the article should open a new tab (to be build in T404795)
  • Allow people to long-press on article recommendations for a preview (same as in Explore)
Designs

https://www.figma.com/design/5gHmEo8IIFxlPfYM6bppzz/iOS---%3E-More-Dynamic-Tabs?node-id=1576-10626&t=6kyskTf5VKmmMbFS-1

Engineering notes
  • Will use one of our newer components for the empty state, design might be slightly different.

QA Notes

Test in TestFlight Wikipedia build 7.8.4 (latest).
Developer Settings toggle for forcing: "Enable tabs V2 with group {letter}"

Note developer settings toggle will not work the best for testing initial tabs overview state. For a more "pure" test see QA Notes in https://phabricator.wikimedia.org/T398878.

Event Timeline

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

Looks good on 7.8.1 (5741)

Tested on iPhone on iOS 26.0 and iPad on iPadOS 18.5. Tested on all themes and all three languages

JTannerWMF renamed this task from Create “Did you know” view. to Create new tab experience that has empty state on first launch (Group C).Sep 15 2025, 9:41 PM
JTannerWMF removed GOlson-WMF as the assignee of this task.
JTannerWMF updated the task description. (Show Details)
JTannerWMF removed the point value 5 for this task.
JTannerWMF added a subscriber: GOlson-WMF.
JTannerWMF subscribed.

I've updated this task with the new requirements

Tsevener set the point value for this task to 3.

@JTannerWMF For this one and T398888, some new logic is to outline the current tab in a gray border. We couldn't find that requirement on V2 tasks. If it's missing can you add it to this task and T398888?

Screenshot 2025-09-18 at 9.58.57 AM.png (883×420 px, 110 KB)

Please design review on Staging 7.8.4 (109).

Update:

Please design review on Staging 7.8.4 (111)

This build temporarily forces Group C assignment upon app launch, which will be closer to a true test of the initial app state for Group C users without having to toggle developer settings. Please change your device region to a target region (I use Germany in my testing) before launching for the first time.

SChekfa-WMF subscribed.

@Tsevener @Mazevedo

thank you! some notes for improvement:

  1. please ensure that the empty state background color of tabs overview is set to #gray100, per the designs. as it currently stands:

image.png (2×1 px, 152 KB)

  1. I am seeing recommendations when there are 2 active tabs. the requirements state that recommendations should only populate if a user has more than two active tabs:

Screenshot 2025-10-09 at 14.50.21.png (2×1 px, 538 KB)

  1. there is a delay in populating the recommendations when I have two active tabs — can this be minimized? this is what i'm seeing
  2. per conversation in Slack, Tais confirmed that recommendations/DYK should never change while user is in tabs overview, even if an article is closed/opened while in tabs overview, causing the user to go over/beneath the threshold of 2 articles. change is only permitted upon reentry into tabs overview.

@SChekfa-WMF

Just responding to a couple of your comments for documentation purposes:

I am seeing recommendations when there are 2 active tabs. the requirements state that recommendations should only populate if a user has more than two active tabs:

It was decided that we'll see recommendations for 2 or more non-Main tabs (requirements have been updated).

per conversation in Slack, Tais confirmed that recommendations/DYK should never change while user is in tabs overview, even if an article is closed/opened while in tabs overview, causing the user to go over/beneath the threshold of 2 articles. change is only permitted upon reentry into tabs overview.

We will follow the requirements listed in https://phabricator.wikimedia.org/T404795:

Live-update back to DYK if someone closes out all tabs / all except 1 non-mainpage tab
Do not live-update with new recommendations if someone close out articles that were the seeds of their recommendations, but still has 2+ non-main page tabs tabs open

Group B: Staging 115
Group C: Staging 116

Appears to be fixed on 7.8.4 (5853)

Tested on iPhone 16 on iOS 26, iPad 12.9 on iPadOS 26, and iPhone 11 on iOS 18. Tested on all themes