Skip to content

Applications

PWA, native or cross-platform app: which to choose

The best option depends on how your application will actually be used, not on trends. This guide compares the three alternatives and gives you criteria to choose.

The Devecu team · · 6 min read

The three options in one sentence

A PWA (Progressive Web App) is a web application that can be installed on a phone or computer and behaves like an app, without going through an app store.

A cross-platform app is built once, with tools such as React Native or Flutter, and runs on iOS and Android. It is published in the stores.

A native app is built separately for each system (Swift for iOS, Kotlin for Android). It offers the deepest device access and is also the most expensive.

PWA: when it is enough

A PWA is often an excellent first option when:

  • Users arrive from a link, an email or a message, and you do not need them to download anything.
  • The application is mostly forms, lists, dashboards and data lookup.
  • You want a single codebase that works on phone and computer.
  • You prefer not to depend on store reviews and fees.

The limits of a PWA

A PWA has less access to device features than a store app, and that access varies by system and browser, especially on iOS. If your project depends on Bluetooth, sensors, background tasks or deep operating-system integration, check this before deciding.

It also does not appear in the stores by default, which matters if your audience expects to find you there.

Cross-platform: the middle ground

React Native and Flutter allow one codebase for iOS and Android with an experience very close to native. They are usually the best option when you need to be in the stores, use device features such as the camera or notifications, and do not want to pay for two developments.

It is the most frequent choice for products aimed at a broad mobile audience.

Native: when it is worth it

We recommend a native app when there are very specific requirements for performance, graphics, hardware or operating-system integration that the other options do not cover well. It is the most expensive to build and maintain because it means two codebases.

A quick guide to deciding

Match your case:

  • Management application or internal dashboard: start with a PWA or a web application.
  • Store or catalog with orders: a well-built PWA is usually enough, and you can add a store app later if the business asks for it.
  • Consumer product that needs to be in the stores: cross-platform.
  • Heavy use of hardware or graphics: native.
  • An idea you want to validate quickly: the cheapest option that lets you truly test it, usually a PWA.

An example from our work

The two systems we have published as case studies, the Dybri Store application and the Psykhé Nutrire management system, are web applications installable as PWAs. In both cases the priority was for users to get in without friction from a link and for the team to work from a phone or a computer.

You can start small and grow

Choosing one option does not lock you in forever. Much of the work, such as business logic, the API and the design, is reused. Many products start as a PWA, validate the idea and move to cross-platform once usage justifies it.

Back to the blog

Do you have a product or an idea you need to build?

Tell us what you need to solve. We can help you define the solution and turn it into software.

Tell us about your project

Choose which categories you allow. You can change your choice at any time from the "Cookie settings" link in the footer. Cookie Policy.