This website uses cookies to better the user experience of its visitors. Where applicable, this website uses a cookie control system, allowing users to allow or disallow the use of cookies on their computer/device on their first visit to the website. This complies with recent legislative requirements for websites to obtain explicit consent from users before leaving behind or reading files such as cookies on a user’s computer/device. To learn more click Cookie Policy.

Privacy preference center

Cookies are small files saved to a user’s computer/device hard drive that track, save, and store information about the user’s interactions and website use. They allow a website, through its server, to provide users with a tailored experience within the site. Users are advised to take necessary steps within their web browser security settings to block all cookies from this website and its external serving vendors if they wish to deny the use and saving of cookies from this website to their computer’s/device’s hard drive. To learn more click Cookie Policy.

Manage consent preferences

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookies list
Name _rg_session
Provider rubygarage.org
Retention period 2 days
Type First party
Category Necessary
Description The website session cookie is set by the server to maintain the user's session state across different pages of the website. This cookie is essential for functionalities such as login persistence, ensuring a seamless and consistent user experience. The session cookie does not store personal data and is typically deleted when the browser is closed, enhancing privacy and security.
Name m
Provider m.stripe.com
Retention period 1 year 1 month
Type Third party
Category Necessary
Description The m cookie is set by Stripe and is used to help assess the risk associated with attempted transactions on the website. This cookie plays a critical role in fraud detection by identifying and analyzing patterns of behavior to distinguish between legitimate users and potentially fraudulent activity. It enhances the security of online transactions, ensuring that only authorized payments are processed while minimizing the risk of fraud.
Name __cf_bm
Provider .pipedrive.com
Retention period 1 hour
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to support Cloudflare Bot Management. This cookie helps to identify and filter requests from bots, enhancing the security and performance of the website. By distinguishing between legitimate users and automated traffic, it ensures that the site remains protected from malicious bots and potential attacks. This functionality is crucial for maintaining the integrity and reliability of the site's operations.
Name _GRECAPTCHA
Provider .recaptcha.net
Retention period 6 months
Type Third party
Category Necessary
Description The _GRECAPTCHA cookie is set by Google reCAPTCHA to ensure that interactions with the website are from legitimate human users and not automated bots. This cookie helps protect forms, login pages, and other interactive elements from spam and abuse by analyzing user behavior. It is essential for the proper functioning of reCAPTCHA, providing a critical layer of security to maintain the integrity and reliability of the site's interactive features.
Name __cf_bm
Provider .calendly.com
Retention period 30 minutes
Type Third party
Category Necessary
Description The __cf_bm cookie is set by Cloudflare to distinguish between humans and bots. This cookie is beneficial for the website as it helps in making valid reports on the use of the website. By identifying and managing automated traffic, it ensures that analytics and performance metrics accurately reflect human user interactions, thereby enhancing site security and performance.
Name __cfruid
Provider .calendly.com
Retention period During session
Type Third party
Category Necessary
Description The __cfruid cookie is associated with websites using Cloudflare services. This cookie is used to identify trusted web traffic and enhance security. It helps Cloudflare manage and filter legitimate traffic from potentially harmful requests, thereby protecting the website from malicious activities such as DDoS attacks and ensuring reliable performance for genuine users.
Name OptanonConsent
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonConsent cookie determines whether the visitor has accepted the cookie consent box, ensuring that the consent box will not be presented again upon re-entry to the site. This cookie helps maintain the user's consent preferences and compliance with privacy regulations by storing information about the categories of cookies the user has consented to and preventing unnecessary repetition of consent requests.
Name OptanonAlertBoxClosed
Provider .calendly.com
Retention period 1 year
Type Third party
Category Necessary
Description The OptanonAlertBoxClosed cookie is set after visitors have seen a cookie information notice and, in some cases, only when they actively close the notice. It ensures that the cookie consent message is not shown again to the user, enhancing the user experience by preventing repetitive notifications. This cookie helps manage user preferences and ensures compliance with privacy regulations by recording when the notice has been acknowledged.
Name referrer_user_id
Provider .calendly.com
Retention period 14 days
Type Third party
Category Necessary
Description The referrer_user_id cookie is set by Calendly to support the booking functionality on the website. This cookie helps track the source of referrals to the booking page, enabling Calendly to attribute bookings accurately and enhance the user experience by streamlining the scheduling process. It assists in managing user sessions and preferences during the booking workflow, ensuring efficient and reliable operation.
Name _calendly_session
Provider .calendly.com
Retention period 21 days
Type Third party
Category Necessary
Description The _calendly_session cookie is set by Calendly, a meeting scheduling tool, to enable the meeting scheduler to function within the website. This cookie facilitates the scheduling process by maintaining session information, allowing visitors to book meetings and add events to their calendars seamlessly. It ensures that the scheduling workflow operates smoothly, providing a consistent and reliable user experience.
Name _gat_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _gat_UA-* cookie is a pattern type cookie set by Google Analytics, where the pattern element in the name contains the unique identity number of the Google Analytics account or website it relates to. This cookie is a variation of the _gat cookie and is used to throttle the request rate, limiting the amount of data collected by Google Analytics on high traffic websites. It helps manage the volume of data recorded, ensuring efficient performance and accurate analytics reporting.
Name _ga
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga cookie is set by Google Analytics to calculate visitor, session, and campaign data for the site's analytics reports. It helps track how users interact with the website, providing insights into site usage and performance.
Name _ga_*
Provider rubygarage.org
Retention period 1 year 1 month 4 days
Type First party
Category Analytics
Description The _ga_* cookie is set by Google Analytics to store and count page views on the website. This cookie helps track the number of visits and interactions with the website, providing valuable data for performance and user behavior analysis. It belongs to the analytics category and plays a crucial role in generating detailed usage reports for site optimization.
Name _gid
Provider rubygarage.org
Retention period 1 day
Type First party
Category Analytics
Description The _gid cookie is set by Google Analytics to store information about how visitors use a website and to create an analytics report on the website's performance. This cookie collects data on visitor behavior, including pages visited, duration of the visit, and interactions with the website, helping site owners understand and improve user experience. It is part of the analytics category and typically expires after 24 hours.
Name _dc_gtm_UA-*
Provider rubygarage.org
Retention period 1 minute
Type First party
Category Analytics
Description The _dc_gtm_UA-* cookie is set by Google Analytics to help load the Google Analytics script tag via Google Tag Manager. This cookie facilitates the efficient loading of analytics tools, ensuring that data on user behavior and website performance is accurately collected and reported. It is categorized under analytics and assists in the seamless integration and functioning of Google Analytics on the website.

