Page MenuHomePhabricator

[SPIKE] Determine feasibility of launching Reading Lists on mobile for WE3.3.4 (2 Days)
Closed, ResolvedPublic3 Estimated Story PointsSpike

Description

Background

WE3.3.4 seeks to launch reading lists on web. We still have to answer the open question of whether or not this launch should include mobile web.
Launching on mobile web will have several benefits:

  • A consistent user experience. If someone gets reading lists on desktop, they might be confused as to why the feature isn't available on mobile. Furthermore, they might mistake the watchlist star for the reading list feature.
  • Data comparison between mobile and desktop usage. This information would help us identify usage patterns and make decisions pertaining to the future of this feature.

Open questions

  • How much additional instrumentation work will launching Reading Lists on mobile require
  • Is the current mobile experience for Reading Lists acceptable from a design perspective? (Meet with @Sneha to walk through current mobile experience).
  • Determine whether we need the onboarding experience for mobile described in T400366 for mobile, and if we do, determine the feasibility of implementing that flow.

Outcomes

  • Determine technical feasibility of launching mobile Reading Lists experience alongside the desktop experience for WE3.3.4
  • If it is feasible within our timelines, write any additional tasks that will be needed for instrumentation for mobile.

Event Timeline

Jdrewniak triaged this task as High priority.
LMora-WMF renamed this task from [SPIKE] Determine feasibility of launching Reading Lists on mobile for WE3.3.4 to [SPIKE] Determine feasibility of launching Reading Lists on mobile for WE3.3.4 (2 Days).Sep 9 2025, 5:37 PM
LMora-WMF set the point value for this task to 3.

Had a meeting with @jwang about whether we should launch the reading list on mobile web at the same time as we launch on desktop. Her recommendation is to NOT launch both at the same time, as experimentation best practice should have us look at only one surface at a time. Especially since we are tracking internal clickthrough/referral rates as part of the experiment, the data would be cleaner if we kept it to desktop only.

For that reason, let's move this ticket back to the Backlog. We will consider doing this as a follow up experiment after the desktop finishes, and this gives us more time to consider all the UI elements for mobile.

HFan-WMF claimed this task.

Closing as this is a duplicate of other mobile Reading List tasks that have been further refined.