Issue: safari's storage limits are different than all other browsers. the data became so big that safari wouldn't allow it. Exceeds cache limits and the site will not function on mobile devices.
Solution: The solution was to break up the json payload into different objects (products, agencies, assessors, etc) and divide them in between local storage and session storage.
Considerations for future: This highlights one of the downfalls of json, it's very big because it precious space for field names. If this happens again in the future, we can see if there is any unused data and try to reduce long field names.
shivaalipour
commented
3 weeks ago
Issue: safari's storage limits are different than all other browsers. the data became so big that safari wouldn't allow it. Exceeds cache limits and the site will not function on mobile devices.
Solution: The solution was to break up the json payload into different objects (products, agencies, assessors, etc) and divide them in between local storage and session storage.
Considerations for future: This highlights one of the downfalls of json, it's very big because it precious space for field names. If this happens again in the future, we can see if there is any unused data and try to reduce long field names.