On 9/07/2015 03:30, Ryan Feeley wrote:
> I’m more interested in engagement than adoption. I think we need to
> consider single-device syncers as a failure of UX because sync is not a
> good back up solution (until we make it one, which I support).
This is an important perspective, although I don't entirely agree. Sync
is an OK backup solution most of the time, in fact it has saved my bacon
in a single-device setup after at least one instance of an
ill-considered `rm -rf`.
Multiple connected devices is definitely the desired state, but
single-connected-device does have some non-zero user value. It's
certainly not as much value, and it's probably hard for them to realize
it early in the onboarding process, but it's non-zero.
At the very least, they can put a smiling mugshot of themselves in the
hamburger menu :-)
We should think of single-device users as an incomplete conversion, as
another intermediate state in the onboarding funnel. If users get to
this state, it's easier for us to message them about the real value of
sync via e.g. in-browser affordances for connecting a second device.
> By letting users know about other platforms up front, we will hopefully
> drive other platform downloads, leading to syncing, but have fewer
> single-device syncers. If successful, this means fewer accounts overall,
> but of a higher quality.
I feel we're more likely to have success in getting users to go from 0
to 1 to 2, than in getting them to jump straight from 0 to 2. But
that's just a guess, and this question seems very amenable to
measurement once we get the right metrics in place.
Cheers,
Ryan
>> On Jul 8, 2015, at 1:22 PM, Edwin Wong <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> I'd like to see an A/B test where we put 'make fx yours' screen
>> before/after verified email screen. Our users will tell us if
>> increased friction vs early customization gets users through the flow.
>>
>> -e
>>
>> On Wed, Jul 8, 2015 at 8:33 AM, John Gruen <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Agree with Mark and Ryan K. on the problem of overloading the
>> funnel before registration. It seems like there are two competing
>> interests coming into play here: increasing signups vs increasing
>> engagement. Is there a middle path where we can do both?
>>
>> I’ve reworked the flow to hopefully address both of these concerns:
>>
>>
>> https://www.lucidchart.com/documents/view/92d0ec74-a2af-40b8-b714-6db99149e39c/1
>>
>> Thoughts?
>>
>> JG
>>
>>
>> > On Jul 7, 2015, at 6:25 PM, Ryan Kelly <[email protected]
>> <mailto:[email protected]>> wrote:
>> >
>> > On 8 July 2015 at 08:12, Ryan Feeley <[email protected]
>> <mailto:[email protected]>> wrote:
>> >>
>> >> In the spirit of increasing engagement, I’m proposing we add
>> some steps to registration to help users understand what sync is,
>> and what devices support it.
>> >>
>> >>
>>
>> https://www.lucidchart.com/documents/view/92d0ec74-a2af-40b8-b714-6db99149e39c
>> >>
>> >
>> > I like the additional customization and linkage, but I'm not
>> sure that
>> > the registration flow is the right place for them. That's a lot of
>> > screens for the user to click through before completing their setup,
>> > which means a lot of opportunities for them to decide they can't be
>> > bothered.
>> >
>> > In particular, I think the download links would be more valuable if
>> > surfaced after the first device is setup, rather than being a
>> > potential roadblock to setting it up. (Like "ok, you're all
>> set, now
>> > sync with these other devices").
>> >
>> > Ryan
>> > _______________________________________________
>> > Dev-fxacct mailing list
>> > [email protected] <mailto:[email protected]>
>> > https://mail.mozilla.org/listinfo/dev-fxacct
>>
>> _______________________________________________
>> Dev-fxacct mailing list
>> [email protected] <mailto:[email protected]>
>> https://mail.mozilla.org/listinfo/dev-fxacct
>>
>>
>
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
