Closed
Bug 1221338
Opened 10 years ago
Closed 8 years ago
A/B/C Test Android Page Based on User Feedback (Send to device)
Categories
(www.mozilla.org :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adavis, Assigned: jpetto)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [kb=1889239] [FXGrowth])
User Story
We recently ran 3 different variations of the Android product page up against each other. (see linked mana page for details) We will be deploying the winner in Bug 1221328 . However, we received a lot of valuable user feedback during our test and would like to try to improve the winner in a new test. Changes to implement for variation B: -Add the following below the form: "You will only receive your Google Play Store link." or “You will only receive a one-time message.” -Change CTA on Button to: "Send me a Google Play Store link" [Require Review from Matej] Changes to implement for variation C: -Same as version B -Add GP logo / branding (not a button) :Habber will make design suggestions for both B and C Link to our meeting notes around these tests: https://docs.google.com/document/d/1DNZ_VywMqnB33mbUk9hlLIC6RnKG_ealuODhE7zcVRM/edit
No description provided.
Comment 1•10 years ago
|
||
Hi Jon-
Do you have bandwidth to help out with this one?
Thx,
Jen
Flags: needinfo?(jon)
Updated•10 years ago
|
Whiteboard: [FXGrowth] → [kb=1889239] [FXGrowth]
| Assignee | ||
Comment 2•10 years ago
|
||
Yep, I can take this on.
To clarify:
- The old/current variation b [1] will be the new default (as stated in bug 1221328)
- There will be a new round of testing that will have 2 variations:
1. Alter messaging/copy on the embedded send to device widget (the new default)
2. Hide the embedded send to device widget and only show Google Play button
I'm a bit confused on #2 above. The user story says:
> Changes to implement for variation C:
> -Add GP logo
Variation C [2] has the Google Play button with logo. What exactly should be changed? Add another Google Play logo somewhere?
How far away are we from this bug being ready to go? I'm pretty close to finishing bug 1221328, but I can wait and do these in tandem if that's more efficient.
[1] https://www.mozilla.org/en-US/firefox/android/?v=b
[2] https://www.mozilla.org/en-US/firefox/android/?v=c
Flags: needinfo?(jon)
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jon
| Reporter | ||
Updated•10 years ago
|
User Story: (updated)
| Reporter | ||
Comment 3•10 years ago
|
||
(In reply to Jon Petto [:jpetto] from comment #2)
> Yep, I can take this on.
>
> To clarify:
>
> - The old/current variation b [1] will be the new default (as stated in bug
> 1221328)
>
> - There will be a new round of testing that will have 2 variations:
>
> 1. Alter messaging/copy on the embedded send to device widget (the new
> default)
>
> 2. Hide the embedded send to device widget and only show Google Play
> button
>
> I'm a bit confused on #2 above. The user story says:
>
> > Changes to implement for variation C:
> > -Add GP logo
>
> Variation C [2] has the Google Play button with logo. What exactly should be
> changed? Add another Google Play logo somewhere?
>
> How far away are we from this bug being ready to go? I'm pretty close to
> finishing bug 1221328, but I can wait and do these in tandem if that's more
> efficient.
>
> [1] https://www.mozilla.org/en-US/firefox/android/?v=b
> [2] https://www.mozilla.org/en-US/firefox/android/?v=c
I clarified the story a bit. Version C is nearly identical to version B but we will add some Google Play branding (likely the logo) to version C. To my knowledge it won't be a button.
Our 2 take-aways from the last test was the we needed to improve copy (version B) and that users feel comforted (or have more trust) when they see the Google Play branding. (version C)
Holly should be doing mockups or wireframes for these.
| Assignee | ||
Comment 4•10 years ago
|
||
Ah, okay. We're talking about a new version C, not based on the current version C. Got it.
| Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•