User Services/Sync/v1: Difference between revisions

User Services/Sync/v1 (view source)

Revision as of 19:02, 18 July 2013

48 bytes removed , 18 July 2013

m

→‎Performance & Stability

Dria

canmove, Confirmed users, Bureaucrats and Sysops emeriti

6,906

edits

@@ Line 39: / Line 39: @@
 === Performance & Stability ===
-* '''NEW''' - As a user, in the event of Sync service interruptions, I expect to be able to use my browser and previously-synced local data as normal, even if Firefox cannot access the Sync servers for an extended period of time.
+* As a user, in the event of Sync service interruptions, I expect to be able to use my browser and previously-synced local data as normal, even if Firefox cannot access the Sync servers for an extended period of time.
-* '''NEW''' - As a user, in the event of Sync service interruptions, I expect zero data loss across all of my devices, even if Firefox cannot access the Sync servers for an extended period of time.
+* As a user, in the event of Sync service interruptions, I expect zero data loss across all of my devices, even if Firefox cannot access the Sync servers for an extended period of time.
-* '''NEW''' - As a mobile user, I expect Sync to be as bandwidth-conservative as possible, minimizing re-downloading or re-uploading of data in event of system errors or other issues, and ensuring that bandwidth used should be approximately proportional to the volume of changes.
+* As a mobile user, I expect Sync to be as bandwidth-conservative as possible, minimizing re-downloading or re-uploading of data in event of system errors or other issues, and ensuring that bandwidth used should be approximately proportional to the volume of changes.
-* '''NEW''' - As a user of a more limited mobile device (ARMv6, FirefoxOS), I expect Sync to be able to intelligently scale down in terms of the amount of bandwidth and storage it uses so it does not excessively tax my data plan or storage space.
+* As a user of a more limited mobile device (ARMv6, FirefoxOS), I expect Sync to be able to intelligently scale down in terms of the amount of bandwidth and storage it uses so it does not excessively tax my data plan or storage space.
 === FHR ===