Page MenuHomePhabricator

Investigate creating mocks for UI component of this A/B test
Closed, DeclinedPublic

Description

Let's chat about if we need to do mocks / or have a UI component to how we want this A/B test to be run.

Event Timeline

debt created this task.Aug 10 2016, 4:12 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 10 2016, 4:12 PM

By default we could use the same cross-wiki UI we did for the other language ID A/B tests. It's not great, but it is the same set up, so we'd be comparing apples to apples. OTOH, a better UI might mean more people understand it and get value out of it. I don't have any strong opinions about the UI, though a clearer separation between the local results and cross-wiki results could help. (I think someone else mentioned that on another ticket.)

debt added a comment.Aug 10 2016, 9:50 PM

@TJones do we have a sample of that cross-wiki UI that was done previously...? Before I start to scour through old pages...

The original mockups I did were based on the A/B test UI. They weren't intended as UI examples, but rather as possible kinds of information to show. People weren't understanding the descriptions as well as I'd hoped, so I added pictures. :)

The current cross-wiki results are pretty much the same, too.

debt added a comment.Aug 10 2016, 10:38 PM

Gotcha....! Maybe we can do an A/B/C test where the C test can be a nicer presentation of the results.

mpopov added a subscriber: mpopov.Aug 11 2016, 12:00 AM
debt closed this task as Declined.Nov 2 2016, 1:28 PM

Declining this as we probably don't need an A/B test for these results, plus textcat is working really well otherwise. :)