User Services/Sync/Migration: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
General discussion of migration issues for Sync.next.  The product owner and team have not made final decisions on these issues.
A summary of the transition from Legacy Sync -> FxA Sync in Fx29. A decision was made on 1/8/14.


== New Sync Users ==
== Legacy Sync Users ==
* No migration issues, just use FxA for the first time.
* For users that have a browser profile that is already connected to Legacy Sync, Legacy Sync will continue to work when they upgrade to Fx29. There will be no upsell to FxA Sync, and no attempt to transition them to FxA Sync in Fx29. Just let 'em be. In Fx29, these users will see no evidence of FxA Sync without disconnecting from Legacy Sync first.
* All Fx29 will prompt with FxAccount flow, informed that Fx29- won't sync with this account.
* These users will not see the marketing information about FxA and Sync in the "walkthrough" shown in Fx29 update.
* If user has Fx28, they should see warning that this is deprecated? (a guess)
* At various UI points in Fx29, we will provide users connected to Legacy Sync with a link to a SUMO page providing details about the transition and future plans.
* Legacy Sync users can continue to connect new browsers to Legacy Sync on Fx28 and below.
* Legacy Sync users *will not* be able to connect new browsers to Legacy Sync on Fx29+. The login screen for FxA Sync will provide a link to a SUMO page providing further information for users trying to do this (i.e., options are install Fx28 or below or upgrade all your devices to Fx29 and use FxA Sync).  
* New Legacy Sync accounts can be created on Fx28 and below, but not on Fx29+.
* We have to transition these users to FxA Sync eventually, but we'll do this more thoughtfully in Fx30+.


== Existing Sync user ==
== FxA Sync Users (i.e., new Sync users) ==
* If they manually chose to use Sync.next, they would be informed that all Fx29- devices will not sync with FxA & Sync.next.
* For users that do not have a browser profile connected to Legacy Sync, they will see marketing information about FxA and Sync in the "walkthrough" shown in Fx29 update.
* Firefox clients would detect if sync account clients all use Fx29+, then message user to use sync.next - FxA flow.
* All sync entry points will take users through FxA Sync create account/login flow.
* These users will be able to create and login to FxA Sync accounts on Fx29+.


== Fx29 ==
== Other Fx29 work ==  
* Will Sync.old and Sync.next be in Fx29 in parallel?
* Lay what technical groundwork we can for a future sunset date, e,g, deprecation messaging channels.
** This is a sticking point for existing users who have/do not want to upgrade at that time.
* Lay what technical groundwork we can for future transition strategies and upsells, e.g., starting to record the Firefox version of connected sync clients.
* Tracking here: https://bugzilla.mozilla.org/show_bug.cgi?id=956445


== Sync Server ==
== Sync Server ==
* v1.2 API is being discussed, not sure the outcome.
* There will be two DBs: Sync 1.1 and Sync 1.5 will point at different DBs
* assumption (edwong's) is that api v1.1 and v1.2 are not compatible and v1.2 requires Fx29+.
* Sync 1.5 will require Fx29.
* There will be two DBs: Sync 1.1 and Sync 1.2 will point at different DBs
 
PROPOSED: Sync API will have minimal change, mostly removal of unused properties.


== Channels ==
== Channels ==
* Feature will be off and enabled via pref in Nightly/Aurora/Beta
* Feature will be on and enabled in Nightly/Aurora/Beta
** increases risk as little public user testing
* Jonath: No guarantees on pre-release channels
** Since it's behind pref, FxAccount user may have to be recreated, Sync data is not guaranteed.
* Finkle: Lots of Fennec users use Nightly
 
PROPOSED: Need a high visibility blog post for users to try out sync using test profiles.


== Custom Servers ==
== Custom Servers ==
* Do we allow for use of custom sync server? 
* If you're already connected to Sync, then in Fx29, your set up will continue to work.
** Will they still be able to use FxA in this flow?
* Otherwise, it is subject to other above restrictions for Legacy Sync users.
PROPOSED: No UI for this, but about:config paths can be modified to support custom servers.
* Custom servers should in theory be possible with FxA Sync, but with a different architecture (Token server + Sync 1.5).

Revision as of 00:43, 9 January 2014

A summary of the transition from Legacy Sync -> FxA Sync in Fx29. A decision was made on 1/8/14.

Legacy Sync Users

  • For users that have a browser profile that is already connected to Legacy Sync, Legacy Sync will continue to work when they upgrade to Fx29. There will be no upsell to FxA Sync, and no attempt to transition them to FxA Sync in Fx29. Just let 'em be. In Fx29, these users will see no evidence of FxA Sync without disconnecting from Legacy Sync first.
  • These users will not see the marketing information about FxA and Sync in the "walkthrough" shown in Fx29 update.
  • At various UI points in Fx29, we will provide users connected to Legacy Sync with a link to a SUMO page providing details about the transition and future plans.
  • Legacy Sync users can continue to connect new browsers to Legacy Sync on Fx28 and below.
  • Legacy Sync users *will not* be able to connect new browsers to Legacy Sync on Fx29+. The login screen for FxA Sync will provide a link to a SUMO page providing further information for users trying to do this (i.e., options are install Fx28 or below or upgrade all your devices to Fx29 and use FxA Sync).
  • New Legacy Sync accounts can be created on Fx28 and below, but not on Fx29+.
  • We have to transition these users to FxA Sync eventually, but we'll do this more thoughtfully in Fx30+.

FxA Sync Users (i.e., new Sync users)

  • For users that do not have a browser profile connected to Legacy Sync, they will see marketing information about FxA and Sync in the "walkthrough" shown in Fx29 update.
  • All sync entry points will take users through FxA Sync create account/login flow.
  • These users will be able to create and login to FxA Sync accounts on Fx29+.

Other Fx29 work

  • Lay what technical groundwork we can for a future sunset date, e,g, deprecation messaging channels.
  • Lay what technical groundwork we can for future transition strategies and upsells, e.g., starting to record the Firefox version of connected sync clients.
  • Tracking here: https://bugzilla.mozilla.org/show_bug.cgi?id=956445

Sync Server

  • There will be two DBs: Sync 1.1 and Sync 1.5 will point at different DBs
  • Sync 1.5 will require Fx29.

Channels

  • Feature will be on and enabled in Nightly/Aurora/Beta
  • Jonath: No guarantees on pre-release channels
  • Finkle: Lots of Fennec users use Nightly

Custom Servers

  • If you're already connected to Sync, then in Fx29, your set up will continue to work.
  • Otherwise, it is subject to other above restrictions for Legacy Sync users.
  • Custom servers should in theory be possible with FxA Sync, but with a different architecture (Token server + Sync 1.5).
Retrieved from "https://wiki.mozilla.org/index.php?title=User_Services/Sync/Migration&oldid=871203"