canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
Line 81: | Line 81: | ||
* 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 '''<= is this implemented? if not, do we have ux spec for this?''' | * 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 '''<= is this implemented? if not, do we have ux spec for this?''' | ||
=== Migration === | === Fx30 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. | * 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 | * 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 |