Hands holding a smartphone with an open app, the screen glowing blue

Mobile App for Business: Native, Cross-Platform or PWA?

When a company decides to build a mobile app, the first technical debate is almost always the same: build separately for iOS and Android, go with Flutter or React Native, or skip all that and ship a PWA. Each option has its champions, and each is right in its own situation. The problem is that the choice is often made on the basis of "that's what our contractor knows" rather than what the product needs.

Below is an honest comparison of approaches to mobile app development for business: the strengths and weaknesses of native, cross-platform and PWA, when to choose which, and what you need to know about publishing in the App Store and Google Play. No holy wars, just the criteria we use to make the call on our own projects.

The problem first, then the technology

Before choosing a stack, answer a few questions. The answers matter more than any comparison table.

We work through these questions in the first stage, audience and user flow research. We choose the technology after that, not before.

Choose the stack based on the product's needs, not on "that's what our contractor knows."

Native development: the full power of the platform

A native app is written separately for each platform, in Swift for iOS and Kotlin for Android, using each platform's own tools and UI components.

When to choose it. A product where the app is the main channel and a key competitive advantage; heavy hardware work; high demands on performance and smoothness; ample resources for long-term development.

Cross-platform development: Flutter and React Native

Cross-platform development lets you write a single codebase for iOS and Android. The two most widely used frameworks work differently.

Flutter

Google's framework, written in Dart. It renders the interface with its own engine, so the app looks the same on every platform and you control every pixel. It suits products with an expressive custom design where you don't need to replicate the iOS and Android system components exactly. The limitation: there are fewer developers on the market than for JavaScript, and device-specific features sometimes require native modules.

React Native

Meta's framework, written in JavaScript or TypeScript. It uses the platforms' native components, so the interface feels closer to the system. A big plus is the shared language and some shared logic with web development: a team that builds your website or web service in React can reuse its knowledge and part of the code. The limitations are similar: unusual device work needs native modules, and framework and library updates need attention.

Where cross-platform falls short

Heavy on-device computation, complex graphics, deep integration with system features that have only just shipped. Another risk is dependence on third-party libraries: if the library for a feature you need is abandoned, you'll have to take over its maintenance.

When to choose it. Most business apps: online stores, booking and delivery services, customer accounts, loyalty programs, internal tools. One team, one codebase, synchronized releases and much lower maintenance costs, with a high-quality interface.

PWA: an app without the app stores

A PWA (Progressive Web App) is a web app that can be installed on the home screen straight from the browser. It can work offline with cached data and send push notifications.

When to choose it. Internal tools for employees, partner services, quick hypothesis testing before investing in a full app, products where most traffic comes from search and links. The project logic here is closer to building a web service than to mobile development.

How to choose: a quick cheat sheet

Put the three approaches side by side, and the differences look like this.

NativeCross-platformPWA
CodebaseTwo: iOS and AndroidOne for iOS and AndroidOne for all devices, desktops included
Device accessFull, new OS features right awayBroad; native modules for specific featuresLimited, especially on iOS
Development and maintenanceMore expensive: every feature is built twiceMuch cheaper maintenance, synchronized releasesCan often be built from an existing web service
PublishingThrough the stores, with reviewThrough the stores, with reviewNo stores, instant updates
When to chooseThe app is the main channel; heavy hardware workMost business appsInternal tools, partners, hypothesis testing

For example, if the brief is an app for hotel or resort guests, what matters is working on the slopes with a weak signal, location, and buying services in a couple of taps. For a mobile VPN service like the one we built, the platform's system-level networking capabilities and reliable background operation come first. Different problems, different priorities when choosing a stack.

What to build in from the first release

Whichever approach you choose, a mobile app is more than screens on a phone. Some things are cheaper to plan for up front than to add later.

The scope of the first release also shapes the budget. The more precisely the user flows and integrations are described, the more accurate the estimate.

Publishing in the App Store and Google Play

Publishing is a separate stage that's often underestimated in project timelines.

The work continues after publishing: updates for new OS versions, bug fixes, new functionality driven by analytics. The principle is the same as for a website: decide in advance which user actions count as success, and track them as conversions and events.

FAQ

Which is cheaper: native or cross-platform development?

Usually cross-platform: one codebase instead of two, one team, synchronized releases. The difference is most noticeable in maintenance and ongoing development, where every native feature has to be built twice.

Flutter or React Native: which should we choose?

Flutter suits products with a rich custom design and animations, since it renders the interface itself. React Native pays off if the company already does web development in React and wants to reuse skills and some of the logic. Both work for most business apps.

Can a PWA replace a mobile app?

For internal tools, partner services and testing hypotheses, often yes. For a mass-market consumer product, a PWA falls short: it isn't in the stores, device features are limited on iOS, and push notifications only work after it's added to the home screen.

Do we need to publish in both the App Store and Google Play?

If your audience uses both iOS and Android, yes. Each store has its own developer account, review process and requirements, so plan the time for preparing builds and listings for both. Cross-platform development makes it easier to keep the two versions in sync.

Whose name should the store developer accounts be in?

The client company's. That way the app, its reviews and its publishing history belong to you rather than the contractor, and changing teams won't cost you access to the app.

Let’s discuss your project
Related reading