Page MenuHomePhabricator

Variant C/D: welcome peek drawer on mobile
Closed, ResolvedPublic

Description

From T250440: Variant tests: C-mobile:

  • When the user first arrives on their homepage, they should get a drawer that comes up from the bottom of the screen. When the drawer is open, the rest of the screen is shaded over.
  • Header: "Welcome to your homepage!"
  • Body: "You can learn to edit, contact your mentor, and see the impact of your work. Continue to learn about the suggested edits on your homepage."
  • The drawer is dismissable by tapping outside of it.
  • The user can tap "Continue" at the bottom to open the onboarding.
  • After the user dismisses the drawer or taps continue, they will never see this drawer again.
  • With the advent of this drawer, we should remove the "Welcome to your homepage!" header on the banner that explains to users how to return, implemented in T224883: Homepage: discovery of homepage after account creation (mobile).

From T250451: Variant tests: D-mobile:

  • When the user first arrives on their homepage, they should get a drawer that comes up from the bottom of the screen. When the drawer is open, the rest of the screen is shaded over.
  • Header: "Welcome to your homepage!"
  • Body: "You can learn to edit, contact your mentor, and see the impact of your work."
  • The drawer is dismissable by tapping "Got it" or outside of it
  • After the user dismisses the drawer, they will never see this drawer again.
  • With the advent of this drawer, we should remove the "Welcome to your homepage!" header on the banner that explains to users how to return, implemented in T224883: Homepage: discovery of homepage after account creation (mobile).

Mockups in Zeplin: variant C, variant D

Var C
Var D

Basically, both Variants C-mobile and D-mobile now have a drawer in the same place under the same circumstances (first arrival to page), but the content is different between them. The text differs, and Variant C's has a call-to-action button.

The desktop version of this task is T258009: Variant C/D: welcome popup on desktop, which uses a different form factor, but the same language. We may wish to share a hidden preference for dismissing both of these forms of welcome.

The "dismissed" state should be synchronized between the desktop and mobile versions of this feature. In other words, if the user dismisses the welcome popup on desktop, that should also hide the welcome drawer on any future mobile visits, and vice versa.

Event Timeline

MMiller_WMF renamed this task from Variant C (mobile): welcome peek drawer to Variant C/D: welcome peek drawer on mobile.Jul 22 2020, 8:24 PM
MMiller_WMF updated the task description. (Show Details)

The user can tap "Continue" at the bottom to open the onboarding.

@RHo should it be "Continue" or "Learn more" as Zeplin shows?

"Continue to learn about the suggested edits on your homepage."

Should it be "the suggested edits" or just "suggested edits"?

Change 627774 had a related patch set uploaded (by Kosta Harlan; owner: Kosta Harlan):
[mediawiki/extensions/GrowthExperiments@master] Homepage: Don't show welcome notice for variant C/D users

https://gerrit.wikimedia.org/r/627774

Change 627775 had a related patch set uploaded (by Kosta Harlan; owner: Kosta Harlan):
[mediawiki/extensions/GrowthExperiments@master] Homepage: Add hook for when mobile homepage summary HTML is loaded

https://gerrit.wikimedia.org/r/627775

Change 627776 had a related patch set uploaded (by Kosta Harlan; owner: Kosta Harlan):
[mediawiki/extensions/GrowthExperiments@master] [WIP] Homepage: Show welcome drawer to variation C/D users

https://gerrit.wikimedia.org/r/627776

hi @kostajh - I must have missed this "Continue" call to action copy change, I've updated so all Zeplin copy should fit what is in the task description now.

The user can tap "Continue" at the bottom to open the onboarding.

@RHo should it be "Continue" or "Learn more" as Zeplin shows?

Updated Zeplin to "Continue"

"Continue to learn about the suggested edits on your homepage."

Should it be "the suggested edits" or just "suggested edits"?

I'm guessing "the suggested edits" because we are referring to them as items to do rather than as the capital "F" Feature. @MMiller_WMF, please confirm if that's right?

Cool. One more question, "Continue" and "Got it" seem quite similar; should we think about using just one of those so as to have one less string that needs translation?

Cool. One more question, "Continue" and "Got it" seem quite similar; should we think about using just one of those so as to have one less string that needs translation?

So with this one i feel like it is important to have two separate strings because the intention is a little different. "Continue" brings up more onboarding info, whereas "Got it" is meant to convey the end (as in "message received"). Which actually makes me re-think whether we should change the button to "Learn more" since that may be more explicit for the user. Thoughts, @MMiller_WMF ?

I'm guessing "the suggested edits" because we are referring to them as items to do rather than as the capital "F" Feature. @MMiller_WMF, please confirm if that's right?

That's right. It should be "the suggested edits".

So with this one i feel like it is important to have two separate strings because the intention is a little different. "Continue" brings up more onboarding info, whereas "Got it" is meant to convey the end (as in "message received"). Which actually makes me re-think whether we should change the button to "Learn more" since that may be more explicit for the user. Thoughts, @MMiller_WMF ?

@RHo -- I think it is appropriate to be careful and nuanced with the wording here. I think you should set it to what you think is right for the different cases.

After the user dismisses the drawer or taps continue, they will never see this drawer again.

@RHo @MMiller_WMF to clarify this, if the user reloads the page (or closes the browser tab and comes back to Special:Homepage), they should see the drawer again, correct? In other words some form of interaction (tapping on the drawer, Continue, or outside of the drawer) is required before we decide to never show it again?

