Games Strategy

Should We Use React Native?

Should We Use React Native?

I steadily get requested by prospects and shoppers if they need to use React Native for his or her subsequent huge venture. React Native, initially began by Fb, is a cross platform framework just like the React javascript framework that guarantees to permit devs to put in writing code as soon as, in Javascript, that may work on each iOS and Android. The reply to that query, in pure advisor converse, is “it depends”. You are able to do tons with React Native. It’s straightforward to select up and roll an app, and you may obtain just about something that you might in a local app.

However in case you are betting your organization or your product on the inspiration of React Native, I’d assume once more, particularly should you’re in search of deeper hardware integration. This five-part collection of posts by the engineering group at Airbnb brilliantly describes the rationale they determined to chuck React Native after 2+ years of funding. The reply, fairly merely, is that it added an excessive amount of complexity and didn’t permit Airbnb to realize their objectives. Let’s see why.

The promise of React Native for most individuals is value and time financial savings. Having a single code base for each iOS and Android in concept enables you to write as soon as for each platforms, which (once more in concept) means fewer assets (one developer can cowl each platforms) and quicker time to market (getting two platforms out with the trouble of 1 developer). The truth, nevertheless, is far totally different.

It’s helpful to evaluate Airbnb’s unique motivations and objectives in shifting from native to React Native. They have been already utilizing the React framework for his or her net merchandise and hoped to leverage that acquainted framework onto their cellular merchandise, which have been exploding in reputation and required a quickly growing variety of engineering assets. So their objectives have been the next:

  • Do extra with much less and transfer quicker
  • Hold high quality excessive
  • Write code as soon as for a number of platforms
  • Hold builders completely satisfied!

So did they hit their objectives? Let’s begin with what labored properly, which have been a number of issues.

The great: velocity & uniform code

Finally 95-100% of their code utilizing React Native supported each iOS and Android, with solely a small proportion being platform-specific. Additionally they word that engineers got here in control shortly utilizing this framework, and that the construct cycle was a lot quicker — you are able to do a React Native construct in 15 seconds versus 15 minutes for native builds (particularly on XCode) — which is an enormous benefit over time.

Moreover, React Native pressured Airbnb to undertake a design language for his or her merchandise that might be constant between platforms. That self-discipline helped their builders. Additionally, as a result of React Native is rooted in Javascript, that meant they might make the most of the various open-source Javascript libraries out there.

The Airbnb group was usually happy with their means to construct absolutely anything with React Native, at good ranges of productiveness, and with code that hit a really excessive % of being shared throughout platforms.

However the listing of issues that didn’t go so nicely is longer, and rather more vital.

The dangerous: debugging & cross-platform compatibility

The primary is that React Native, although it’s been out for three years, continues to be comparatively new and shifting quick as a platform. Simply examine that to iOS or Android improvement, which have 10+ years of concentrated improvement. That it’s new isn’t essentially horrible, however a fast-moving platform signifies that points crop up in methods that aren’t predictable or straightforward to determine. The Airbnb workforce spent a whole lot of time sustaining their very own fork of React Native due to the necessity to repair points. A fork is an entire copy of the grasp supply code repository, which mitigates the reliance on the unique supply. However as a result of that they had their very own fork, then the method of holding React Native up-to-date turned actually exhausting, as a result of Airbnb’s customizations needed to be regularly merged in.

The subsequent huge drawback outcomes from the character of React Native structure (and all cross platform frameworks for that matter). React Native supplies an execution setting for Javascript code, which bridges to native code. By its very nature, bridging provides an incredible problem to debugging. The place did the bug happen? Within the native code or within the React Native code? Stack traces don’t move throughout the bridge, so if there’s a problem in native code it’s very difficult to debug. This is probably not an issue sooner or later because the framework evolves, however builders face it right now continually; and actually, the problem of debugging was referred to as out pretty steadily by the Airbnb workforce.

Really helpful for You

Webcast, December 18th: Optimizing Buyer Engagement with Consumer Intent

Once more, the complexity of React Native operating on prime of native code led to points. Delicate variations within the Android setup and configuration vs iOS setup and configuration regularly made it difficult to debug platform-specific points. This acquired additional difficult for the Airbnb group by the problem of debugging in developer environments — e.g., with a simulator — versus in a deployed setting. The outcomes didn’t match. Moreover, the Airbnb group used Bugsnag to seize points, however Bugsnag didn’t all the time play nicely with React Native. This, once more, added extra challenges to their debugging.

