Benefits of using this against just the <Image> component

[Naoto-Ida]

Doesn't the Image component have a caching mechanism?
I'm interested in boosting my app's performance, wondering if anybody had some insight into
this form of caching.

[sharq1]

@Naoto-Ida thank you for bringing this up - I was having problems with react-native-cache-image and I had no idea there is preload functionality for native Image component.
It looks to me, that with react-native-cache-image you get much more control over caching (by modifying consts in storageMgr.js), while you cannot do that with native Image.
I wonder whether if user hits 'Clear temporary data' system-wide it will clear preloaded images (native)? With react-native-cache-image it surely won't.

[Naoto-Ida]

Thanks for the info.

I'm kinda wondering how the performance benefits are with this caching.

[folivi]

does anyone have a code sample of the use the preload method?

[axe312ger]

Looks like react native can now do it on its own:
facebook/react-native@f7bcb3e

[vovkasm]

@axe312ger : As I can see, RN (at least latest tagged v0.36.0-rc.1 for iOS) do not deal with disk cache, it uses simple NSCache object to cache image data in-memory (RCTImageCache.m#L35). Moreover, it resets cache not only on memory warning, but also every time when user switched to other app (RCTImageCache.m#L47).

Or I am wrong?

In any case, personally I will use this component as a base for our application.