Least Firebase Remote Config Cache Duration — an experiment

If you have used Firebase Remote Config, you probably have read from the documentation the below statement, and wonder if you could reduce the time

By default the cache expires after 12 hours, but you can change the cache expiration for a specific fetch by passing the desired cache expiration to the fetch method

Sometimes we might wonder why do we really need to cache it. There are some explanations, as mentioned by the below Firebase blog post

Firebase Remote Config loading strategies

So, why do we have all of this caching and throttling behavior in the first place? Well, partly it’s a way to ensure we can keep this service free, even if your app scales to millions upon millions of users. By adding in some well-behaved caching, we can make sure that our service can handle your…