Timer measurements shall be managed by local storage.

[CreatorDodo]

1. This is because a timer must be shared among several tabs in one browser.

2. Data synchronization problems across tabs

   • chrome.storage.local operates asynchronously by default, but the changes are not automatically reflected on all tabs.
   • This means that updating data on one tab does not immediately reflect on the other.

3. Limit the number of requests

   • Chrome Storage APIs have write restrictions.
   • For chrome.storage.local, requests are restricted 1800 times per minute, while chrome.storage.sync is subject to stricter limits (120 times per minute).

4. State Management Difficulties

   • Data cannot be imported as synchronously as localStorage, and values must be imported asynchronously through chrome.storage.local.get.
   • Therefore, additional synchronization logic is required to perform state management in frameworks such as React and Vue.