When we talk about scalability of React Native, we talk about how much a developed app can handle. This could be, for example, the response time of the app, the amount of memory that the app can handle or what the battery drainage of the app is. Identification of the system’s key scalability challenges under a plausible scenario. The moderators of React Native state on their website that performance is a serious issue in React Native.

Key Quality Attributes React Native is a framework that builds native applications for iOS and Android using JavaScript, based on React, a JavaScript library1. React Native was created by Meta and is now an open source project, with over 2000 contributors. To ensure quality of the code React Native has a modular architecture and there are some rules and guidelines. Before getting in detail of quality assurance let’s take a look at the key quality attributes that React Native satisfies.

Main Architecture In the beginning React, the website focused framework on which React Native is based, was advertised as the V in the Model View Controller architecture 1. However, the phrase implies that some other technology should implement the Model and the Controller. This phrasing was something Facebook already discontinued and moved away from in 2013 1. A more applicable architecture pattern or style that really defines React Native is the Container / Component pattern 2.

React Native is an exciting framework made by Meta that enables developers to write an application in one language and deploy it to many different operating systems. It allows deployment mainly for Andriod and iOS, but also for tvOS and the web1. The framework was designed to increase productivity and allow developers to really focus on designing and developing their product, without having to worry about the ins and outs for each operating system with their specific programming languages2.