Page MenuHomePhabricator
Create Task
Maniphest T133230

First run opt-out experience for hovercards
Closed, DeclinedPublic
Actions

Description

Goal

Let readers know about new feature (hovercards) and provide an opportunity to decide whether to use it or not.

Solution

We ask them after using the hovercards.

How

There are two proposed flows for asking readers if they would like to keep the hovercards.

Flow no 1:

  1. Hovercards are enabled
  2. User sees page previews upon first hover
  3. User sees page previews for subsequent X hovers
  4. User is presented with option to disable
  5. User selects to keep/disable
  6. User preference is kept.

Question - what happens when users switch browsers? Perhaps we should cap the onboarding experience at X weeks, months after page previews are live.

Flow no 2:

  1. Hovercards are enabled
  2. User is presented with a notice in the form of a page preview and prompted to view the preview
  3. User views review
  4. System presents option to enable/disable
  5. User preference is saved.

flows.png (1×3 px, 172 KB)

Mocks

Flow no 1
Nth hovercard use

Desktop HD.png (1×2 px, 1 MB)

on hover-out of first hovercard

Desktop HD Copy 2.png (1×2 px, 847 KB)

Flow no 2

https://dl.dropboxusercontent.com/spa/tuyaic6q75gkcv4/Exports/first-run-flow-2/first-run-flow-2.html

Related Objects
Search...

Event Timeline

• Nirzar created this task.Apr 20 2016, 10:58 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 20 2016, 10:58 PM
• Nirzar added subscribers: • JKatzWMF, dr0ptp4kt.Apr 20 2016, 10:58 PM
• Tbayer subscribed.Apr 20 2016, 11:17 PM
• bmansurov subscribed.Apr 21 2016, 5:17 PM

I assume this is when we push it to stable? Otherwise the user can always disable it in the beta features page.

• Nirzar added a comment.Apr 21 2016, 5:18 PM

@bmansurov that is correct

dr0ptp4kt added a comment.Apr 22 2016, 4:29 PM

What shows after the user taps "Disable it"?

What if the user tapped through on the hovercard instead of dismissing the hovercard?

• bmansurov added a comment.Apr 22 2016, 8:55 PM

Also, how would the user re-enable it?

• Nirzar added a comment.Apr 22 2016, 8:59 PM

@dr0ptp4kt

disable it will disable it and show how to enable it back. I will upload the mocks

What if the user tapped through on the hovercard instead of dismissing the hovercard?

That's a good question. i don't have answer yet.

Also, how would the user re-enable it?

we are working to finalize the design for re-enabling hovercards. https://www.mediawiki.org/wiki/Beta_Feature/Hovercards/preferences

• JKatzWMF added a subscriber: • Moushira.Apr 22 2016, 10:51 PM

