We currently have an issue as per reported here whereby the app does not posses the ability of comparing the date since the last time a request was made and the current point at time.
For this reason, data stored on the client side ends up not being updated even when the API is actually providing recalculated currency rates.
A per the MDN document on the matter, the sessionStorage API provides an advantage that might help the presented issue to be addressed: data stored in the user's browser is removed when the window or tab that data is attached to is finished but is kept in case of multiple page reloads.
We are therefore going to A/B test this new approach and see if it has positive impacts on the performance of the application.
We currently have an issue as per reported here whereby the app does not posses the ability of comparing the date since the last time a request was made and the current point at time.
For this reason, data stored on the client side ends up not being updated even when the API is actually providing recalculated currency rates.
A per the MDN document on the matter, the
sessionStorageAPI provides an advantage that might help the presented issue to be addressed: data stored in the user's browser is removed when the window or tab that data is attached to is finished but is kept in case of multiple page reloads.We are therefore going to A/B test this new approach and see if it has positive impacts on the performance of the application.