User Services/Sync/v1: Difference between revisions

Jump to navigation Jump to search

User Services/Sync/v1 (view source)

Revision as of 19:36, 1 August 2013

1,960 bytes added ,  1 August 2013
m
no edit summary
mNo edit summary
mNo edit summary
Line 32: Line 32:
* As a user, I want to be able to go into a settings menu to create my Firefox Account, so that I can set up it up in my own time.
* As a user, I want to be able to go into a settings menu to create my Firefox Account, so that I can set up it up in my own time.


=== Migration from Old Sync ===
=== Migrating from Old Sync ===
* '''MIGRATION - IDEAL''': As an existing Firefox Sync user, I want to be migrated to this new Firefox Sync service seamlessly and invisibly, so I never have to think or worry about what's happening to my data.
TBD...''in process as of 2013/08/01''
* '''MIGRATION - IF ABOVE IS NOT POSSIBLE''': As an existing Firefox Sync user, I want migrating to the new Firefox Sync service to be as simple as possible -- ideally as simple as pressing a single button a single time -- so I don't have to spend a lot of time thinking or worrying about what's happening with my data.
* '''NEW'''- ''NOTE: This user story is mostly a placeholder while we work out a detailed migration strategy.  Very likely this will change'' - As a current Sync user, I expect my current Sync data to be available as normal until I upgrade to New Sync on any one of my devices.  Once I have upgraded to new Sync on one device, the first time I use any of my other devices, I expect Firefox to prompt me to either upgrade to New Sync or to disable Sync on that device.  (This does imply that New Sync will ship simultaneously on all platforms that support current Sync...this story may change as we hash out a detailed migration strategy.)


=== Detaching Sync ===
=== Detaching Sync ===
Line 58: Line 56:
== UX design ==
== UX design ==
TBD - when/if  we have designs they should be added or linked to here
TBD - when/if  we have designs they should be added or linked to here
== Migration strategy ==
=== Strategy ===
* We want to encourage existing Sync users to migrate to a Firefox Account, without harming the experience of users who aren't ready to move.
* We're aiming for an overlap period between Sync and Sync.next. This will reduce the risk of users having partitions in their devices, reduce problems with upgrade/downgrades and staged releases, etc. The exact duration of this overlap period will depend on several factors: complexity, cost, time to market, and market parity.
* Delayed upsell. We want to sell Sync.next and Firefox Account once users are ready to upgrade -- that is, they have the right version of Firefox on each of their devices.
* Forcing function. As we ramp up, we'll remove the ability to set up an old Sync account from each product. Eventually we will force users off the old service and decommission it. See overlap period.
=== Migration mechanism ===
* Detect specific states.
** Non-email Sync account name. No migration possible.
** Single device. Encourage migration! No partitioning possible!
** Self-hosted. Offer to migrate to Mozilla's system if there's no locked pref to indicate that that's not desirable, provide docs to support continued self-hosting, inform the user of decommissioning plans so they can make an informed choice.
* Offer to set up a new Firefox Account using their same email address. Enter the normal account setup flow, which will take care of email verification. Don't reuse the password -- it's gone over the wire, many users won't remember it, and it's probably neither strong nor memorable.
* Preserve data syncing preferences, also allowing user to make new decisions at this point.
* Write decommissioning sentinel into the old Sync account. ({{Bug|895526}}, {{Bug|895518}}.)
* Disable or delete local Sync.old account.
* Clean up local prefs for sanity.
* Configure to intercept old account hooks e.g., Send Tab intents.
=== Non-goals ===
* Migration of data.
* Simultaneous syncing to Sync.old and Sync.next.
=== Open issues and action items ===
Please <s>strikethrough</s> when complete. Thanks!
* [lloyd] How long is the overlap period? Need to know some operational costs.
* [rnewman, mfinkle] What's the client engineering burden to having an overlap period?
* [rnewman] Send Tab isn't in the PICL IdP. We're trying to find out how important a feature this is for parity.
* [product] We know we plan to disable the account setup UI during ramp-up. At what point do we want to disable *login*, for those poor suckers who reinstalled Windows and want to get their data back from Sync?
* [product] When should we kill the Sync promo on Android? Depends on how valuable it is and how long our roadmap is for Sync.next.
* [?] Add-ons that provide sync engines will be screwed.
=== Original etherpad for notes ===
* https://services.etherpad.mozilla.org/sync-migration


== Change log ==
== Change log ==
* 2013/08/01 - Removed all "Migration from Old Sync" user stories as they were placeholders - new stories will be added soon.  Added "Migration Strategy" as a new top level section so all of this is in the same place.
* 2013/08/01 - Changed "Draft" banner to "Last updated", minor wording change in the "Goals" section.
* 2013/08/01 - Changed "Draft" banner to "Last updated", minor wording change in the "Goals" section.
* 2013/08/01 - Moved page to "User Services/Sync/v1" (and left a redirect in the original location); removed "What is this?" section; added "Tracking", "Goals", and "UX design" sections.
* 2013/08/01 - Moved page to "User Services/Sync/v1" (and left a redirect in the original location); removed "What is this?" section; added "Tracking", "Goals", and "UX design" sections.
Dria
canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/688377"

Navigation menu