Firefox/Sync/Progress Report/2017Q3

From MozillaWiki
< Firefox‎ | Sync‎ | Progress Report
Revision as of 23:19, 25 August 2017 by Juliemccracken (talk | contribs) (Aug 24th confidence assessments entered)
Jump to navigation Jump to search

August 24, 2017

OKR Progress

Objective Key Result Confidence Features Notes
Jul 6 Jul 25 Aug 2 Aug 24 Sep 7 Sep 21 Score
1. To enable bi-directional bookmarks on iOS by Firefox 57.

User story: As an iOS user, I’d like to see my existing mobile bookmarks on my desktop.

1.1 Users can see their mobile bookmarks on desktop. 50% 65% 65% 95%

Bookmarks are Sync'd from iOS to desktop.

  • So far so good with the internal testing. Looks great. Softvision testing is underway.
1.2 Users can delete their mobile bookmarks from their iOS device.

We don’t want to prevent users from deleting their mobile bookmarks from the mobile device.

50% 50% 50% 95%

Ability to delete mobile bookmarks from iOS device and Sync those deletions to desktop.

  • Same as with 1.1 - looks great. Softvision testing is underway.
2. To have our data provide valuable insights about Sync engine errors and bookmark validation. 2.1 Validate our validation data.

(Desktop, iOS and Android)

We don’t have confidence that our validation data query results and if they tell us what we want to know. Our analyses tell us different things depending on how they’re run. Let’s get a third party to review the validity of our queries and results.

50% 50% 75% 90%

Validated validation data

  • Largely done. The data looks good. Just needs to be written up at this point.
  • Analyst hired and starts on Aug. 28th.
2.2 Stand up dashboards with accurate bookmark validation data from Android and iOS.

Make sure that the Android and iOS pings are coming in and land the data in Presto in order to create dashboards.

50% 50% 60% 60%

Bookmark validation dashboards for iOS and Android

  • Android and iOS are landed.
  • Data seems good, but it doesn’t seem to be refreshed.
  • Might need to dig into the data a little more.
2.3 Flatten Sync engine data.

The engine data are currently unusable for creating dashboards. We need to flatten, have confidence in our results so that we can prioritize our fixes for Desktop.

50% 50% 60% 80%

Provide better sync engine error data for dashboards.

  • Flattening up the data is done and looks good. Hasn’t landed yet.
2.4 Stand up Sync Engine Dashboards.

Using the flattened Sync engine data, stand up dashboards and have confidence in the analysis.

40% 40% 40% 60%

Bookmark Validation Dashboard

  • Unknown about how long the queries will take when run across engines.
  • 2.2 is a blocker or 2.4
2.5 Formulate concrete action items from the validation and sync engine data.

Create a backlog of prioritized bugs to be addressed as a result of our data discoveries.

60% 50% 55% 50%

Implementation of a Repair Failure Strategy

  • Need to work out as a team what our strategy is...a MetricsFest.
  • To get done with 2.5 by the end of the quarter, we shouldn’t take much longer than mid-Sept. to finish 2.2 and 2.4.
3. To prevent bookmark corruption. 3.1 Land the bookmark Sync tracker on Android.

In support of Full Bookmark Management that’s being introduced in 56.

Needs to land in nightly by: July 31st (56 goes to Beta on August 7).

50% 70% 80% 95% Version-based syncing of bookmarks
  • It landed. Seems to work well.
  • The core of the work is done, and there shouldn’t be much follow-on work.
3.2 Prevent re-ordering of bookmarks on Android.

There is a recurring problem where users bookmarks are re-ordered on their mobile device. Fix this.

50% 50% 60% 60%

Prevention of bookmark reordering on Android.

  • Have discovered other problems.
  • Need to improve deduping, deletion tracking, timestamp-based change tracking.
  • Have started on improvements but nothing has landed yet.
3.3 Analyze and prevent erroneous bookmark deduping on Desktop.

There is a problem where users’ bookmarks are incorrectly deduped or reordered on their desktop device. This is a form of data loss.

60% 60% 75% 85%

Feature description(s)

  • A lot of work has been completed over the past couple weeks.
  • Good initial feedback; needs more test coverage for edge cases.
  • Targeting final review or landing pref’d off by the end of the quarter.
3.4 Batch upload API enabled for all users, with more than 99% of uploads fitting into a single atomic batch. 50% 75% 80% 80%

Batch upload API enabled

  • Still risk involved because we're still seeing 503s with batch uploads.
Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox/Sync/Progress_Report/2017Q3&oldid=1179343"