Confirmed users, Bureaucrats and Sysops emeriti
1,452
edits
Mobile/Projects/Firefox Accounts with Sync 1.1 integration: Difference between revisions
Mobile/Projects/Firefox Accounts with Sync 1.1 integration (view source)
Revision as of 20:53, 14 January 2014
, 14 January 2014no edit summary
No edit summary |
|||
| Line 79: | Line 79: | ||
* In the event of service interruption to Sync, this must have no impact with current use of the browser | * In the event of service interruption to Sync, this must have no impact with current use of the browser | ||
* In the event of service interruption, all data that should be synced will sync once service is restored in a way that is seamless to the user and without degradation to browser usage | * In the event of service interruption, all data that should be synced will sync once service is restored in a way that is seamless to the user and without degradation to browser usage | ||
=== Migration === | |||
* We want to encourage existing Sync users to migrate to a Firefox Account, without harming the experience of existing users (defined as those who have 2+ devices attached to an existing sync account) who aren't ready to move for a minimum period of 3 months from when outbound communication has begun. | |||
* There must be overlapping support for current sync accounts who haven't signed up to Firefox Account and to the new Firefox Account & sync v1.1 for a minimum period of 3 months from when outbound communication has begun | |||
* Wiki for migration information: https://wiki.mozilla.org/User_Services/Sync/Transition_To_FxA_Sync | |||
== Firefox for Android MVP - contextual user stories == | == Firefox for Android MVP - contextual user stories == | ||
| Line 252: | Line 258: | ||
** AC 3. | ** AC 3. | ||
*** Once EOL hits, existing users will not be able to access their sync unless they migrate to FxA | *** Once EOL hits, existing users will not be able to access their sync unless they migrate to FxA | ||