Services/Sync/NextGen: Difference between revisions

No edit summary
Line 57: Line 57:
= High-level roadmap =
= High-level roadmap =


(rnewman writing now)
We can split this effort into four main areas:
 
# Design, build, and deploy the PIdP service (identity)
# Design, build, and integrate the Firefox front-end to this service, on both desktop and mobile (services integration and/or Firefox frontend engineering)
#* Depends on PIdP service
# Finish the implementation and deployment of the Sync 2.0 production service (services engineering, services operations)
# Implement and integrate the Sync 2.0 client on desktop and mobile, including UX design and UI implementation, bearing in mind concurrent version requirements (services integration).
#* Depends on PIdP service, Firefox account support, crypto work.
 
Note that (2) is blocked on (1), and (4) depends on everything else to some extent. Development work can begin but not complete until those dependencies are met.
 
It might be helpful to think of achieving a Firefox account — that is, providing a PIdP and browser integration — as one project, and browser data synchronization as a separate project on top.


More details are in [[Services/Sync/NextGen/TechnicalPlan|the technical plan]].
More details are in [[Services/Sync/NextGen/TechnicalPlan|the technical plan]].
canmove, Confirmed users
640

edits