@Moushira can you start driving traffic to this page? (VP's and mailing lists?)
https://www.mediawiki.org/wiki/Beta_Feature/Hovercards/preferences

dr0ptp4kt added a parent task: T70860: [GOAL] Graduate Page Previews feature (Popups extension) out of Beta Feature.Apr 26 2016, 5:17 PM
dr0ptp4kt triaged this task as Medium priority.Apr 26 2016, 5:52 PM
• JKatzWMF added a comment.May 17 2016, 4:26 PM

@Moushira ping!

MBinder_WMF added a project: Web-Team-Backlog.May 17 2016, 6:31 PM
• Jhernandez moved this task from Incoming to Triaged but Future on the Web-Team-Backlog board.May 18 2016, 3:34 PM
• Jhernandez mentioned this in T135628: Hovercards overrides NavPopups; should be the other way around.May 18 2016, 5:23 PM
• JKatzWMF mentioned this in T136394: Difference between Hovercards advanced and disabled mode is unclear.Jun 8 2016, 5:09 PM
• Tbayer added a comment.Jul 31 2016, 3:55 AM

According to the data from the A/B test on huwiki (T139319#2467334, T139319#2509065) the settings cog is very rarely clicked (in <0.01% of hovers), which is surely a good argument for such a change.

• Tbayer mentioned this in T139319: Analyze results of Hovercards A/B test - Hungarian.Aug 2 2016, 5:45 PM
• Nirzar added a project: Design.Aug 2 2016, 10:16 PM
MBinder_WMF edited projects, added Page-Previews (2016-17-Q2-Goal); removed Page-Previews.Sep 1 2016, 7:39 PM
MBinder_WMF added a parent task: T140162: Hovercards usability/qualitative study.Sep 1 2016, 7:41 PM
• Nirzar moved this task from Triaged but Future to Design on the Web-Team-Backlog board.Oct 5 2016, 8:04 PM
• Nirzar edited projects, added Web-Team-Backlog (Design); removed Web-Team-Backlog.
• Nirzar moved this task from Needs analysis to Next up on the Web-Team-Backlog (Design) board.
• Nirzar moved this task from Next up to Designing/discussing right now on the Web-Team-Backlog (Design) board.Oct 5 2016, 8:29 PM
ovasileva updated the task description. (Show Details)Oct 6 2016, 1:58 PM
ovasileva subscribed.

@Nirzar - updated workflows based on our conversation yesterday

• Nirzar updated the task description. (Show Details)Oct 6 2016, 4:42 PM
• Nirzar updated the task description. (Show Details)
• Nirzar added a comment.Oct 6 2016, 9:42 PM

@ovasileva https://dl.dropboxusercontent.com/spa/tuyaic6q75gkcv4/Exports/first-run-flow-2/first-run-flow-2.html

here's the flow no2. wanted to show you before I update the description

ovasileva added a comment.Oct 7 2016, 11:17 AM

@Nirzar - looks good. I like both. I think this is a good candidate for testing

• Nirzar added a comment.Oct 8 2016, 10:19 PM

@ovasileva A/B testing or usability testing?

• Nirzar updated the task description. (Show Details)EditedOct 17 2016, 11:10 PM
• Nirzar moved this task from Design to Product Owner Backlog on the Web-Team-Backlog board.
• Nirzar edited projects, added Web-Team-Backlog; removed Web-Team-Backlog (Design).

@ovasileva moving to product manager backlog

ovasileva added a comment.Oct 19 2016, 10:31 AM

@Nirzar - both, but A/B testing would be difficult, so usability testing in particular

ovasileva moved this task from 2016-17-Q2-Goal to Next Up on the Page-Previews board.Dec 19 2016, 7:15 PM
ovasileva edited projects, added Page-Previews; removed Page-Previews (2016-17-Q2-Goal).
ovasileva moved this task to Hovercards Pt2 on the Page-Previews board.Dec 19 2016, 11:16 PM
• Nirzar added a comment.May 6 2017, 12:43 AM

@ovasileva are we still planning on doing this?

ovasileva added a comment.May 8 2017, 9:06 AM

@Nirzar - as we stand right now, I don't think so, but I'd like to keep it open as a reference for once we go into approaching the enwiki community

Jdlrobson edited projects, added Reading-Web-Planning; removed Page-Previews, Web-Team-Backlog, Design.Jun 9 2017, 8:22 PM
Jdlrobson subscribed.

Per https://phabricator.wikimedia.org/T133230#3242955 it feels like we should decline this.

I don't see the point in allowing it to clutter the backlog.

As a suggestion if we don't want to decline this, maybe we should start using Reading-Web-Planning again?
I'll start an email thread.

ovasileva changed the task status from Open to Stalled.Jun 12 2017, 3:25 PM
ovasileva added a project: Page-Previews.

Not a bad idea. However, I would like to have it appear at least on the page previews backlog, if not the overall reading backlog. As it was in the product owner backlog, I don't necessarily see it as clutter - these are the tasks that require product decisions, such as this one. Marking it as stalled for now.

• Mohcinzh011 subscribed.Jun 30 2017, 11:19 PM
This comment was removed by • demon.
• demon subscribed.Jun 30 2017, 11:29 PM
Jdlrobson edited projects, added Web-Team-Backlog; removed Reading-Web-Planning.Oct 9 2017, 5:01 PM

Done, yes?
@Nirzar
@ovasileva

ovasileva added a comment.Oct 10 2017, 11:35 AM
In T133230#3669994, @Jdlrobson wrote:

Done, yes?
@Nirzar
@ovasileva

Still stalled, technically. After we deploy, I think it'd be okay to close, we will most likely not be doing this.

• Nirzar closed this task as Declined.Oct 10 2017, 9:43 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits