As part of T397532, we want to limit the initial reading list experiment to a subset of logged-in users in order to avoid complex UI & workflow considerations.
We only want to show the new Reading List UI to users who:
- Are logged-in
- Have zero watchlist items
- Have zero existing reading lists (from mobile apps)
- Have zero edits
Additionally, we don't want user experience to change mid-way through the experiment, if one of these parameters change. Therefore, we want to use these parameters to set a hidden user preference (or other persistent DB flag) for the user that will maintain their ability to be enrolled in the experiment, as well as maintain their reading list functionality after the experiment is over.
User story
As a logged-in reader, I want to the ability to save articles, and I don't want that functionality to disappear after an arbitrary amount of time.
Requirements
We want to create a new hidden user preference (or other persistent DB flag) that will be set to true under the following conditions
- The user is logged-in
- The user has zero watchlist items
- The user has zero existing reading list items
- The user has zero edits
When this preference is true, we want users to see the new Reading List feature.
Acceptance criteria
- Only users with the criteria mentioned above can initially see the new reading list feature.
- After making an edit, users who initially saw the reading list feature will continue to see it.
- After adding items to their watchlist, users will continue to see the reading list feature
- After adding items to their reading list on mobile apps, users will continue to see the reading list feature.
BDD
- For QA engineer to fill out.
Test Steps
- For QA engineer to fill out.
Communication criteria
Add if this needs an announcement or discussion.
Rollback plan
Describe the rollback plan in production for this task if something goes wrong.
This task was created by Version 1.0.0 of the Reader Experience team task template using phabulous.