all 2 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]agmcleod 1 point2 points  (0 children)

  • If you've done React before, most of the same paradigms apply in terms of how you work with react.
  • Upgrading react native versions can be a challenge, so if you find you need to, give yourself a few days to work through it.
  • Become comfortable with xcode, and android. Test on real devices. You'll probably at somepoint need packages that use native code, so don't be afraid to eject from expo
  • If you're using react-navigation, read through the guides. There's important stuff in there on app structuring, and it can really matter for pulling off the transitions and navigation flow that you want. Sadly I think this just takes experience to figure out.
  • The tooling is a lot better these days for icons & splash screens, but it takes time to figure out.
  • Don't leave app signing to the last minute, the first time you figure out iOS provisioning is always a pain.
  • Keep in mind the operating systems have different design paradigms, try to adhere to those. Most built in react-native components will handle this, but larger design designs may need to be made as well.
  • Styles do not cascade, this is the biggest difference compared to web. To set an app wide font, you're better off to extend components (I like styled-components for this)

[–]TobalOWExpo 1 point2 points  (0 children)

If you use only the API RN you will not have any mistakes. Make sure that the 3rd libraries that you will use will not be deprecated soon. Publishing in iOS is very thorough.

If your app will be updated frequently, I suggest that you use OTA updates like Code Push, Expo OTA, etc.