We move forward with Chris' plan [1] with the following amendments/clarification:
1) We support old-sync-signin for existing users (i.e. "let 'em be") in 29+, yes. But we do not allow for old-sync-account-creation in 29+. [2] 2) We limit FxA promotion in 29 to users that don't currently have a Sync account setup in their profile (i.e. nearly 99% of our users). We don't upsell/promo FxA to users with sync profiles in 29 (we do it in 30). I think that's it, and I believe after some vidyo/IRC that we're in agreement that this is doable both in engineering and UX. -Mark [1] https://mail.mozilla.org/pipermail/sync-dev/2014-January/000627.html [2] two reasons for this: a) allowing creation of old-sync accounts introduces complexity on the server-side "support two syncs" ops migration if we can't depend on a flat account DB b) seems like it just opens up complexity in users messaging down the road when we do eventually turn off the old sync auth system (ex: FAQs that have to now talk about both firefox versions *and* dates) On Tue, Jan 7, 2014 at 11:34 AM, Nick Alexander <nalexan...@mozilla.com>wrote: > On 1/3/2014, 3:59 PM, Chris Karlof wrote: > >> Hi all, >> >> I see today listed as the deadline for a decision on a transition plan. >> I haven't seen significant discussion on this over the last day or two. >> >> What I've seen is: >> - https://wiki.mozilla.org/User_Services/Sync/Migration >> - https://services.etherpad.mozilla.org/sync-migration >> - >> https://www.lucidchart.com/documents/edit/4678-1408- >> 52b1b652-9823-7a810a00c462 (Sync >> Migration tab) >> - Brendan asking "why given how sync works now, we can't keep the option >> for those users who want the same secrecy property they have now" >> >> The most concrete transition proposal I've seen is by Richard and Ryan >> F., largely captured in the Lucid chart linked to above. It's largely >> sensible, but it includes elements that I don't consider minimal (e.g., >> auto transitioning users and upselling). >> >> Here's my proposal for a bare minimum strategy for an *initial* >> transition from Existing Sync to FxA Sync. >> >> tl;dr *Just let Existing Sync users be. Support FxA Sync and Existing >> >> Sync side by side in Fx29 with no attempt to upsell or transition from >> Existing Sync -> FxA Sync.* >> > > I support this. > > *What this means:* >> >> 1) For users that are already connected to Existing Sync, Existing 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 Existing Sync first. >> 2) The default "Create Account" screen for Sync will change to use FxA. >> We include warnings that this won't work with Sync on Fx29- or Sync with >> pairing. For users looking for "Existing Sync", we also include a link >> that will direct them to the Existing Sync "Setup Sync" and "Pair A >> Device" screens. >> > > 3) The default "Login" screen for Sync will change to use FxA. We >> include warnings that this won't work with Sync on Fx29- or Sync with >> pairing. For users looking for "Existing Sync", we include a link that >> will direct them to the Existing Sync "Setup Sync" and "Pair A Device" >> screens. >> > > I support this approach. Documentation and SUMO are the drivers to make > this palatable, and I assume that doesn't need to be done by Fx29 code > complete. > > *What this means for the future:* >> >> 1) We don't necessarily have to commit to a sunset date or strategy for >> Existing Sync *now*. New users will (most likely) get FxA Sync and old >> users have the capability to continue to use Existing Sync, if they >> desire. >> 2) In Fx29, we lay what technical groundwork we can for a future sunset >> date, e,g, deprecation messaging channels. >> 3) In Fx29, we lay what technical groundwork we can for future >> transition strategies and upsells, e.g., starting to record the Firefox >> version of connected sync clients. >> > > I think we should be a little more opportunistic at Fx29 with one upsell: > user with a single device. This user is completely confused about what > Sync does. We can transition them. We should transition them. Then we > can at least message them via email about how we can do better for them. > > Nick >
_______________________________________________ Sync-dev mailing list Sync-dev@mozilla.org https://mail.mozilla.org/listinfo/sync-dev