In abstract, bridging between React Native and native code turned out to be fairly onerous to debug, however in delicate ways in which have been onerous to trace down. A lot of that problem comes from the inconsistency of how knowledge is handed forwards and backwards via the bridge. Seems, to debug successfully it’s a must to be an skilled not simply in iOS and Android improvement, but in addition React Native. Therefore, the promise of “write once deploy twice” is just shattered. The truth is, one might surmise from Airbnb’s expertise that it’s truly extra work to help React Native as a third surroundings.

The ugly: the failed promise of Javascript & efficiency

The promise of React Native is steadily tied to the plethora of open supply libraries: good in principle, however the actuality is that a lot of the libraries that Airbnb tried to make use of had points on one cellular platform or one other. Libraries are sometimes written with native bridging, and the bridging is simply nearly as good because the developer who wrote it initially. Because of this this developer needs to be proficient, or an professional, on each iOS and Android. In fact, most builders solely have experience on one or the opposite so, but once more, a supply of platform-specific points come into play. Having to dive this deep to repair all these points shortly erode the advantages of React Native altogether.

Bear in mind, Javascript by its nature shouldn’t be a typed language, so it’s straightforward for nasty little bugs to be launched unwittingly. This elementary concern with Javascript signifies that refactoring was at occasions extremely daunting. It’s not straightforward to make massive modifications throughout a code base when conflicts in naming typically simply lead so to confusion. (As a aspect observe, Typescript works with React Native as nicely, and would in all probability scale higher than uncooked Javascript.)

And eventually, we come to the elephant within the room: efficiency points. Begin up time for React Native is heavy and sluggish. All the runtime setting for React Native must be initialized earlier than issues can begin to occur. That’s why the Airbnb staff needed to make the most of native code for launch screens, in an effort to make their app as responsive as may be through the essential moments when customers might simply be turned off by delays.

It’s protected to say that the efficiency of native code is all the time going to be higher than that of a framework that rides on prime. It’s all the time been that approach. That’s not React Native’s fault, nevertheless it’s the truth of the state of affairs.

Rounding out the listing, listed here are the opposite huge technical issues that Airbnb identified:

  • There’s no help for 64-bit apps on Android with React Native, so you’ll be able to’t benefit from the efficiency capabilities of the newest hardware.
  • They weren’t capable of absolutely make the most of gestures due to vital variations in gesture dealing with architectures on iOS vs Android.
  • There are vital holes in React Native’s Accessibility help.
  • There have been main issues upgrading variations of React Native because it advanced.

Don’t overlook the expertise

After which there’s the difficulty of expertise. As famous by Airbnb, to help React Native completely, you actually need experience in iOS, Android, and React Native. It’s not straightforward to seek out engineering expertise that is aware of two of these three talent units, not to mention all three. In fact, this drawback surfaced repeatedly in debugging points.

And right here’s the place I’ll add from my very own expertise recruiting expertise — the expertise pool for individuals who know native Android or iOS improvement is simply a lot greater than for many who know React Native. This isn’t an insignificant element for managers to remember when deciding to go together with this framework or not. Want proof? Swift and Kotlin are extremely ranked on GitHub’s listing of lively programming languages, and each Java and Swift are into the highest 10 of Tiobe index of recognition. And naturally, Swift is a extremely popular and liked language.


I’ll come again to what I stated earlier: React Native could also be applicable in plenty of instances, and as a consultancy Rocket Farm will use it when it is sensible. In truth of all of the cross-platform options on the market, React Native is our favourite. However in case you are betting your product and even your organization on an structure, going native is the best way to go. Attain Native is extra complicated, more durable to check and debug, and has actual trade-offs when it comes to efficiency. Complicated organizations, as Airbnb discovered, will discover it more durable to employees and keep over time on such a framework.

Yearly like a drumbeat, Apple and Google enhance and broaden what their core platforms can do. Yearly, frameworks like React Native should scramble to catch up. I’d quite keep near the dominant gamers within the ecosystem and maintain issues easy. We had shoppers get completely torched by Fb’s determination to desert one other fashionable framework referred to as Parse 2 years in the past. I by no means need to put a shopper in that place once more.

Word: particular because of Matt Graziano for his considerate evaluate and feedback on this publish. Matt is a robust proponent of React Native and we don’t all the time agree. Matt is the founding father of Ambrao, a know-how consultancy that makes a speciality of net and cross-platform cellular app improvement for early stage corporations trying to get their merchandise to market.