<snip> My tentative proposal for iOS is to* ship 3.0 as-is*, enabling > bidirectional sync in 4.0 or 5.0 — as soon as we're confident that desktops > will eventually self-recover and our current 50-50 bias will trend towards > 100%. I think this is acceptable; we'll continue to offer the read-only > fallback. > > The alternative is that we ship 3.0 with the flag flipped, and > approximately *70%* of our users get bidirectional syncing, with some of > those users' Firefoxes eventually stopping as they encounter fresh > corruption. That number is lower than I feel comfortable with for a feature > that changes how your bookmark UI behaves. >
I concur. The likelihood of confusion and frustration is too high to ship with bidirectional Sync on. We will get better day as this rides to release and be better able to estimate the pain in 6 weeks, 12 weeks, etc. Data! Nick
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
