3min read

Native or React Native? Choose the Best Tech for your Project

Luckily for all, going native is not the only option when it comes to developing your mobile app nowadays. Instead, our choice is broader.

I must admit that I was one of the strongest advocates of native technologies. My conviction was supported by constant research and market monitoring. During the last 8 years we have seen a lot of enthusiasts proclaiming the end of native development. What happened with all these new shiny technologies that were to be the next big thing? They usually settled in a niche and disappeared from view. But it’s different today—something has finally changed and we have more options to choose from—all depending on the scope, budget and character of the project. In the following article I’ll present a brief analysis of native and non-native technologies. It is important to take all this into consideration when deciding which technology would work best for your project.

Check if React Native
is the right tech for your project

The champion

Native app development has many benefits. Just to name a few:

  • We get official support from the platform vendor.
  • We can choose the desired abstraction level to operate on. This allows us to find a sweet spot between development effort, and required level of control.
  • Even with a relatively high level of abstraction the performance is impeccable.

If the market consisted of a single platform, we would be able to end discussion. In fact, the market is split into two almost equal parts between iOS and Android. Two platforms using different languages and adopting different paradigms. As a result, the respective developer teams can only cooperate on a conceptual level. Sharing almost no code. Additional effort needs to be put into testing their work and synchronizing their efforts. All this makes developing natively fairly expensive.

The failed contenders

The obvious solution to this problem would be to use one language and one paradigm for all the platforms. Ideally this “holy grail of mobile development” should be already based on a popular technology. Take these two together and you get a perfect candidate: JavaScript. The temptation is big. Both iOS and Android come with a component called WebView which, to put it simply, displays a webpage inside an app. Add some layering around and even access to native API’s is possible. This concept, known commonly as hybrid mobile apps, or web-containers, seems to be the solution. The biggest name here is Phonegap.

But when we take a closer look, a fundamental flaw can be observed: the lack of performance. JavaScript on its own is an interpreted language. And because of its prototype-based programming model, it isn’t easy to optimize its execution. The UI engine based around HTML and CSS is also order of magnitude slower than a more direct approach. On a relatively slow device like a smartphone, this has a noticeable impact on the perceived performance. That may be one of the reasons why Mark Zuckerberg from Facebook, a strong supporter of web-containers, announced in 2012: “The biggest mistake we made as a company was betting too much on HTML5”.

There are other technologies like Xamarin or Appcelerator that adopt the idea of a common language, but drop the HTML part for a self-made abstraction layer, or direct mapping of the native UI components. Performance may be better, but most of the cost benefits are also gone.

The runner-up

What was really missing in the hybrid app approach was a performant implementation of a cross-platform UI abstraction layer. In 2013 Facebook presented a solution, at first only for the web, in the form of React. The underlying tech called “Virtual DOM” provides a smart approach for describing UI in a HTML-like declarative manner. This representation is later translated either to normal HTML or when using React Native, to native UI components. Although nice for programmers (it improves productivity a lot) this doesn’t solve the performance problem. The novelty lies is the way React handles changes to the element tree. The engine, once it “knows” what needs to be done, can do smart things in order to assure that the UI stays fluid. For example by deciding to postpone part of the work until the next rendering frame. The framework still uses JavaScript, but the main performance bottleneck is no longer there.

This combination of productivity and performance improvements makes, in our opinion, a fundamental difference in comparison to the previous hybrid technologies. As a nice side effect: the application can share a lot of code between the two main deployment targets: web and mobile. Our experience shows that around 50% code reuse can be achieved.

And the winner is…

Taking all this into account, we think that these two competing approaches will dominate the mobile ecosystem in the foreseeable future. When choosing technology for your project, follow the golden rule. If only one platform is targeted, or absolute control and performance are required, then native development should be selected. If cost-effectiveness and time-to-market are the key factors, React + React Native should be considered.

Good luck!


AntoniPrincipal Software Engineer


Sign in and expect sharp insights, recommendations, ebooks and fascinating project stories delivered to your inbox

