|
|
Line 107: |
Line 107: |
| === Performance & Stability === | | === Performance & Stability === |
| * As a user, in the event of Sync service interruptions, I expect to be able to use my browser and previously-synced local data as normal, even if Firefox cannot access the Sync servers for an extended period of time. | | * As a user, in the event of Sync service interruptions, I expect to be able to use my browser and previously-synced local data as normal, even if Firefox cannot access the Sync servers for an extended period of time. |
|
| |
| == Desktop MVP - contextual user stories ==
| |
| 1. As a Firefox user, I want the "core" functionality of Sync to remain the same in every respect once a Firefox Account based registration scheme replaces the crypto-based registration scheme so that I can continue to experience the same benefits from Sync in the future as I do today.
| |
|
| |
| Acceptance criteria
| |
| 1. Any data that is syncable in current Sync will be syncable when we introduce accounts
| |
| 2. Any choices a user has to customize current Sync will be available when we introduce accounts
| |
| 3. A user will not detect any difference in performance of Sync today and performance of Sync after we introduce accounts
| |
|
| |
| 2. As a user who currently has a Sync account, I can choose to migrate to FxA/Sync after the release of 29 so that I can benefit from having an FxA.
| |
| Acceptance criteria
| |
| 1.A user of current sync can find detailed instructions on a Mozilla web property for how to transition from current sync to FxA/Sync
| |
| 2.A user can follow those instructions to transition successfully from current Sync to FxA/Sync
| |
| 3.After that user has transitioned from current sync to FxA/Sync they will only be able to manage their Sync preferences by signing-in to their Firefox Account.
| |
| 4.After transition, the default views for this users will change from current Sync views to FxA/Sync views
| |
|
| |
| 3. As a user who is not signed-in to Sync when I upgrade to 29, I want to be able to set-up FxA/Sync so that I can benefit from Sync and FxA.
| |
| Acceptance criteria
| |
| 1. As a user I can enter the FxA/Sync set up process by: A)Clicking a promotional snippet B)Clicking the Sync icon in the footer of the about:home our about:newtab page C)Selecting "Sync set up" from the Firefox Tools menu
| |
|
| |
| 4. As a product owner, I want to limit the amount of exposure that current sync users have to FxA/Sync, so that I can wait until we have a more streamlined transition flow before I more actively encourage them to transition.
| |
|
| |
| Acceptance criteria
| |
| 1.Users who are signed into sync when the upgrade to 29 will see nothing different in their Sync preferences from what they see today until they transition to FxA
| |
| 2.Users who are signed into sync when they upgrade to 29 will not see promotional language offered in a Snippet on their about:home page that pushes them to transition to FxA until they transition to FxA.
| |
|
| |
| 5. As a product owner, I want to prevent current sync users from making any change to their current sync settings unless they upgrade to FxA so that I can simplify current sync maintenance requirements.
| |
| Acceptance criteria
| |
| 1.Users who are signed into sync when they upgrade to 29 will not be able to change any setting in their Sync preferences or add a new device
| |
| 2.If these users attempt to change their settings or add a device they will be directed to transition to FxA
| |
| 3.Users who are signed into sync and using a version of Firefox that predates 29 will not be allowed to make any changes to their Sync preferences or add a new device
| |
|
| |
| 6. As a product owner I want to prevent a user who has not yet set up a Sync account from creating a current sync account after the release of 29 so that I can more easily transition all users to FxA/Sync over time.
| |
| Acceptance criteria
| |
| 1. After the release of 29, no user, on any version of Firefox will be allowed to create a current Sync account
| |
|
| |
| 7. As a user I want to be able to change or reset my password so that I can continue to use Sync even if I forget my Firefox Account password.
| |
|
| |
| Acceptance criteria
| |
| 1.A user can access Firefox Account settings
| |
| 2.A user can choose to change or reset their password from the settings
| |
|
| |
| 8. As a user, I want to be able to sign-out of my Firefox Account so that I can decide to stop Syncing data on a particular client.
| |
|
| |
| Acceptance criteria
| |
| 1.A user can sign-out of her Firefox Account
| |
| 2.After the user has signed out of an account on a given client, no data will be shared with or from that client
| |
|
| |
| 9. As a user, I want to be able to sign-in to my Firefox Account so that I can decide to Sync data from a particular client if I have previously signed-out of that client.
| |
|
| |
| Acceptance criteria
| |
| 1.A user can sign-in to her Firefox Account
| |
| 2.After the user has signed-in to a particular client, data will resume syncing to/from that client
| |
|
| |
| 10. As a user, I want to create a Firefox Account so that I can use Sync to trade data across my Firefox clients.
| |
|
| |
| Acceptance criteria
| |
| 1.A user can create a Firefox Account
| |
| 2.A user can use their own email address and password of their choosing to create and account
| |
|
| |
| 11. As a user, I want to know how strong my chosen password is against security attacks so that I can determine the password strength I want.
| |
| Acceptance criteria
| |
| 3.A user will see a "password strength" meter as they enter their password
| |
|
| |
| 12. As a user, if I am prompted to set-up Sync, I want the option to defer so that I can choose to use Firefox without creating a Firefox Account or setting up Sync.
| |
| Acceptance Criteria
| |
| 1.If a user is prompted to set-up Sync, he can choose not to
| |
| 2.If the user wishes to set-up Sync at a later time, he can.
| |
|
| |
| 13. As a product owner, I want to send a verification email to each email address provided by an account creator so that I can provide necessary notifications to the user in the future
| |
|
| |
| Acceptance Criteria
| |
| 1.Users will receive a verification email after they submit their email address and password
| |
| 2.This email will be sent to the address provided by the user during the account creation process
| |
|
| |
| 14. As a user, I want to be able to verify my email address and my desire to set up a Firefox Account by clicking a link in the verification email I received from Firefox
| |
|
| |
| Acceptance Criteria
| |
| 1. Users can open the verification email
| |
| 2.Users can click a link in the email to verify their email address
| |
|
| |
| 15. As a user, I want to know that my account has been verified after I click a link in my verification email so that I know I have completed the process of setting up an account
| |
|
| |
| Acceptance Criteria
| |
| 1.After a user clicks a verification link in the email received from Firefox email address they will see a web page declaring a success state
| |
| 2. This page will open in their default browser
| |
| 3. If the default browser is something other than Firefox, this user will be directed to open Firefox
| |
|
| |
|
| |
| 16. As a user, I want the option to review the ToS and Privacy Policy so that I can make sure I’m comfortable providing my information to Mozilla.
| |
|
| |
| Acceptance criteria
| |
| 1.Users can link to the ToS from the “Create Account” page
| |
| 2.Users can link to the Privacy Policy form the “Create Account” page
| |
| 3.Both the ToS and PP will open in New Tabs if clicked
| |
| 4.A user may accept or decline the ToS and/or PP
| |
| 5.If a user declines the FxA creation flow is stopped
| |
| 6.If a user accepts, the FxA creation flow continues
| |
|
| |
| 17. As a user, after I have verified my email address I want to be able to access my Sync Preferences so that I can choose what data I want to share across clients and begin syncing
| |
|
| |
| Acceptance criteria
| |
| 1.Users can access Sync Preferences after they have verified their account
| |
| 2.Users can choose to “Start Syncing” from the Preferences page
| |
| 3.Users can select to share “Everything” and will begin syncing all possible data
| |
| 4.Users can further customize what they want to share by selecting from the following list
| |
| *Bookmarks
| |
| *History
| |
| *Passwords
| |
| *Tabs
| |
| *Add-ons (b/w Desktops only)
| |
| *Preferences (b/w Desktops only)
| |
|
| |
| 18. As a user I want to tell Firefox how old I am so that I can be cleared for COPPA restricted activities
| |
| Acceptance criteria
| |
| 1.Users will be asked to provide their year of birth on the account set up page where they enter their email address and password
| |
| 2.If a user enters a year that indicates their age is less than 13 years old on the day they attempt to set up an account she will be denied a Firefox Account
| |
| 3.If a user enters a year that indicates their age is at least 13 years old on the day they attempt to set up an account she will be granted a Firefox Account
| |
|
| |
| 19. As a user who is not signed-into Sync, I want the onboarding experience for Firefox 29 to include a strong call to action to set up Sync so that I can begin to take advantage of Sync and the value of Firefox Accounts.
| |
| Acceptance criteria
| |
| 1. Users who are not signed-into sync when they upgrade to Firefox 29 will experience an interactive onboarding experience
| |
| 2. This experience will include a strong call to action to set up Sync
| |
|
| |
|
| == Migration == | | == Migration == |