Identity/AttachedServices: Difference between revisions

m (fix formatting of previous commit)
Line 1: Line 1:
== Overview ==
== Overview ==


We want users to have access to their data, in particular the data that forms their web-browsing context (bookmarks, tabs, web apps, passwords, etc.) from all of their devices. This data should be tied to their identity, so that logging into a device is sufficient to connect to all the services the user has previously set up, whether those services are provided by Mozilla or third parties. These are Identity-Attached Services, which, as a whole, we're code-naming PICL (Profile In the Cloud). While we figure out what PICL will include, and until we can demonstrate true user value, this is a Mozilla Labs project. If PICL is successful, it will subsume Firefox Sync.
We want users to have access to their data, in particular the data that forms their web-browsing context (bookmarks, tabs, web apps, passwords, etc.) from all of their devices. This data should be tied to their identity, so that logging into a device is sufficient to connect to all the services the user has previously set up, whether those services are provided by Mozilla or third parties. These are Identity-Attached Services, which, as a whole, we're code-naming PICL (Profile In the Cloud).


Some early explorations of the issues surrounding this effort are available in this public Mozilla tech talk: http://vid.ly/5x1u5r
Some early explorations of the issues surrounding this effort are available in this public Mozilla tech talk: http://vid.ly/5x1u5r


The PiCL [https://wiki.mozilla.org/Identity milestone schedule] can be viewed under the roadmap section on the Identity page.
As of the second quarter of 2013, PICL is no longer an experiment. Check out [[/Identity/AttachedServices/Roadmap|the roadmap]].


== Use Cases ==
== Use Cases ==
668

edits