feat(docs): Add FxA-51 "Connect another device" doc. #210
Conversation
shane-tomlinson
force-pushed the
fxa-51-connect-another-device
branch
from
4e14b0a
to
ec7bb5e
|
|
||
| * Date: November 10th, 2016 | ||
| * Document prepared by: Alex Davis | ||
| * Start date of test: |
vladikoff
Dec 16, 2016
Contributor
I guess this could hopefully be "~ January 1st, 2017"
I guess this could hopefully be "~ January 1st, 2017"
shane-tomlinson
Dec 20, 2016
Author
Member
If the plan is to cut train-76 on ~ Jan 3rd, this will go into prod the week of Jan 9th. I'll say that.
If the plan is to cut train-76 on ~ Jan 3rd, this will go into prod the week of Jan 9th. I'll say that.
| The outcome we are looking for is a slick user flow that makes it obvious to users that in order to complete their setup of Sync, they need to add another device after email confirmation. | ||
|
|
||
| ## Hypothesis | ||
| If we refine our UI/UX during sign up to remove friction around setting up a second device for firstrun users on desktop, then we will see an increase in multi-device users within the first 7 days of registration because we have observed that less than 30% of registration (65k clicks / 210k registration / month) engage with our mobile download buttons and at best 26% (8% 7d md / 30% ctr) of them follow through to an install within 7 days after clicking. |
vladikoff
Dec 16, 2016
Contributor
nit: in this doc there are a few firstruns and several first runs
nit: in this doc there are a few firstruns and several first runs
| If we refine our UI/UX during sign up to remove friction around setting up a second device for firstrun users on desktop, then we will see an increase in multi-device users within the first 7 days of registration because we have observed that less than 30% of registration (65k clicks / 210k registration / month) engage with our mobile download buttons and at best 26% (8% 7d md / 30% ctr) of them follow through to an install within 7 days after clicking. | ||
|
|
||
| ## Metrics | ||
| We will know our hypothesis to be true when we see the proportion of multi-device users increase after 48h and 7d of registration to FxA+Sync on firstrun. |
vladikoff
Dec 16, 2016
Contributor
registration to FxA+Sync on firstrun. is it only firstrun? or would we also look at the 'normal' sign in flow via the FF Desktop menu?
registration to FxA+Sync on firstrun. is it only firstrun? or would we also look at the 'normal' sign in flow via the FF Desktop menu?
| We will also want to keep an eye out for: | ||
| Email confirmation rate: we should not impact this negatively in any way. | ||
| Measured with flow events and visualized in re:dash | ||
| Install rate from confirmation page on mobile: If users confirmed their email on mobile, we will drive users to install via smart banner. (install rate) |
vladikoff
Dec 16, 2016
Contributor
nit: part above missing a bit of formatting or .
nit: part above missing a bit of formatting or .
|
|
||
| ### Additional AB metrics: | ||
| % of users that verify in a second Firefox instance (Desktop or Fennec) that connect that instance. XXX stomlinson to look up existing metrics to see if any match. | ||
| % of users that see the app store links that click on a link. XXX we log marketing impressions, and clicks and send this data to GA. stomlinson to figure out how to do this as part of flow events too. |
vladikoff
Dec 16, 2016
Contributor
XXX TODO notes not formatted
XXX TODO notes not formatted
|
|
||
| Email prepares the user for next steps | ||
|
|
||
|  |
vladikoff
Dec 16, 2016
Contributor
might be useful to use img tags here to make this a bit smaller so it is easier to read the doc
might be useful to use img tags here to make this a bit smaller so it is easier to read the doc
| ## Hypothesis | ||
| If we refine our UI/UX during sign up to remove friction around setting up a second device for firstrun users on desktop, then we will see an increase in multi-device users within the first 7 days of registration because we have observed that less than 30% of registration (65k clicks / 210k registration / month) engage with our mobile download buttons and at best 26% (8% 7d md / 30% ctr) of them follow through to an install within 7 days after clicking. | ||
|
|
||
| ## Metrics |
vladikoff
Dec 16, 2016
Contributor
We should add the new DataDog events we are adding into this section...
We should add the new DataDog events we are adding into this section...
shane-tomlinson
force-pushed the
fxa-51-connect-another-device
branch
2 times, most recently
from
3b2d1e2
to
1b30b35
* Updates based on @vladikoff's feedback. * Ensure metrics are well defined.
shane-tomlinson
force-pushed the
fxa-51-connect-another-device
branch
from
1b30b35
to
0d0fbea
|
@vladikoff - updated. @davismtl - mind having a look? |
|
Looks good to me. |
|
|
||
|
|
||
|
|
||
| ## Results |
davismtl
Dec 21, 2016
Contributor
For some reason, when looking at this in "View", it's lost all its formatting.
For some reason, when looking at this in "View", it's lost all its formatting.
philbooth
pushed a commit
that referenced
this pull request
Oct 17, 2017
chore(awsbox): remove awsbox config for fxa-oauth-server
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
No description provided.