Hey, thanks for rhe response @samee!
I don’t think any of that helps me though. The first link is about something else and the second link is not a true cache, it’s all in memory at runtime, and I have to manage it myself in a very spaghettified manner all over my app.
The way caching works in browsers is your web server can specify a cache-control header to set a max-age for any GET response and the web browser will know to keep that thingy in the file system, whether it be an image, html, or whatever. (There are other headers you can use but they aren’t as good, or you can use E-tags which fulfill the same role of caching but in a different way).
In any case, caching is a pretty robust thing in web browsers and can help the scalability and UX if your system a lot. Browser cache is very transparent to use, since you just set a response header and the browser knows what to do - save the files locally after the first response, and load them from local file system next time they are requested if the expiration date hasn’t passed. I’m looking for something similar in React Native. I’m pretty sure it doesn’t exist though.