When to Choose React Native for Building a Mobile App and When to Avoid It

  • 127003 views
  • 10 min
  • Aug 20, 2018
Mykola V.

Mykola V.

IOS/Android Developer

Anastasia D.

Anastasia D.

Copywriter

Share

Cross-platform development has become a great alternative to fully native mobile app development. Following the native mobile development approach, you create separate apps for Android and iOS. The cross-platform development allows you to cut expenses and save time by using the same code across both platforms. The React Native framework is a rising mobile solution and is considered the future of cross-platform mobile app development.

In this article, we cover the benefits of using React Native for cross-platform mobile development and also tell you when it’s not a good choice.

React Native is an open-source framework that allows you to build a mobile app with only JavaScript. It was introduced by Jordan Walke, a Facebook software engineer, as a new technology for simpler development and a better user experience. The main distinctive of this framework is that React Native apps function just like native apps. They don’t differ from apps built on Java, Objective-C or Swift and they use the same UI building blocks as native iOS or Android apps. But with React Native, building a mobile app is much faster and less expensive.

Why to choose React Native
The statistics show the reasons why more and more developers choose React Native for the cross-platform development

Let’s look at the advantages and some challenges of using React Native to develop a mobile app.

Advantages of React Native

#1 Community matters

React Native is an open-source platform. That means all documentation related to this technology is open for everyone and is available for free to everyone in React Native community. There’s a great advantage to using a community-driven technology. For example, if you face any issue related to React Native development, you can get help from community experts or find information online.

Another benefit of working with an open-source platform is recognition for writing code. Developers can share their experiences and create portfolios, which encourages them to write better code. For example, after learning something new while working with React Native, a developer can share their experience with the GitHub React Native Community, get feedback, and collaborate with other members.

Apart from the GitHub community, React Native is also greatly supported by Facebook. Facebook developers have set up a special forum for long-form conversation where other developers can share best practices and solutions. In addition, there’s a Reactiflux Chat if you need to get an immediate answer to any question.

