Popular posts

re: not always being able to find an Expo module to do what you want to do. We're trying to solve this issue by squeezing it from both sides. (a) by continuing to support "detach" and make it better so you can write native code or react-native link native code whenever you need to. and (b) making it possible to do almost anything you want to do with just JS. For example, by continually working on improving our multimedia support so you don't need to install special modules to deal with sound or video.

For Firebase in particular, we're looking at a bunch of different options. Here is a starter snack for using the Firebase Realtime database: https://snack.expo.io/HJ1Wjg95Z

We also are looking at adding react-native-firebase in to Expo directly but there are some reasons that might not work well.

1.) When you detach and use ExpoKit, you retain most of the Expo SDK (like Expo Graphics, Audio, and Camera) that doesn't depend on Expo services. So if you use any of these APIs after detaching, you'd still want to use ExpoKit.

You also can use Native Directory (https://native.directory) to find libraries that are compatible with Expo. Library authors indicate which platforms they support, making it easier for developers to filter by libraries that support Expo.

2.) We would like to support several Firebase features if we can do so in a useful and sustainable way that keeps Expo APIs stable over time. Some features like App Indexing are also more challenging to implement because they are only possible in standalone apps, in contrast with the Expo client. (Since you mentioned it, you may find Expo's support for Admob useful: docs.expo.io/versions/latest/sdk/admob.html.)