Change 627774 merged by jenkins-bot:
[mediawiki/extensions/GrowthExperiments@master] Homepage: Don't show welcome notice for variant C/D users

https://gerrit.wikimedia.org/r/627774

Change 627775 merged by jenkins-bot:
[mediawiki/extensions/GrowthExperiments@master] Homepage: Add hook for when mobile homepage summary HTML is loaded

https://gerrit.wikimedia.org/r/627775

After the user dismisses the drawer or taps continue, they will never see this drawer again.

@RHo @MMiller_WMF to clarify this, if the user reloads the page (or closes the browser tab and comes back to Special:Homepage), they should see the drawer again, correct? In other words some form of interaction (tapping on the drawer, Continue, or outside of the drawer) is required before we decide to never show it again?

Also, noting that the text in phab has a period at the end of both second sentences, while the mockups do not. I've added periods to the end of both sentences in the patch, hopefully this is correct

@kostajh -- yes, we only want to disappear the drawer if they do an action that dismisses it. Viewing it once does not count as one of those actions.

And yes, I prefer to have periods at the ends of the sentences.

Change 627776 merged by jenkins-bot:
[mediawiki/extensions/GrowthExperiments@master] Homepage: Show welcome drawer to variation C/D users

https://gerrit.wikimedia.org/r/627776

Etonkovidova added a subscriber: Etonkovidova.

For Design review.
@RHo - if I understood correctly the following spec - it means that there won't be the banner with the arrow (on the screenshots and on the mockups it's still present).

With the advent of this drawer, we should remove the "Welcome to your homepage!" header on the banner that explains to users how to return

Variant CVariant D

@Etonkovidova -- about that banner with the arrow: I think I may have made a mistake in the specifications. We will still want that banner with arrow, but only in the case when the user arrives on the homepage after clicking the call-to-action from the Welcome Survey. As a baseline, can you please check these things in production (we want both to be true):

  • If the first time the user goes to their homepage is from the call-to-action after the welcome survey, they get the banner with the arrow.
  • If the first time the user goes to their homepage is by navigating there through the side menu, they get no banner.

If that's all good, then yes, we still want the banner with the arrow to display in that first scenario, and I can send this back to "Needs More Work" to fix that.

@Etonkovidova -- about that banner with the arrow: I think I may have made a mistake in the specifications. We will still want that banner with arrow, but only in the case when the user arrives on the homepage after clicking the call-to-action from the Welcome Survey. As a baseline, can you please check these things in production (we want both to be true):

  • If the first time the user goes to their homepage is from the call-to-action after the welcome survey, they get the banner with the arrow.
  • If the first time the user goes to their homepage is by navigating there through the side menu, they get no banner.

If that's all good, then yes, we still want the banner with the arrow to display in that first scenario, and I can send this back to "Needs More Work" to fix that.

Checked on cswiki wmf.10 - the banner (and the arrow) appears for users who come from the call-to-action after welcome survey. So, the production behaves as expected.

The question remains: variants C and D - should they have the banner and the arrow? I could not see it when testing on beta.
The steps:

  • a new user fills out the Welcome survey and submits
  • sees "Go to your homepage" button and clicks on it
  • sees the peek drawer on the Homepage but not the banner with the arrow.

With the advent of this drawer, we should remove the "Welcome to your homepage!" header on the banner that explains to users how to return

That was implemented in 354a6a920ad2a0480a748f5780c9c9cff283a6a3, I'll partially revert that and fix this to show for variants C and D when arriving via welcome survey.

Change 630564 had a related patch set uploaded (by Kosta Harlan; owner: Kosta Harlan):
[mediawiki/extensions/GrowthExperiments@master] [WIP] Homepage: Show discovery banner with variant specific arrows

https://gerrit.wikimedia.org/r/630564

Change 630564 merged by jenkins-bot:
[mediawiki/extensions/GrowthExperiments@master] Homepage: Show discovery banner with variant specific arrows

https://gerrit.wikimedia.org/r/630564

The banner is back on both variants.

variant Cvariant D

Great thanks!

The banner is back on both variants.

variant Cvariant D

@Etonkovidova -- about that banner with the arrow: I think I may have made a mistake in the specifications. We will still want that banner with arrow, but only in the case when the user arrives on the homepage after clicking the call-to-action from the Welcome Survey.

FWIW in variant C this seems somewhat pointless, since initially it will be obscured by the welcome drawer, closing the drawer will open onboarding, and closing onboarding will take the user to the suggested edits module, so they won't really see the notice.

@Etonkovidova -- about that banner with the arrow: I think I may have made a mistake in the specifications. We will still want that banner with arrow, but only in the case when the user arrives on the homepage after clicking the call-to-action from the Welcome Survey.

FWIW in variant C this seems somewhat pointless, since initially it will be obscured by the welcome drawer, closing the drawer will open onboarding, and closing onboarding will take the user to the suggested edits module, so they won't really see the notice.

While definitely not as helpful, I do think it has some benefit since the notice (with the big arrow) is still visible under the 50% opacity layer under the peek. And presumably the reminder will still be shown (until dismissed) if the user either exits out of the welcome peek or navigates back from the SE module to the homepage?

In general though, I would be in favour of other options besides this banner for homepage discovery, as detailed under T220552: [EPIC] Growth: features to aid homepage discovery.

And presumably the reminder will still be shown (until dismissed) if the user either exits out of the welcome peek or navigates back from the SE module to the homepage?

You are right, I forgot the notice sticks around until dismissed.

This looks good to me in beta. To be resolved once in production.