Confirmed users, Bureaucrats and Sysops emeriti
1,452
edits
Mobile/Projects/Firefox Accounts with Sync 1.1 integration: Difference between revisions
Jump to navigation
Jump to search
Mobile/Projects/Firefox Accounts with Sync 1.1 integration (view source)
Revision as of 20:46, 14 January 2014
, 14 January 2014→Firefox for Android MVP - contextual user stories
| Line 142: | Line 142: | ||
** AC 1. | ** AC 1. | ||
*** When a user taps the 'sync tab' in the tab tray, concise & clear messaging is provided about the benefits of creating a FxA to enable sync with a link taking the user to the account creation flow | *** When a user taps the 'sync tab' in the tab tray, concise & clear messaging is provided about the benefits of creating a FxA to enable sync with a link taking the user to the account creation flow | ||
* As a user, my only option to enable sync is to create a FxA from Fx29 onwards. | |||
** AC 1. | |||
*** Current existing sync sign-up and device pairing is no longer supported from Fx29 | |||
** AC 2. | |||
*** The only way to enable sync is by completing the FxA creation flow for new users | |||
* 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 | |||
** AC 1. | |||
*** Users can open the verification email after completing the appropriate steps in the FxA creation flow | |||
** AC 2. | |||
*** Users can click a link in the email to verify their email address | |||
* 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. | |||
** AC 1. | |||
*** Users can link to the ToS from the “Create Account” page | |||
** AC 2. | |||
*** Users can link to the Privacy Policy form the “Create Account” page | |||
** AC 3. | |||
*** Both the ToS and PP will open in a mobile-friendly format | |||
** AC 4. | |||
*** A user may accept or decline the ToS and/or PP | |||
** AC 5. | |||
*** If a user declines the FxA creation flow is stopped | |||
** AC 6. | |||
*** If a user accepts, the FxA creation flow continues | |||
* As a user I want to tell Firefox how old I am so that I can be cleared for COPPA restricted activities | |||
** AC 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 | |||
** AC 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 accountm she will be denied a Firefox Account | |||
** AC 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 | |||
=== Core existing sync user stories === | === Core existing sync user stories === | ||
| Line 171: | Line 201: | ||
** AC 3. | ** AC 3. | ||
*** Users can access bookmarks from another FxA device from a folder | *** Users can access bookmarks from another FxA device from a folder | ||
* As a user, I want to customize my sync preferences so I can choose what data to share across my screens for syncing so I have control of the data I am sending to the cloud. | |||
** AC 1. | |||
*** Preferences can be accessed in the Settings / Sync menu | |||
** AC 2. | |||
*** Preferences are global and not local to the device where applicable | |||
** AC 3. | |||
*** 'add-ons' and browser 'preferences' can only be shared across desktop clients and therefore not appear in the mobile settings preferences list | |||
=== Detaching Sync === | === Detaching Sync === | ||
* As a user, I want to be able to stop Syncing to preserve data costs on my mobile, but be able to preserve the ability to sync when I resume syncing again. | * As a user, I want to be able to stop Syncing to preserve data costs on my mobile, but be able to preserve the ability to sync when I resume syncing again. | ||
** AC 1. | ** AC 1. | ||
*** In the Settings / Sync menu, users must have the ability to turn off sync | *** In the Settings / Sync menu, users must have the ability to turn off sync either by expressly 'turn off sync' or 'sign out of FxA' | ||
** AC 2. | ** AC 2. | ||
*** In the Settings / Sync menu, users must have the ability to resume sync | *** In the Settings / Sync menu, users must have the ability to resume sync either by expressly 'turn on sync' or 'sign in to FxA' | ||
=== Security/Encryption === | === Security/Encryption === | ||
| Line 192: | Line 229: | ||
** AC 2. | ** AC 2. | ||
*** Users must detect no change to browser performance when sync service is resumed and the backlog of sync data is being processed | *** Users must detect no change to browser performance when sync service is resumed and the backlog of sync data is being processed | ||
=== Migration === | |||
* As a user who currently has an existing sync account with 2+ devices attached to it, I cannot migrate to FxA+Sync1.1 using the standard points of entry in Fx29 but I can find out what's going on. | |||
** AC 1. | |||
*** SUMO article is written about the migration of existing sync users | |||
** AC 2. | |||
*** Release notes are written about the migration of existing sync users | |||
** AC 3. | |||
*** A link is available in-product (Settings / Sync) that points to an article or information about the migration of existing sync users | |||
* As a user who currently has an existing sync account with 2+ devices attached to it, I can migrate to FxA+Sync1.1 using the standard points of entry from Fx30 onwards. | |||
** AC 1. | |||
*** FxA creation points of entry must all support migration existing sync users through the FxA flow | |||
** AC 2. | |||
*** Current sync data is moved over to the new FxA system | |||
** AC 3. | |||
*** Once migrated, users can only manage their sync account via FxA and not through any old sync methods | |||
* As a user who currently has an existing sync account with 2+ devices attached to it, I expect my current sync functionality to behave as-is for a minimum of 3 months from when outbound communication about the service EOL has started (expected to begin in Fx 30) | |||
** AC 1. | |||
*** Outbound comms plan prepared and in place about EOL-ing existing sync and replacing it with FxA+Sync1.1 | |||
** AC 2. | |||
*** EOL will not happen for a minimum of 3 months (2 release cycles) from when outbound comms actively have begun | |||
** AC 3. | |||
*** Once EOL hits, existing users will not be able to access their sync unless they migrate to FxA | |||
== Migration == | == Migration == | ||