I have inherited a vanilla React Native IOS/Android app that I would like to migrate to Expo. It’s important for me to move it to the managed workflow, even though there will be a considerable effort, because of the ease of publishing to both IOS and Android.
There’s a gist by Brent that gives a rough guide to migrating to Expo, you can see it here. He links a list of libraries that are a part of the Expo SDK and says:
Compare that with your package.json.
Here’s my package.json. I’m not sure how to review which libraries I can/can’t use in Expo. Is it that I can only use libraries in the list provided by Brent? Looking at the libraries in my package.json, which are the ones that I need to replace and do you have suggestion on what to use as a replacement?
I know that I can’t use react-native-firebase which is used only for notifications in this project, so I’ve already started research on migrating to Expo notifications.
But, for the rest I will need some help and suggestions.
A good rule of thumb to determine if a library is compatible with Expo is if you need to run react native link or make any native code modifications, it won’t work. As for the react-native-community libraries, you can compare with our API reference https://docs.expo.io/versions/latest/ to determine which ones we have pulled into our SDK.
Thank you. I actually need your opinion on this thread:
Basically, I want to know what will I lose if I migrate from managed to bare workflow in order to setup Stripe payments in IOS? I can leave this feature for the end of the development process, since it’s just one place where the user is paying for the subscription. In the meantime I will focus on getting the rest ready and investigate how’s the sanest way to setup payments in Expo that work on both mobile platforms.