Feature: Full client-side data caching

[faisalnjs]

If no cached data in storage, load all bulk_load data and locally set a timestamp marker of the current datetime.

If there is cached data, request a bulk_load of all added, deleted, and edited data from the stored timestamp (last fetched) up until the current datetime. Then, locally update the timestamp marker of the current datetime. Then, update the stored cached data to reflect the newly fetched added, deleted, and edited data. After, refresh the screen (run init functions) using the new cached data.

[lipskyr]

This is very exciting!
(Very very)

I wanted to make sure that even with caching, there would still be an "responsiveness" to changed answers. Like if a student is marked right but later that right answer is changed to wrong, this change would be picked up upon and the student's answer status would change to wrong and an "unread" notification would be added.

[faisalnjs]

Yes, the same functionality will remain. The only thing that is changing is the way data is received and stored.