We're checking this condition twice (here and in the 42nd line) because it is possible that during AsyncStorage read the value was fetched and set from the service.

I'm not sure we should use AsyncStorage for this. We want to add support for feature flags to the web eventually, and by using something specific to React Native here, we'll make it harder to do that

Do you think it's a bad idea to use Redux for this?

The reasoning behind this decision was that I wanted for feature flags to be available as high in a tree as possible. Especially, I thought that they might be useful even for things that affect what we do with Redux - so Redux should depend on flags, not the other way around. If we store them in Redux, we would get cached values only after rehydration, so a lot of things might be hard to be configured by them. Also, the flags provider would be located deeper in a tree (probably could be somehow worked around).

On the web, we can use e.g. localStorage. This difference can be abstracted away and most of the logic still could be shared. The logic that will be different will be really simple - just read and write.

So overall, it seems worth having this difference because it makes flags more powerful. But if you disagree, I can change the implementation.

Okay, fair enough – thanks for explaining