Require FxA for Lockbox as part of a first-run experience

[sandysage]

trafficstars

Part of product initiative #528 - Provide onboarding support for new users to the Lockbox extension

Goal There are too many initial entry points that create confusion around why an entry would be created before an account. With the current state of the product offering, an account is required to realize the current value of security.

Requiring it for all users, and moving it to part of the first-run experience, we align to user expectations around account creation as a necessary first step to getting started.

NOTE This doesn't eliminate guest access entirely from our radar. But it's not seen as a value at this stage in our progress.

Designs https://mozilla.invisionapp.com/share/CTEFRXMZ7#/279643448_0-1_Onboarding_-_Connect_FxA

Design Acceptance Criteria

• [x] Require FxA to be connected (create new or sign in to existing) for all users
• [x] Include the FxA prompt as part of a multi-step onboarding first run
• [x] Allow a user to easily create a new account or sign in to an existing account

Content Tasks

• [ ] Header/Content of Step 1
• [ ] CTAs/Headers for FxA access

[jimporter]

Does this mean there are no guest accounts? If so, what's the impetus for this? My understanding was that we thought guest accounts were an important way to make it easier for people to get started.

[sandysage]

Next up:

• [ ] content review of the page that launches you into the FxA flow
• [ ] engineering review to determine feasibility & scoping (engineering stories)
• [ ] user research review to make sure there is alignment to the provided recommendations
• [ ] product sign off on the acceptance criteria

[linuxwolf]

@changecourse @sandysage see https://github.com/mozilla-lockbox/lockbox-extension/issues/534#issuecomment-367502065 for questions/concerns before engineering can scope.