The controller of the personal data that you are about to provide in the above form will be Polidea sp. z o.o. with its registered office in Warsaw at ul. Przeskok 2, 00-032 Warsaw, KRS number: 0000330954, tel.: 0048 795 536 436, email: (“Polidea”). We will process your personal data based on our legitimate interest and/or your consent. Providing your personal data is not obligatory, but necessary for Polidea to respond to you in relation to your question and/or request. If you gave us consent to call you on the telephone, you may revoke the consent at any time by contacting Polidea via telephone or email. You can find detailed information about the processing of your personal data in relation to the above contact form, including your rights relating to the processing, HERE.

Data controller:

The controller of your personal data is Polidea sp. z o.o. with its registered office in Warsaw at ul. Przeskok 2, 00-032 Warsaw, KRS number: 0000330954, tel.: [0048795536436], email: [] (“Polidea”)

Purpose and legal bases for processing:


Used abbreviations:

GDPR – Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016
on the protection of natural persons with regard to the processing of personal data and on the free movement
of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)

ARES – Polish Act on Rendering Electronic Services dated 18 July 2002

TL – Polish Telecommunications Law dated 16 July 2004

1)        sending to the given email address a newsletter including information on Polidea’s new projects, products, services, organised events and/or general insights from the mobile app business world |art. 6.1 a) GDPR, art. 10.2 ARES and art. 172.1 TL (upon your consent)

Personal data:name, email address

2)       statistical, analytical and reporting purposes |art. 6. 1 f) GDPR (based on legitimate interests pursued by Polidea, consisting in analysing the way our services are used and adjusting them to our clients’ needs, as well as developing new services)

Personal data:name, email address

Withdrawal of consent:

You may withdraw your consent to process your personal data at any time.

Withdrawal of the consent is possible solely in the scope of processing performed based on the consent. Polidea is authorised to process your personal data after you withdraw your consent if it has another legal basis for the processing, for the purposes covered by that legal basis.

Categories of recipients:

Your personal data may be shared with:

1)       authorised employees and/or contractors of Polidea

2)       persons or entities providing particular services to Polidea (accounting, legal, IT, marketing and advertising services) – in the scope required for those persons or entities to provide those services to Polidea


Retention period:

1)       For the purpose of sending newsletter to the given email address – for as long as the relevant consent is not withdrawn

2)       For statistical, analytical and reporting purposes – for as long as the relevant consent is not withdrawn

Your rights:


Used abbreviation:

GDPR – Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016
on the protection of natural persons with regard to the processing of personal data and on the free movement
of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)

According to GDPR, you have the following rights relating to the processing of your personal data, exercised by contacting Polidea via [e-mail, phone].

1)       to access to your personal data (art. 15 GDPR) by requesting sharing and/or sending a copy of all your personal data processed by Polidea

2)       to request rectification of inaccurate personal data
(art. 16 GDPR) by indicating the data requiring rectification

3)       to request erasure of your persona data (art. 17 GDPR); Polidea has the rights to refuse erasing the personal data in specific circumstances provided by law

4)       to request restriction of processing of your personal data (art. 18 GDPR) by indicating the data which should be restricted

5)       to move your personal data (art. 20 GDPR) by requesting preparation and transfer by Polidea of the personal data that you provided to Polidea to you or another controller in a structured, commonly used machine-readable format

6)       to object to processing your personal data conducted based on art. 6.1 e) or f) GDPR, on grounds relating to your particular situation (art. 21 GDPR)

7)       to lodge a complaint with a supervisory authority,
in particular in the EU member state of your habitual residence, place of work or place of the alleged infringement if you consider that the processing
of personal data relating to you infringes the GDPR
(art. 77.1 GDPR)

No obligation to provide data:

Providing your personal data is not obligatory, but necessary for Polidea to provide you the newsletter service

Refusal to provide the above data will result in inability to receive the newsletter service.


In the process of providing the newsletter service, we make decisions in an automated way, including profiling, based on the data you provide.


“Profiling” means automated processing of personal data consisting of the use of your personal data to evaluate certain personal aspects relating to you, in particular to analyze or predict aspects concerning your personal preferences and interests.


The automated decisions are taken based on the analysis of clicked and viewed content. They affect the targeting of specific newsletter content to selected users registered to receive the newsletter service, based on the anticipated interests of the recipient.