#2 Reusable code & pre-built components

This is probably the most important advantage of React Native. With the convenience of this framework, developers don’t need to build a separate mobile app for each platform, as almost 90 percent of React Native code can be reused between iOS and Android.

For companies and organizations that are considering building a mobile app, React Native is a perfect solution that can cut the time and cost in half. Moreover, if a company already has a web app written in React, much of this code can be reused for building a mobile app.

An open-source library of pre-built components in React Native greatly speeds up the process of mobile app development. It’s likely that someone already has written the code for some functions you need to deploy in your app and that you can use it for free.

Walmart decided to revise their mobile app in React Native as they needed to improve app performance as quickly as possible. In this case, using React Native was the most beneficial decision as 96 percent of the code was shared between iOS and Android. React Native allowed the team of developers to improve app performance for both platforms quickly.

Why to choose React Native framework
The React Native is rapidly gaining popularity over other frameworks

#3 Simplified UI

React Native is all about the mobile UI. If we compare this framework to AngularJS or MeteorJS, we find that it looks more like a JavaScript library than a framework.

It’s important to create a sequence of actions when building a mobile app, and React Native makes an implementing order just perfect. In addition, user interfaces designed in React Native are more responsive, decrease load time, and provide a smoother feel.

#4 Third-party plugin support

The React Native framework is still advancing, so it might lack some components in the core framework. To fill this gap, React Native provides two types of third-party plugins: native modules and JavaScript modules.

For example, if you need to add Google Maps or Google Calendars to your basic app functionality, React Native allows you to link any plugin with a native or third-party module. Among the most prominent third-party plugins for React Native are React Native Selectme, React Native Vector Icons, React Native Router Flux, React Native Gifted Spinner, React Native Modalbox, and React Native Drawer.

#5 Modular architecture

Modular programming is a software design technique that separates the functionality of the program into several independent and interchangeable blocks called modules. There are a couple of advantages to this technique: it provides flexibility within the development team as developers can delve into each other’s projects if needed and it makes it extremely easy to generate updates. React Native intuitive modular architecture helps developers greatly by providing the ability to upgrade and update applications quickly. It’s also possible to reuse modules that work both with web and mobile APIs.

#6 Live and hot reloading

Live and hot reloading are not the same features in React Native application development. Let’s first define the difference between these two options.

Live reloading reads and compiles a file in which changes were made by a developer and then provides a new file to the simulator, which automatically reloads the app from the starting point.

Hot reloading is based on Hot Module Replacement (HMR) and was introduced after the first reloading option. It features the same sequence of actions, but when you press Ctrl + S to save changes, an HMR intermediator inserts the updated files into the required place while the app is running. One of the biggest advantages of hot reload is the ability to make changes in the source code so they can be seen without the need to recompile the app. If a software engineer has two open windows (one with the code and another with the app screen), for instance, they can see the result on the app screen immediately after applying changes in code. Let’s look closer at how this option works in the video below.

#7 Declarative coding style

Declarative programming describes what the program must do rather than how to do it, which is the opposite of imperative programming. A declarative coding style makes React Native code extremely flexible and understandable for developers. It’s also profitable when a developer needs to jump into a new project and assimilate quickly. The declarative style simplifies coding paradigms and the coding process, resulting in code that’s easier to read for both the system and developers. A developer can simply look at the code and understand it due to the brilliant UI.

#8 Plenty of ready-made solutions and libraries

The React Native framework has an impressive list of ready-made solutions and libraries that greatly facilitate mobile development. Among the huge number of React Native libraries, we list some of the most useful ones below.

For example, testing libraries help software engineers write bug-free and flawless code. The most famous and versatile testing tools are Jest, Enzyme, Chai, and Mocha.

For successful type checking, there are tools such as PropTypes and Flow, while ESLint is a perfect tool for linting. Axios, react-native-firebase, and Apollo Client are used for setting up the networking workflow in React Native projects. For state management, Redux is one of the most frequently used React Native libraries.

In addition, React Native is compatible with JavaScript libraries.

When React Native isn’t a good solution

Despite React Native being a breakthrough in mobile application development, it has some drawbacks. Recently, Airbnb and Udacity shared their experience using React Native and gave the verdict that this platform has plenty of benefits but still can’t be successfully used to build absolutely any kind of mobile application.

