Firefox/Sync and Backup: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 15: Line 15:
* [http://people.mozilla.com/~zfang/SignIn/Home.html OBSOLETE - Sign in to the Browser Mock ups]
* [http://people.mozilla.com/~zfang/SignIn/Home.html OBSOLETE - Sign in to the Browser Mock ups]
* [http://people.mozilla.com/~zfang/SignInMobile/Mobile.html OBSOLETE - Sign in to the Mobile Mock ups]
* [http://people.mozilla.com/~zfang/SignInMobile/Mobile.html OBSOLETE - Sign in to the Mobile Mock ups]
* [http://docs.services.mozilla.com/ Mozilla Services Documentation]
* [http://docs.services.mozilla.com/sync/index.html Sync Client Documentation]


Open questions:
Open questions:
Line 23: Line 23:
* Does all the information need to be encrypted? Does all the information need the same level of security?
* Does all the information need to be encrypted? Does all the information need the same level of security?
* Is Persona the only login method? Can a user benefit from this service without a Persona account?
* Is Persona the only login method? Can a user benefit from this service without a Persona account?
* Back-up = Permanent storage? Do we want to remove data after certain level of inactivity?
* Back-up == Permanent storage? Do we want to remove data after certain level of inactivity?
* Discoverability of Sync+Back Up: Hidden in settings? A more findable UI with feedback about status (i.e. shows avatar if logged in).
* Discoverability of Sync+Back Up: Hidden in settings? A more findable UI with feedback about status (i.e. shows avatar if logged in).
* Profile Sync vs Experience Sync: Can we offer an API that add-on and web-app developers can use to store information about the user? Can we run a freemium model?
* Profile Sync vs Experience Sync: Can we offer an API that add-on and web-app developers can use to store information about the user? Can we run a freemium model?
* Transition from the actual Sync to the new service. How does it look like?
* Transition from the actual Sync to the new service. How does it look like?
* How does this look with a locally run machine? Is it possible to run this service locally?
* How does this look with a locally run machine? Is it possible to run this service locally?

Latest revision as of 23:34, 9 July 2012

This page aggregates resources and information about the work that has already been done to define how to simplify browser synchronization and profile back-up. Some of this information can be obsolete.


Open questions:

  • Is the user experience to "pair devices" or to "log in to the account"?
  • What's the required security level?
  • Key stored locally or wrapped and stored remotely? Do we want to offer both options?
  • Does all the information need to be encrypted? Does all the information need the same level of security?
  • Is Persona the only login method? Can a user benefit from this service without a Persona account?
  • Back-up == Permanent storage? Do we want to remove data after certain level of inactivity?
  • Discoverability of Sync+Back Up: Hidden in settings? A more findable UI with feedback about status (i.e. shows avatar if logged in).
  • Profile Sync vs Experience Sync: Can we offer an API that add-on and web-app developers can use to store information about the user? Can we run a freemium model?
  • Transition from the actual Sync to the new service. How does it look like?
  • How does this look with a locally run machine? Is it possible to run this service locally?