Confirmed users
971
edits
| Line 16: | Line 16: | ||
== Crypto and Storage in the Browser == | == Crypto and Storage in the Browser == | ||
We run a Sync Client in the browser. This means that we talk the standard Sync protocol to grab sync data, decrypt the records and store the data in local storage. We run queries against a locally stored copy of the data. | We run a Sync Client in the browser, implemented in JavaScript. This means that we talk the standard Sync protocol to grab sync data, decrypt the records and store the data in local storage. We run queries against a locally stored copy of the data. | ||
=== Pros === | === Pros === | ||
| Line 29: | Line 29: | ||
* Local storage is not well deployed and limited | * Local storage is not well deployed and limited | ||
* Not all mobile browsers are capable of crypto and/or local storage, which leaves some out | * Not all mobile browsers are capable of crypto and/or local storage, which leaves some out | ||
* People would have to sync while having the app open | * People would have to sync while having the app open: no 'instant on' experience | ||
* No ability to sync in the background, the web app will have to be open | |||
== Crypto in Native Client == | == Crypto in Native Client == | ||