// the take
A drop-in replacement for React Native's Image component that wraps SDWebImage on iOS and Glide on Android to fix the flickering and cache-miss problems people hit with the stock component. It's for anyone shipping image-heavy RN screens (feeds, grids, galleries) who needs real control over caching, preloading, and load priority instead of hoping the server's cache headers behave.
It leans on two mature, battle-tested native image libraries instead of reinventing caching logic in JS, which is the right call for something this performance-sensitive. The cache API is unusually well thought out for a community library: separate memoryCache/diskCache toggles, a cacheKey escape hatch for signed URLs that change but represent the same image, and three cache modes (immutable/web/cacheOnly) that map to real-world needs instead of one-size-fits-all behavior. Format coverage is genuinely broad — AVIF, animated WebP/APNG, SVG, HEIC, even iOS photo-library URIs — and the responsive source-array feature (pick the closest size per view) is a feature most RN image libs don't bother with. Downsampling and HDR dynamic-range controls show someone cared about actual memory behavior on large photos, not just making images appear on screen.
The jump to requiring React Native 0.83+, the New Architecture, and React 19 is a hard wall — any app not yet migrated has to stay pinned to the old v9 branch indefinitely, which fragments the user base and means issues/fixes may not land on both lines. Native code means Expo users lose Expo Go entirely and need a custom dev build, and Android apps with their own Glide AppGlideModule can silently break unless you know to read the integration docs first. There's no way to evict a single cached image by key — only nuke the entire memory or disk cache — which is a real gap if your backend needs per-image invalidation beyond bumping cacheKey. Running two independent native caching stacks (SDWebImage, Glide) also means platform-specific quirks are baked in by design: expect caching edge cases (e.g. 'web' cache mode handling compressed responses) to behave differently on iOS versus Android.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →