Open yordis opened 7 years ago
Hey @yordis,
Expo is going to quickly break our tutorial as soon as we start adding interesting features or any third party libs that include native code, so I'd rather go the non-expo route for this tutorial.
Here is a shortlist of some of the packages that we already use in this tut:
From what I understand about Expo, using these packages wouldn't be possible and getting features found in these packages would require ejecting from Expo anyway. But I could be wrong!
Let me know your thoughts
@srtucker22 I wish I could say something but I am new into the ecosystem. Outside of my knowledge about it and I suggested for know what are your thoughts, specially that even react-native-app
use expo
at least in the latest one, that's how I found it 😄
gonna close this for now, but happy to reopen if expo meets our needs down the line
react-native-alphabetlistview # works with expo
react-native-fcm # cannot install, use import { Notifications } from 'expo'
react-native-image-crop-picker # import { ImagePicker } from 'expo'
react-native-loading-spinner-overlay # works with expo
react-native-vector-icons # import { FontAwesome } from '@expo/vector-icons'
@vko-online I am glad that you remember me this issue 😄
Yeah so far fcm
is the only issue and to be honest I am converting react-native-fcm
to Expo.Notifications and the workflow is so simple on Expo 😄
Oooo worth reopening. Thanks @vko-online 🍺
I'll investigate and maybe rework the tut to use Expo since it's so much easier to get started
since it's so much easier to get started
@srtucker22 yeah that was probably why I suggested 😅
Expo is not necesary
@hansfpc we could do everything in assembly, C or any other programming language is not necessary 😅
I actually tried converting the project to Expo pretty recently. However, I was running into all sorts of issues with dealing with the Expo environment -- pretty frustrating things like older versions of code running in the simulator -- that would make for really nasty first time user experiences. I also found setting up debugging with React Native Debugger to be nontrivial. So I'm sticking to a non-Expo track for now
@srtucker22 that can't be true, much easier with expo, and you can test on devices