Tally this check-list before shipping your first React Native app

If you are new to mobile development with React Native, it is important to know the basic hygiene factors before publishing the app. The main distinctive of this framework is that React Native apps function similar to native apps. They are no different from apps built on Java, Objective-C or Swift. If you have newly developed a React Native-based mobile app, here is a simple checklist you should follow before publishing it on the Play Store or App Store.

Console longs can slow down your React Native app. You should scrub the logs on their way out. It is easy to find or replace them but some logs take a long time to construct and provide useful debugging. The easiest step is to simply remove them from the production build.

Developers usually implement a system that automatically resizes and optimises the assets. But to be 100% sure, squeeze and resize your images for optimal package size. Squoosh.app is a great tool to drag each asset to the site and for visual inspection and verification.

You may or may not have to add Android permissions as you built your app. React Native project does not start with zero permissions. By default, the Android section asks for following permissions: Internet, System Alert, Read phone state, read and write external storage, and check the license. You can remove the unnecessary permissions from these.

ProGuard helps in optimising, and shrinking your Android built. Once you turn on the ProGuard, you should run all your automated tests to check for issues. There is a reason why it’s not turned on by default. Hermes helps in getting you the byte code and improved startup time. It is recommended to turn on both ProGuard and Hermes.