#1 Immaturity

React Native is newer, faster, and less mature than iOS or Android. This can have a negative impact on programs. Generally, React Native works perfectly, but there are some cases when its immaturity results in unpredictable instances, which we’ll show you below:

  • The React Native framework is growing extremely fast and new updates are released every week. Every new update has a lot of changes, so developers need to regularly update their apps. Going more than a few months without updating an app can have a poor result. For example, Airbnb developers faced a problem with React Native for their mobile app development in 2017. They found it impossible to use React Native version 0.43 to React Native version 0.49 as they used React 16 alpha and beta.
  • In some cases, developers can’t limit themselves to writing code only in React Native. They might need to use an additional native code for components that aren’t compatible with React Native.
  • There are some cases when React Native components work worse than native components. For example, with long lists. Users see these kinds of lists everywhere: tweets on Twitter, photos on Instagram, and posts on Facebook are all app lists. When these lists become too huge and complicated, it’s much harder to implement them with React Native. React Native has a FlatList library to work with long lists, but it can’t be compared to the flexibility and maturity of native platforms like UICollectionView (on iOS) and RecyclerView (on Android). So using native platforms in such cases is considered more productive.

#2 JavaScript tooling

JavaScript is an extremely flexible and powerful programming language, but it is a weakly typed language. Some mobile engineers might face a lack of type safety, which makes it difficult to scale. As a result, engineers have to adopt other integrations like TypeScript and Flow to the existing infrastructure.

#3 Complex user interfaces

React Native isn’t a good choice for developing an app that requires many interactions, animations, screen transitions, or complex gestures.

However, there’s a gesture responder system in React Native that runs the lifecycle of all gestures in the app, when it comes to screens with complex gestures, developers might face some difficulties as the Android and iOS touch subsystems are too different for using a unified API.

#4 Initialization time

Even on high-end devices, it takes several seconds to initialize the runtime before React Native can render for the first time. The reason is that the JavaScript thread also requires time to initialize.

#5 Open-source libraries

Knowing several platforms well is a rather daunting task for a mobile engineer, and requires much time and effort. React Native libraries that have native bridges, such as for videos and maps, require a good understanding of three platforms to run successfully. If mobile engineers know only one or two platforms, it may lead to a lack of knowledge required to solve some inconsistencies on Android and iOS.

Wrapping up

Summing up the pros and cons of using the React Native framework for mobile app development, we would say that it can benefit about 80 percent of businesses by saving them a great deal of time and money. React Native is a perfect solution for most use cases unless you have some specific platform issues.

CONTENTS

Authors:

Mykola V.

Mykola V.

IOS/Android Developer

Anastasia D.

Anastasia D.

Copywriter

Rate this article!

Nay
So-so
Not bad
Good
Wow
38 rating, average 4.47 out of 5

Share article with

Comments (7)
WeDoWebApps
WeDoWebApps about 6 years ago
Thanks for sharing this information but i need more information React Native is good or not.
Reply
Maryna Z.
Maryna Z. about 6 years ago WeDoWebApps
Hi there! Well, there isn't an exact answer to that question. In the article, we've tried to show when it's reasonable to use React Native and when it's not. The bottom line is: if you need a technology that'll allow you to launch a mobile app fast and cover iOS and Android platforms, then RN is a good choice.
Reply
Jignesh Thanki
Jignesh Thanki almost 6 years ago
Thanks for sharing!! I am very happy to find the advantages of using React Native to develop a mobile app by this post. I share this post with my Friends.
Reply
Anastasia D.
Anastasia D. almost 6 years ago Jignesh Thanki
Hi there! We're glad you enjoy our work. Thanks :)
Reply
Myappgurus App Development
Myappgurus App Development over 4 years ago
Thanks for sharing the detailed reason to choose react native. As a technical guy, I experience that react native made coding simpler than ever. It has allowed the clients to effectively scale according to rising demand in Mobile App Development, UX/UI, DesignWeb Development
Reply
Alexander Triando
Alexander Triando over 4 years ago
Very informative blog. The details posted are very important for React Native app development companies or startups. Keep sharing.
Reply
Prakash Kumar
Prakash Kumar about 3 years ago
This is very useful for freshers who are mobile app developers. Thanks and kudos. Will share it with my peers and friends.
Reply

Subscribe via email and know it all first!