Skip to main content

React Native init vs Expo

At the initial stage, you must use one of the starters. The main competing starters are React Native CLI and Expo, taking advantage of one over the other.

In the official React Native documentation, from the Getting Started section , we learn that we have two ways to launch a mobile app: expo and react-native cli. Windows and Linux users, and most of them, go to the Building Projects with Native Code tab and select Target OS: iOS, they encounter an inscription that sends them to the Expo starter, but before putting Expo, I suggest you read the information in the following table:

Namereact-native initExpo
You can add your own modules written in Java / Objective-CYesNo
Weight of a standard Hello World application5mb25mb
Requires Android Studio and X-Code to run projectsYesNo
Fonts need to be imported manually in X-CodeYesNo
Provides JS API out of the box like Push-Notification, Asset ManagerNoYes
You can use libraries that use native code in Objective-C / JavaYesNo
Application sharing (via QR code or link)NoYes

If you nevertheless chose Expo, then it is a matter of time that you will encounter its limitations and want to use native modules, then for this you will have to do detach. From my own experience and from many familiar colleagues, I know that detach is done crookedly, which means that you will have to refactor a bunch of mistakes. For me, Live Reloading in the simulator has become a faithful friend, but in Expo it constantly breaks and it constantly has to be restarted, which makes the development process painful.

Expo is full of dependencies that you personally will not need for the project, but you will have to wait additional time until your JS bundle with excess garbage is collected, and after this garbage Expo will add to your release .apk and .ipa on your mobile devices. clients, due to which the application launch time will increase, and along with it, the application development time increases, since the JS bundle has to be collected very often.

Each native library that you connect yourself in the react-native cli must be checked, since the library is different from the library, and at the same time, on the other hand, third-party libraries are easier to fork, change or even rewrite taking as a basis in your project, in Expo with this explicitly more difficult.

If the Expo components would work with the react-native cli, then there would be no problems, and so I observe a chasm in starter compatibility and the saddest thing is that Expo will start throwing you its additional errors related to its infrastructure. At Expo, React Native is almost always not the freshest version. At the time of this writing, Expo SDK 30.0.0 contains the React Native version 0.55.4, and the current one at the moment is 0.57. For example, the debounce function does not work, on Android, in debug mode (debug js remotely enabled) for the TextInput component, which means that you will always lag behind new improvements in the React Native libraries.

Of course, not everyone has the opportunity to buy a Mac, but benchmarking two starters and my 2.5 year experience with both shows that developing an application with react-native cli, even only from Windows on Android, is a better investment in a more professional solution. since React-Native uses the same codebase for iOS and Android.

I hope for your feedback, thanks to which the information in this article will be corrected and supplemented.

It's time to put React Native Cli on your computer and move from theory to practice.

Questions#

What is the preferred React Native starter?

  1. Expo
  2. React Native Cli

To see how well you learned this lesson, take the test in the mobile application of our school on this topic or in the telegram bot.

Sumerian school

Contributors โœจ#

Thanks goes to these wonderful people (emoji key):


Dmitriy Vasilev

๐Ÿ“–๐Ÿ’ฒ

Become a Patron!