PWA vs Native vs Cross-Platform: which technology should you choose for your application?

Introduction

Today, there are several ways to create an application. Among the most common solutions are Progressive Web Apps (PWA), native iOS apps (Swift), Android (Kotlin), as well as cross-platform solutions like Flutter or React Native.

Choosing the right technology is not always straightforward. Each solution has its advantages and limitations depending on the project.

In this article, I will try to guide you in order to help you choose the most suitable solution for your application.

To do this, we will compare these different approaches according to several important criteria:

• the performance

• the development budget

• the development time

• the type of project

What is a native application?

A native application is an application developed specifically for a mobile operating system, such as Android or iOS.

On Android, development is primarily done using the Kotlin language, while on iOS, it is done using Swift. These two technologies are modern programming languages specifically designed to develop high-performance mobile applications.

The main advantage of native development is complete access to the features of the operating system. When a new feature is introduced in Android or iOS, it is generally possible to use it immediately in the application.

Native development also allows direct access to the hardware of the phone, such as the camera, GPS, sensors, or biometric features, as long as these accesses are permitted by the operating system.

Since the application is developed directly for the system, this allows for the best possible performance and a seamlessly integrated user experience with the platform.

You can often recognize a native application when the same application exists on iOS and Android, but with slight interface differences. For example, certain visual elements like buttons, search fields, or fonts may vary to comply with the conventions of each system.

Among the examples of well-known applications developed natively are Revolut, Airbnb, and Uber.

However, native development generally requires creating two distinct applications: one for Android and one for iOS. This means that you need to maintain two different codebases, which can increase development time, maintenance, and the potential number of bugs.

Advantages of native applications

• optimal performance

• full access to hardware

• better integration with the system

• optimized user experience

Disadvantages

• longer development

• higher cost

• two codebases to maintain

What is a cross-platform application?

A cross-platform application allows you to develop a single codebase for multiple platforms. In our case, this means a single code for Android and iOS.

The principle is to develop the application with a framework like Flutter or React Native, then generate a compatible application for each system. A specific configuration may be necessary for Android and iOS, but the core of the application remains common.

Specifically, development is done in the language of the framework used. Then, a rendering engine takes care of displaying the application interface. This allows for a rendering that is very close to, or even identical to, that on Android and iOS.

However, since the application does not execute directly via the native components of the system, performance may be slightly lower than that of a native application, especially for very complex applications.

Furthermore, when new features are added to iOS or Android, they are not immediately available in cross-platform frameworks. Generally, you have to wait for an update of the framework before you can use them.

The main advantage of cross-platform development is having just one codebase to maintain, which considerably reduces development time and costs.

Examples of applications developed with these technologies include:

• Flutter: Google Pay, Alibaba, BMW App

• React Native: Facebook, Discord, Bloomberg

Advantages of cross-platform applications

• one codebase

• faster development

• reduced cost

• consistent rendering across multiple platforms

Disadvantages

• performance slightly lower than native

• dependency on the framework

• access to new features may be delayed

What is a PWA?

A PWA (Progressive Web App) is an enhanced web application, often referred to as a WebApp. It is essentially a website that uses modern technologies to provide an experience similar to a mobile application.

Thanks to a specific configuration, the browser can offer the user to install the application on their phone. For the end user, it feels like a traditional application, but in reality, it is still a website.

A well-designed PWA can operate very smoothly. It can be loaded for the first time, then continue to function with minimal network dependency, especially thanks to Service Workers. This allows, for example, to manage an offline mode or to limit network calls to only the necessary data (like APIs).

PWAs also allow access to certain advanced features:

• push notifications

• local storage (database)

• installation on the home screen

• partial offline functionality

The main advantage of a PWA is its distribution. It is accessible directly via a web browser, without going through stores like Google Play or the App Store. This allows for much faster deployment without the need for validation.

However, a PWA is still limited by the capabilities of the browser. If a feature is not accessible via the web, it will not be available in the PWA. Moreover, some features are still limited on iOS, which can restrict possibilities.

Some well-known examples of PWAs include:

• Starbucks

• Pinterest

• AliExpress

Advantages of PWAs

• rapid development

• no need to go through stores

• accessible from a simple link

• simplified maintenance

• installation possible on mobile

Disadvantages

• limited access to hardware

• browser dependency

• restricted features on iOS

• performance inferior to native

Comparison PWA vs Native vs Cross-Platform

When to choose each solution?

Native

Native development is particularly suited when there is a specific need for a single platform. In this case, costs may be similar to a cross-platform solution, as only one application is developed.

For example, I worked for a butcher shop that used only iPads. The choice naturally leaned towards a native iOS application, as there was no need to support Android.

More generally, native development is recommended for:

• applications with a large budget

• projects requiring optimal performance

• complex applications

• games

• applications with a lot of animations or interactions

Cross-platform

Cross-platform is often the best choice when the budget is more limited compared to native, while needing an application available on iOS and Android.

With a single codebase, it helps reduce costs while maintaining good performance.

It is an ideal solution for:

• startups

• MVP (Minimum Viable Product)

• projects with a reduced budget

• applications needing rapid presence on multiple platforms

PWA

PWAs are particularly suited to projects with a very limited budget or for simple applications.

They are ideal for:

• internal tools

• simple applications

• platforms accessible via a link (without mandatory installation)

For example, I developed an application for a client who wanted to offer a service to their own customers. We chose a PWA because the budget was limited, but it allowed us to include all the necessary features.

If we had opted for a cross-platform solution, some features would have had to be dropped due to the budget, not to mention the additional costs related to publishing on stores.

Moreover, since the application needed to be distributed directly from its business, the PWA format was much simpler and more convenient to set up.

Conclusion

There is no universal solution between PWA, Native, and Cross-Platform. Each technology addresses specific needs and should be chosen based on the project.

Native development remains the best option for performance-demanding applications or those requiring full access to the phone's features.

Cross-platform offers an excellent compromise between cost, development speed, and multi-platform compatibility.

Finally, PWAs are ideal for simple projects, limited budgets, or applications directly accessible via the web.

The choice will primarily depend on several factors:

• your budget

• your performance needs

• development time

• expected features

In many cases, it may be wise to start with a quick solution like a PWA or a cross-platform MVP, and then evolve to native if the project grows.

As a developer, the important thing is not to choose a "better" technology than another, but to choose the one that is most suited to your needs.