Page MenuHomePhabricator

[L] Show Semantic Results Above Lexical Results for Hybrid Search C Group [NICE-TO-HAVE]
Open, LowPublic8 Estimated Story Points

Description

User Story

As a reader in a Hybrid Search experiment variant, I want to see meaning-based results before traditional article results, so that I can explore whether semantic retrieval helps me find relevant information faster.

Description

Introduce a C-group layout variant for the Hybrid Search experiment where semantic results are presented above lexical results on the search results page.

This variant exists solely to test whether result positioning influences engagement, trust, or perceived relevance, independent of retrieval quality.

The control (A) and primary experiment (B) groups remain unchanged.

Requirements

Semantic Results (Top Section – C Group Only)

  • The top of the results page displays a clearly labeled semantic results section
  • Section contains up to 3 semantic results
  • Results are rendered as section-level excerpts returned from semantic retrieval embeddings
  • Results are presented in a horizontal, scrollable list
  • Each semantic result includes:
    • Article title
    • Excerpt text
    • Provenance indicator (article and section, when available)
  • Tapping a semantic result navigates to the relevant article section

Lexical Results (Secondary Section)

  • Lexical results appear below the semantic section
  • Display up to 3 lexical results
  • Presented in a vertical list
  • Each result includes:
    • Article title
    • Thumbnail image when available
  • Tapping a lexical result navigates to the article page

General Behavior

  • Layout applies only to the Hybrid Search C group
  • A and B groups retain their respective layouts
  • Semantic and lexical sections remain visually distinct
  • No interleaving of results across sections

Notes:

  • This task is explicitly designed to test positioning bias, not to propose a default UX
  • Semantic results must be clearly labeled to avoid confusion or trust erosion
  • Any negative trust or performance signals should be treated as stop signals for this layout

Design:

Figma mockup

Note: When semantic search is displayed before keyword search, we should restrict the deep search cards to 8-9 lines max, so both are visible in smaller screens without scrolling.


Copy and Translations: TBA

Event Timeline

TLessa-WMF updated the task description. (Show Details)
TLessa-WMF updated the task description. (Show Details)
JTannerWMF renamed this task from Show Semantic Results Above Lexical Results for Hybrid Search C Group [NICE-TO-HAVE] to [L] Show Semantic Results Above Lexical Results for Hybrid Search C Group [NICE-TO-HAVE].Jan 6 2026, 10:01 PM

For testing purposes:

Go to Developer Settings -> Go to the bottom of the page or search for Hybrid Search test group -> change the number to 2 to become a member of group c

Hi @TLessa-WMF

This is ready for review, please go to the feature branch
https://github.com/wikimedia/apps-android-wikipedia/pull/6221

Steps to download the APK
Click on "Checks" -> find "Android branch build" -> scroll down and find "Artifacts" -> Download the "app_alpha_release" file

How to test

  1. Make sure you are in the test group 2
  2. You can go to Developer Settings -> make sure "Hybrid Search test group" is 2
  3. hybridSearchOnboardingShown and hybridSearchEnabled are on.
  4. Make sure you have the eligible app languages selected: en, fr, pt

Note: When semantic search is displayed before keyword search, we should restrict the deep search cards to 8-9 lines max, so both are visible in smaller screens without scrolling.

@TLessa-WMF If we change the presentation for the B vs C group, wouldn't that influence the experiment? Can we keep the semantic cards exactly the same in both cases?

@Dbrant, yes good point. That applies to both variants.

Design QA here: https://docs.google.com/spreadsheets/d/1bdtOy8M_FxsCDx5vvH7sGmOnETtt2exa3cjKkElO-B4/edit?usp=sharing

Note: the P0s are part of the QA, I will create tickets for the P1s. Let me know if I should be doing this differently, please.

Issues:

  • After the search is completed and the results are displayed, we still show the keyboard on screen. Is there a way to hide the keyboard at this step? Note: this adjustment also applies to the other variant.
  • Keyword search shuffles when cards are scrolled horizontally. Note: When we decide on the Fixed height for the cards, this issue will be resolved.
  • Semantic search cards don't touch the edges of the screen Note: this adjustment also applies to the other variant.
  • The cards have too little information to satisfy information needs in the card view. Current 6 lines. Note: this adjustment also applies to the other variant.
  • Semantic search it not being trigered when user taps "enter" on keyboard. When I tap "enter", the keyboard disappears instead of triggering search. Note: this adjustment also applies to the other variant.
  • Remove "x results from x articles"

{F71694219}