{"id":18360,"date":"2023-03-28T07:00:46","date_gmt":"2023-03-28T05:00:46","guid":{"rendered":"https:\/\/pasiona.com\/maui-vs-react-native\/"},"modified":"2023-03-28T07:00:46","modified_gmt":"2023-03-28T05:00:46","slug":"maui-vs-react-native","status":"publish","type":"post","link":"https:\/\/pasiona.com\/en\/maui-vs-react-native\/","title":{"rendered":"Maui Vs React Native"},"content":{"rendered":"

If you wouldn’t eat a fork soup, don’t develop an app with the wrong technology.<\/strong><\/p>\n

<\/p>\n

In the latest articles<\/a> written by colleagues from the Mobile department<\/a> we emphasize our great commitment to .NET MAUI, and in them we give you some tips of our knowledge, but, although we have our<\/a> preferences, we have experience not only in MAUI but also in React Native.<\/p>\n

In some cases we have the big question: with what technology to approach it? .NET MAUI and React Native are two very popular mobile development technologies, with their particular strengths and weaknesses, and the choice of which one to use depends largely on the specific requirements of the project to be developed. Although both have their strengths and weaknesses, we will explain from our point of view and broadly the differentiating points that can make us opt for one or the other.<\/p>\n

What is React Native?<\/strong><\/h2>\n

\"Logo<\/p>\n

It is an open source framework currently developed by Meta<\/a> for creating “native” mobile applications using JavaScript and React.<\/p>\n

Platforms<\/strong><\/h3>\n

Android and iOS<\/p>\n

User interface<\/strong><\/h3>\n

Although the development is with React, most of the controls that allow us to use React Native internally, refer to native controls. This allows you to create applications that look and feel in a very similar way to native applications, without the need for specific knowledge of each platform.<\/p>\n

Native API Access<\/strong><\/h3>\n

It is true that React Native offers us the possibility to access the native API of each platform but, according to our experience, using the native API to establish BLE connections (Bluetooth Low Energy<\/em>) or other requirements that need to delve a little deeper into the native API, the results have not been optimal.<\/p>\n

Similarly, we also found certain deficiencies in the background tasks of the application.<\/p>\n

Development<\/strong><\/h3>\n

It offers highly modular and reusable code, making it easy to maintain and scale.<\/p>\n

Success stories<\/strong><\/h3>\n

Some examples of success with the aforementioned framework are the mobile applications of: Facebook, Instagram, Discord, Pinterest, UberEats, Walmart and Airbnb.<\/p>\n

What is .Net Maui?<\/strong><\/h2>\n

\"Logo<\/p>\n

.NET MAUI<\/strong>, is a proprietary platform of Microsoft, based on .NET to create cross-platform native mobile applications.<\/p>\n

Platforms<\/strong><\/h3>\n

<\/strong>Android, iOS, Windows 10\/11, Mac OS, GNU\/Linux (Tizen).<\/p>\n

User interface<\/strong><\/h3>\n

Similar to React Native, all standard platform controls internally implement the native controls of each platform, allowing you to build applications with a native look, without requiring platform-specific knowledge.<\/p>\n

To develop the interfaces in MAUI, having the development layer of the front completely separated, allows to develop the user interface in both XAML and Blazor, allowing the developer to act in the language that feels most comfortable (or suits him best).<\/p>\n

Native API Access<\/strong><\/h3>\n

From MAUI we have access to 100% of the native API, allowing us to access all the components of the device, BLE wifi, camera, etc.<\/p>\n

Development<\/strong><\/h3>\n

As in React Native, it allows us to have one code to govern them all, but where customization by platform is much simpler than React Native and its own predecessor, Xamarin Forms.<\/p>\n

Success stories<\/strong><\/h3>\n

Some examples of success with the aforementioned framework are the mobile applications of: Cincinati Children’s Caren (Medical Center), UPS, Alaska Airlines, Microsoft Azure, Captio and Orlo.<\/p>\n

 <\/p>\n

But what now?<\/strong><\/h2>\n

As we discussed in the previous paragraphs, it is not easy to make a choice, but if we review point by point the two platforms we find small keys that will make us choose, let’s see the key points of each:<\/p>\n

 <\/p>\n

\"Compare<\/p>\n

 <\/p>\n

 <\/p>\n

Seeing these points, we can deduce in which cases we could cover the application with one or another technology, obviously from our experience. Surely, in a round table with developers they could differ based on their own experiences.<\/p>\n

If we are going to carry out a small project, in which we look for speed and that is visually attractive, we have access to the native API and simple processes, and we have a JS team with knowledge of React Native or React (being able to assume the learning curve of React Native), without hesitation, we would opt for an application in that technology.<\/p>\n

On the other hand, if we need to make an application available for Windows, Linux and MacOS (these last two it is true that we can currently find that not all components are available), apart from iOS and Android, or the application, is used to:<\/p>\n