// the find
invertase/react-native-firebase
🔥 A well-tested feature-rich modular Firebase implementation for React Native. Supports both iOS & Android platforms for all Firebase services.
The de facto standard for using Firebase in React Native apps. It wraps the native Firebase SDKs (not the JS web SDK) via a bridge layer, giving you access to the full Firebase suite—Auth, Firestore, FCM, Crashlytics, Analytics, etc.—with a TypeScript-first API that deliberately mirrors the Firebase Web SDK. If you're building a React Native app on Firebase, this is almost certainly what you're using.
- Modular package structure means you only install what you need—no single monolithic dependency bloating your bundle with services you don't use.
- Uses native Firebase SDKs under the hood rather than the JS web SDK, so you get proper offline persistence, background messaging, and platform-native behavior that the web SDK can't provide in a native app context.
- Has a CI-enforced type comparison script (.github/scripts/compare-types) that diffs the library's TypeScript types against the official Firebase Web SDK types, which is an unusually disciplined approach to keeping the API surface in sync.
- E2E test coverage runs against real Firebase services (emulators + actual CI Firebase project) for most modules, not just unit tests with mocked bridges—this catches real integration regressions.
- Native module setup is genuinely painful: each package requires manual Podfile/Gradle changes, google-services.json placement, and platform-specific steps. Even with auto-linking, new contributors regularly spend hours on setup issues, and the GitHub issues are full of build failures.
- Breaking changes between major versions have historically been significant (there are migration guides for v6, v22, v23, v24, v25), and keeping up with both RN upgrades and Firebase SDK upgrades simultaneously creates a version matrix problem—your exact combination may be untested.
- The library is maintained by a small commercial team (Invertase); when Firebase releases a new feature, there's often a meaningful lag before it lands here, and some modules (ML, Dynamic Links which is actually deprecated by Google) are poorly maintained or frozen.
- No web/Expo Go support for most modules—if you're using Expo managed workflow you're either stuck with the Firebase JS SDK for certain features or forced to eject, which the docs understate how disruptive this can be.