Lessons Learned Building Large-Scale React Native Apps

DZone 's Guide to

Lessons Learned Building Large-Scale React Native Apps

A developer team lead reflects on what React Native has brought to his team and why they love coding in this popular framework.

· Web Dev Zone ·
Free Resource

We've built a number of great mobile applications on React Native. We recently wrapped up one of the largest we've done here at SmartLogic — largest in terms of user base, navigation depth, redux state, and sagas. With every app, our list of best practices and little tricks that work well for us grows, but with the larger apps, there are some additional best practices we've recently settled on.

We took some time to reflect back on some of the best lessons we've learned after completing over a half dozen React Native apps. Here are our top four takeaways and lessons learned from our experiences building large React Native applications.

Develop iOS and Android at the Same Time

Not every React Native app we build targets both Android and iOS (yes, we like React Native so much we use it even if we don't need its cross-platform capabilities). When we are expecting to target both platforms, it is extremely important that we develop styling and platform specific functionality for both at the same time. Going back and adjusting styles per platform later is asking for frustration as a fix for one breaks the other. In our experience, it is more cost effective to style for both platforms at the same time, rather than one and then the other.

What Version Is the App? (Build ≠ Release ≠ Semantic Version)

Remember, what you list as the version in the various app stores has nothing to do with what version your app thinks it is. When building an app to replace an existing one, clear version management is exponentially more important, but will also quickly become important if your app takes off and becomes popular. It is also extremely important because, hopefully, you are continuing to iterate on your app.

Let's clearly define three terms:

  • Release - A compiled app binary that you are going to send to App Store Connect or Google Play.
  • Build - The build number (or Version Code in Android) must always be increasing, so increment this every time you push to the store (a release), no matter what you are trying to accomplish (test release or public release).
  • Semantic Version - The public-facing version number, which can be set in a few different places, in the store its just a vanity, more importantly, in your app's code, it should know its own semantic version number.

The lesson here is to make sure the internal semantic version number understood by the app is correct, and you'll get some big wins.

First is that your crash reporting will correctly identify the version that had an issue, beyond just knowing the build number. As I mentioned, the stores will require that your build number and release number are increasing, but we find that a semantic version number is much easier to discuss and understand what features have been enabled in that release. Second, the latest release report from Firebase (more on Firebase later) is super useful to measure adoption, and it relies heavily on the semantic version number your app has coded in it. Finally, you want the app to understand its version number, and show the user somewhere in the app so that they can refer to it during support calls.

Managing the semantic version number and build version number was not as simple as we expected. Fastlane (more on this later) helps, but it can't increment the semantic version numbers for all platforms, or do so necessarily in the way you want it to. Here is the approach we took:

  • Increment the build number every time we push to a store, including alphas and betas.
  • Before every public release to the stores, increment the semantic version number.
  • If it is just bug fixes, increment the patch version number.
  • If you add enough major features or changes that you want to increment the major or minor version numbers, then move those forward.

This way your build number will march on, making updates easy to track, and you'll have a new semantic version in the stores so you can measure crashes and rollouts easily.

Descriptive and Organized Code

For our most recent React Native project, we used a very strict code review policy; we ensured that a developer unfamiliar with the code read and reviewed it. Most of the time, that developer was me. I've got a great team, and they are doing amazing things with React Native (as I've outlined in this post already) and I'll be the first to admit, I'm not as fluent in React Native as they are. The code the team wrote, especially with smart use of Redux and Saga, was extremely readable. No matter where in the app they were working, I was able to understand what was being built, and how it was expected to work, even with minimal context.

This has been even more apparent as we've had a few bugs to squash or additional features to add; thanks to our well organized and super clear code, it has been easy for me to jump in and help out. This really helps solidify my belief that this is a great direction for mobile development because ultimately finding good developer talent, and making sure they can dive in quickly, is a big deal. React Native has helped empower our team to excel in mobile development and bring in new talent who are able to become productive quickly.

Invaluable Tools and Processes

There are a number of tools we used that really helped with our processes:

  • Sagas - We've used this in various projects before, every time we are better organized and they have even more value in describing the flow of data and logic within the app.
  • Fastlane - We used this to automate builds, and it worked really well.
  • React Native Debugger - This desktop app is crucial in the development of the mobile app if you're using Redux and Saga.
  • Firebase - This is a great set of tools, and was very easy to integrate for analytics, crash reporting, rollout monitoring, remote configuration, and push notifications.

In Conclusion

We continue to love React Native. Sure there are some pain points, version conflicts, build issues that crop up, especially with operating systems or Xcode updates. Ultimately though, the reuse of most of the styling, and all of the business logic is really a huge win. On top of that, the development cycle is much faster when just reloading JavaScript code, rather than doing a full recompile of the app. The final product and performance is great, and we will continue to use React Native to build successful mobile applications.

web dev ,react native ,mobile application development ,cross-platform development

Published at DZone with permission of Dan Ivovich , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}