Background

We want to experiment with showing a logged out user on mobile web the "save article" functionality and see if this will be more likely to encourage them to create an account compared to the control. In this A/B experiment, the treatment group user will see a bookmark icon instead of the "watch star" icon.

For the first time the user sees this bookmark icon, we will use a pulsating blue dot (codex component) to draw their attention to it. After the user taps the icon at least once, the blue dot will no longer show for the user who has this EdgeUnique cookie.

When tapped, the bookmark button will open a dialog that explains that they will need to be logged into a Wikipedia account in order to save the article. The dialog in treatment will have "create account" as the primary action, and "log in" to existing account as the secondary action.

Tapping on Create Account will take the user to the existing account creation flow. After successful sign-up, we will skip the post-account creation survey and bring the user back to the article page where they launched the flow from. The page will not automatically be saved, and after user taps it again to save the article, we show them the same success toast as usual.

Tapping on Log in will take the user to the existing login flow. After successfully logging in, they are brought back to the article page. The page will not be automatically saved to their reading list.

User story

For a user who is in the treatment group:
As a logged out user reading an article on mobile web, I am bucketed into the treatment group of the A/B test. I see a bookmark button instead of the normal "watch star" button at the top of the article, with a pulsating blue dot indicating to me that it's new.

I tap on the bookmark icon, and a dialog opens explaining that to save this article for revisiting, I need to be logged in.

1. As a brand new user who doesn't have an account, I choose to create a new account and finish the standard account creation flow. I am taken back to the article. The article is not automatically saved, and we skip the onboarding popovers pointing to the bookmark button.

2. As a user who uses the "log in" button to go into my existing account through the bookmark button, I am automatically opted into the Reading List beta, I see the bookmark button (and the page is not automatically saved). We show a popover pointing to overflow menu button to let these previously existing users know where the watchstar button has moved.

For a user in the control group, or who is not bucketed into the experiment at all:

I will see the watchstar button on the article as usual, and tapping on it will give me the choice to login (primary CTA) or sign up (secondary).

1. If I choose to log into my existing account, nothing changes. (User is not opted into the Reading List beta, they do not see the bookmark icon anywhere). Existing watchstar behavior applies (where the article becomes automatically watched)

2. If I choose to sign up for a new account through the watchstar, I am EXEMPTED from the rule that opts newly created accounts into the Reading List beta. I do not see the bookmark icon anywhere. Existing watchstar behavior applies (where the article becomes automatically watched).

Design requirements

Figma file

---

Requirements

Acceptance criteria

• As a logged out user who is in the treatment group of the experiment, I see the bookmark button at the top when I navigate to an article on mobile web. (This replaces the watch star button)
• If I have never clicked on the bookmark icon previously, there is a pulsating blue dot drawing my attention to the bookmark
• After tapping the icon at least once to open the dialog and dismissing it, the pulsating dot will not show again on this article or any other article.
• Tapping the bookmark opens up a dialog that allows for account creation or login
• Tapping on account creation takes me to standard account creation form
• Successful completion of the account creation form will automatically skip the optional newcomer survey and takes me back to the original article where I tapped the bookmark icon. This article is NOT automatically saved to my reading list, and the onboarding popover for the bookmark is skipped. But if I tap the bookmark again, the same toast that indicates article save success appears.
• Tapping on log in triggers the existing login flow. Successful completion of the log in flow takes me back to the same article, and my account is now opted into the Reading List beta. On the article page, I see the bookmark icon (with no onboarding tour), and a popover indicating where the new "Watchstar" location is.
• As a user who is in the control bucket or not bucketed into an experiment at all, I see a watchstar on the article on mobile web.
• Tapping on it opens a dialog to login or signup for new account.
• Signing into an existing account will NOT opt user into reading list beta. The user is returned to the article page with the page automatically watched.
• Creating a new account through watchstar will NOT opt users into reading list beta (an exception to new user creation rule). User will not see bookmark icon anywhere on the article, which should now be watched by the user.

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.