Page MenuHomePhabricator

Mobile should separate out Saved reading list and editor Watchlist experiences.
Open, MediumPublic

Description

Background

Many years ago, the mobile site added the Watchlist feature. Presumably, due to the use of a star, many readers interpreted this as "favorite" an article and we saw large amounts of logged in users who were not editing but were creating reading lists. As a result the watchlist experience on mobile has always been a bit confusing catering both to an editing and reading audience.

Since then, the mobile watchlist code has effectively become unmaintained. We have accummulated a large amount of technical and design debt in our backlog to address, for example: T266065, T115013
If this continues, there is an increasing risk we will need to one day disable the feature without any action.

It is proposed we link to the reading list version of the watchlist and remove all MobileFrontend code.

Extension:ReadingList which is built in Vue.js provides a modern equivalent of the mobile watchlist feature:
See for example https://en.m.wikipedia.org/wiki/Special:ReadingLists/<your username>/-10

On the long term, strategically this provides us an entry point to exposing the reading list feature already on apps.

Existing unmaintained EditWatchlist experienceNew proposed reading list extension based experience
Screenshot 2024-05-24 at 9.46.49 AM.png (2,048×1,698 px, 407 KB)
Screenshot 2024-05-24 at 9.47.08 AM.png (2,026×1,706 px, 341 KB)

User story

  • As an editor who patrols Wikipedia I want easy access to my watchlist feed showing me recent edits
  • As an logged in user who keeps lists of articles I care about I want a list of my saved pages.

Requirements

  • The MobileFrontend Watchlist code is decomissioned.
  • The desktop watchlist is used on mobile, just as we use desktop code for history, contributions and recent changes.
  • Change is made in the ReadingList extension. Updates are made to MobileFrontend to ensure the link shows in the correct places.
  • Reading lists that a user has saved other than "Watchlist" are disabled (this is already handled by Extension:ReadingList)

Design

AMC disabled:

Screenshot 2024-04-16 at 4.06.51 PM.png (1,216×1,016 px, 146 KB)

Screenshot 2024-04-16 at 4.00.20 PM.png (2,074×1,662 px, 230 KB)

AMC:
Screenshot 2024-04-19 at 4.37.56 PM.png (394×722 px, 35 KB)

Acceptance criteria

  • The mobile menu links to "Watchlist" and "Saved"
  • When clicking Saved I am taken to the Special:ReadingList/<username>/-10/Watchlist page.
  • When clicking Watchlist I am taken to Special:Watchlist

Event Timeline

ovasileva triaged this task as Medium priority.Apr 25 2024, 2:37 PM
ovasileva moved this task from Incoming to Groomed on the Web-Team-Backlog-Archived board.

Circling back to this as this is a blocker for full roll out on mobile given we have lots of engaged users using the watchlist as a reading list.

I think the easiest way to handle these users is to add a tab "export" that exports to a reading list.

The current experience is this:

Screenshot 2025-12-10 at 5.32.37 PM.png (1,029×395 px, 49 KB)

After removal that page it would look like this:

Screenshot 2025-12-10 at 5.33.48 PM.png (1,033×755 px, 93 KB)

or this:
Screenshot 2025-12-10 at 5.34.19 PM.png (1,027×776 px, 101 KB)

We could add a tab to those pages

Screenshot 2025-12-10 at 5.34.53 PM.png (1,025×787 px, 102 KB)

or a message box at top of page
Screenshot 2025-12-10 at 5.36.23 PM.png (1,021×442 px, 60 KB)

When clicked it would open this dialog:

Screenshot 2025-12-10 at 5.30.41 PM.png (1,568×444 px, 74 KB)

And after hitting the button you'd be redirected to:

Screenshot 2025-12-10 at 5.39.24 PM.png (1,038×586 px, 121 KB)

This could also become a useful tool for editors who may have benefits (and want to go in the other direction in future)

Thanks so much for raising this, Jon! I'm liking both approaches, but I'm wondering: if we use the terminology "as reading list" in the tab or "where your reading list went" in the banner, are these users already familiar with the concept of reading list already? in the existing mobile watchlist, I don't really see "reading list" verbiage used anywhere.

I think a one time exporting of the watchlist to reading list default list would be a fine idea; but wondering how much engineering work that might entail? I don't think it's a throwaway work, since this functionality may become useful again in the future as you said for users who want to add items from one list to the other, but just wanted to gauge what the tech investment might look like.

I'll ping this as a task for Sneha to check out when she's back for 2 days early next week, to get some design input.

Per conversation, we'll not invest much time here (discussed with @Sneha and @HFan-WMF) We are assuming that the people who want reading lists on mobile are going to be happy enough to have them available, that they won't immediately be annoyed at having past items that aren't in the new reading lists feature.

Two options, with sequencing which might look like..

With banner:

  • Add a banner to the Special:EditWatchlist pointing users to reading lists beta feature.
  • Change watchlist link in menu to point to editor view to show that we are deprioritizing the "reading" view.
  • Drop the watchlist card view altogether.

Without banner:

  • Ship reading list feature to all users
  • Change watchlist link in menu to point to editor view to show that we are deprioritizing the "reading" view and help train them to use reading list
  • Drop the watchlist card view if no complaints after say 1 month