He has two react-native courses, if it’s the more recent one, then it includes expo.
Expo has upgraded recently. The biggest difference is the exp.json (kind of the settings file for your expo projects config) file is now inside of app.json (which is the more “standard” place for configuration in a create-react-native-app).
Expo typically has an upgrade guide in their blog posts:
That larger change happened in v18, I think the course is either v16 or v15? Not sure if the course was updated or not:
Also, join the expo slack channel-- they’re super helpful and can probably help you get by any issues in the course material.
The other big update is react-navigation (used in the course). The options object that you pass in to configure a route is slightly different, but if you check out both the course Q & A forum and also the react-navigation docs, you shouldn’t get too hung up there. It’s not major, some settings that used to be nested objects like
are now a single property
and things like that… hope that helps.
As for using Meteor, I have a Meteor back-end with graphql. Then my webapps and react-native apps connect with apollo-client. But if you want pure meteor, you should be able to use the “react-native-meteor” package or maybe the “meteor-client-bundle” (I think is the name). Spencer C. has a lot of blog posts on using meteor with react-native, so once you get the hang of basic expo + react-native, figuring out how to use meteor shouldn’t be a major undertaking. You basically point your rn app to the websocket route. The only downside is I never figured out how to run meteor locally and have expo hit the app… I always pushed it to galaxy and had the app pointed to that URL. There is probably a way to hit your app locally though.